[9fans] oh, no! (again)

[<cej@gli.cas.cz>]

Sadly, I was too optimistic when SATA install succeeded... :-(
This is a report of error messages I've got while booting new system on (and from) sdE0:

sdiahci: drive 0 in state ready after 0 resets   # SATA HD with Plan 9 system on it
sdiahci: drive 1 won't come up; in state new after 10 resets   # SATA DVD
sdE1 waitready: [new] task=50 sstat=113
sdE1 waitready: [new] task=50 sstat=113
sdE1 waitready: [new] task=50 sstat=113
sdE1 waitready: [new] task=50 sstat=113
sdE1 not responding; offline
sdiahci: drive 2 won't come up; in state portreset after 10 resets
sdiahci: drive 3 won't come up; in state portreset after 10 resets
sdiahci: drive 0 in state missing after 0 resets   # strange!
sdiahci: drive 1 in state missing after 0 resets   # strange!
.
1. 1
2. 1
3. none of the above
*nobiosload: 1
[snip]
user[none]: glenda
sdE0: LLBA blah blah ...
sdE1: LBA 0 sectors
time...
fossil(#S/sdE0/fossil)...version...time
init: starting /bin/rc
sdEO: i/o error d0 @206,672
fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x0000005e: part=label block 94: i/o error
sdEO: i/o error d0 @ 3,707,248
fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x000029a4: part=data block c0660: i/o error
aux/vga: error reading block 0x000029a4
rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
init: rc exit status: rio 29: display open
init: starting /bin/rc
==

Other time, rio comes up, with acme running, but:
term% 9fat:
sdE0: i/o error d0 @ 4,317,856   # the number after @ changes when cmd is repeated
fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x0000beb7: part=data block 48823: i/o error   # the numbers after 'score' and 'block' change when cmd is repeated

Sorry for being so verbose, but I can't realize which parts are not significant,
thanks, wishing a great day,

++pac.