"As for not working after disk builder - this is normal behavior."

I meant that the "Hard disk not found" error occurred, which is not the expected behaviour (at least, I don't think it is expected) when (re)booting with the disk builder kernel.

Now that I have successfully applied Beta11, I reloaded the disk builder kernel with only the Toshiba as master, and NOW it works. The drive is detected, "built", and stress testing proceeds without error...

I wonder why I had to jump through hoops to get the drive initially built, but once built, it works just fine (and rebuilds just fine).

Could the RioCar core boot sequence be sensitive to some data "pattern" (or missing pattern) on an un-built, un-"upgraded" disk, which results in the "Disk not found" error?

Thanks again.

===============
Probing primary interface...
hda: TOSHIBA MK3017GAP, ATA DISK drive
hda: TOSHIBA MK3017GAP, ATA DISK drive
hda: TOSHIBA MK3017GAP, ATA DISK drive
hda: TOSHIBA MK3017GAP, ATA DISK drive
hda: TOSHIBA MK3017GAP, ATA DISK drive
hda: TOSHIBA MK3017GAP, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TOSHIBA MK3017GAP, 28615MB w/0kB Cache, CHS=58140/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:0f:f
f
Partition check:
hda: [PTBL] [3876/240/63] hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initDrive(s) appear to be already built. Skippi
ng.
Press return to continue anyway - anything else to start a shell.

warning: can't open /etc/mtab: No such file or directory
Making first drive...
mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Linux ext2 filesystem format
Filesystem label=
228160 inodes, 29204280 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
3565 block groups
8192 blocks per group, 8192 fragments per group
64 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409, 663553,
1024001, 1990657, 2809857, 5120001, 5971969, 17915905, 19668993,
25600001,

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

real 2m17.635s
user 0m0.730s
sys 0m3.660s
hdstress.cpp 189 ( 30): Poll result=1 on fd=5
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 194 ( 30): Read a button press
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
Speed checking /dev/hda3
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
Read/write of 8Mb took 3.39 seconds
hdstress.cpp 189 ( 30): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.


Edited by Keith2 (30/05/2002 07:41)
_________________________
Former owner of two RioCar Mark2a with lots of extra stuff