Does anyone else have experience with this particular model of Toshiba hard drive?

I recently added a second 30GB hard disk to a RioCar, and discovered that this Toshiba MK3017GAP drive will only work in the RioCar as a slave drive.
It will not work (No hard disk found - Contact Support) by itself as a master, nor as a master to the original Fujitsu MHL2300AT, nor even as master to a 543MB Toshiba from an old notebook.

In all failure modes, I can hear the drive spin up, and continue spinning until I remove power.

Make it the slave, and it works fine (although disk builder would only format it as slave to the 543MB Toshiba, but not the OEM Fujitsu).

I tried this 30GB Toshiba in a notebook (as master), and it FDISK'ed, formatted, and booted DOS just fine.

I have inserted and swapped these drives around a number of times. The cables appear to be fine, no difference which drive is on which connector, only which is jumpered as slave. Even tried the cable select mode - no improvement.

Serial Log is as follows (Toshiba MK3017GAP as master alone):
========================
empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.14-rmk5-np17-empeg50 ([email protected]) (gcc versi
on 2.95.3 20010315 (release)) #8 Fri Feb 8 18:48:15 GMT 2002
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40104095)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15024k/16M available (964k code, 20k reserved, 372k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 636f6972 'rioc'
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004800).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
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...Kernel panic: VFS: Unable to mount root fs on 03:05

============================
With Toshiba MK3017GAP as slave to the RioCar OEM Fujitsu MHL2300AT, the RioCar boots just fine:

Probing primary interface...
hda: FUJITSU MHL2300AT, ATA DISK drive
hdb: TOSHIBA MK3017GAP, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
hdb: 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: hda1 < hda5 hda6 > hda2 hda3 hda4
hdb: [PTBL] [3876/240/63] hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
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 init player.cpp : 385:empeg-car 2.00-be
ta11 2002/02/08.
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

Umm but the kernel has correctly detected the Toshiba by itself. I don't know why you get the multiple lines, but I have seen that before and it seems normal.

I haven't done a drive builder to install a new drive but the fact that the kernel can't find a root fs is probably more the reason you are getting the "No hard disk found" message. This points more to a disk builder problem. Are you sure you're doing the disk builder bit right? Disk builder will not install the player software etc. The drive has to be the master to get the player software while doing an upgrade using the correct .upgrade file. This would explain why it falls over on the single drive boot.

You are powering off the empeg and waiting until the disk builder program tells you to power on aren't you?

In fact according to your boot log, you have the correct partitions on the toshiba. You just don't have the player software.

Try doing an upgrade with just the Toshiba as a master by itself

The RioCar doesn't properly start up with only this Toshiba as master, so I cannot get to the stage where I could use Emplode to install an upgrade image. Once the RioCar says "No hard disk found", it's game over for doing anything with the Toshiba hard disk.

Too bad the disk builder doesn't stress test BOTH hard disks - maybe that would provided a clue to the real cause of the problem...

What I am wondering is whether anyone else has been able to use this particular model successfully in a RioCar.

Actually, you should still be able to start emplode with the empeg off, hit cancel as it looks for the player, select tools, upgrade player and apply power when asked.

Well, what that DID it! Thank you.

It never occurred to me to simply ignore the hard disk not found error, and just proceed with the upgrade (I used Beta11).

Any idea why the primary interface probe lists the Toshiba six times? Could this be indicative of a problem, just on the edge of not working...?

Note to FAQ/empeg folks: It would appear that some (only this model?) hard disks might appear to not work after disk builder alone. Proceeding to the upgrade process _anyway_ worked in my case.

Serial Log of Toshiba MK3017GAP as working single master is below..

===============
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 init player.cpp : 385:empeg-car 2.00-be
ta11 2002/02/08.
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

================

Toshiba as master, OEM Fujitsu as slave also works!

Probing primary interface...
hda: TOSHIBA MK3017GAP, ATA DISK drive
hdb: FUJITSU MHL2300AT, ATA DISK drive
hdb: FUJITSU MHL2300AT, ATA DISK drive
hda: TOSHIBA MK3017GAP, 28615MB w/0kB Cache, CHS=58140/16/63
hdb: FUJITSU MHL2300AT, 28615MB w/2048kB 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
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
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 init player.cpp : 385:empeg-car 2.00-be
ta11 2002/02/08.
! tunedb_disk.cpp :1224:Database size mismatch error.
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

Greetings!

Cool!

As for not working after disk builder - this is normal behavior. Disk builder's sole function is to set up the disk, filesystems and stress test. It never actually loads any version of the player software.

I am surprised it gave a "Disk Not Found". I would think that if disk builder was still the active kernel, it would attempt to rebuild the disk at each boot, and give the indications on screen. Or, if the disk was already built, prompt the user in the shell for yes/no to continue (did you have Hyperterm connected at boot time?). Is the "Disk Not Found" error tied strictly to a timeout??? It might be a false error that would be seen in this situation.

Lastly, I have seen multiple probe instances before. I suspect, but do not know for certain, that the kernel is waiting for a response back from the drive, and sending multiple queries. This result is shown by the single ide0 reply. I would not be worried by that, as long as the response was sane.

Any idea why the primary interface probe lists the Toshiba six times? Could this be indicative of a problem, just on the edge of not working...?

No. The kernel essentially asks the IDE bus "Is anybody out there?" Each attached drive replies. It has to ask several times, as some drives take longer than others to get themselves sorted out, and do not respond to requests until that time. Once a certain number of requests have resulted in only one reply, the kernel will decide that there really is only one drive out there.

Note to FAQ/empeg folks: It would appear that some (only this model?) hard disks might appear to not work after disk builder alone. Proceeding to the upgrade process _anyway_ worked in my case.

That's the way it always works. Strictly speaking, the error message is misleading: it's actually "No mountable root partition found", but the leading cause of that is there being no disk at all. I guess these two errors should be kept separate, to avoid confusion for anyone who has applied a disk builder but not yet an upgrade.

Peter

"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.