SSD upgrade woes...

Posted by: Major_Sarcasm

SSD upgrade woes... - 28/12/2008 13:54

Hi All

My long-suffering spouse bought me a couple of Transcend 32GB SSDs for Christmas as linked in the CF Empeg thread here.

I installed them yesterday and used Mark's Big Disk Builder as per the drive upgrade instructions in the FAQ (very comprehensive, thanks Tony). The builder worked fine, no problems that I could see so I installed V3A11 with Hijack slipstreamed downloaded from Mark's Big Disk page. So far so good. After installation, I updated Hijack to 503 and then tried to upload some files with Emplode. For some odd reason, Emplode couldn't see the Empeg on COM1, even though I'd been uploading Hijack with COM1 only a few minutes previously. No probs, I thought, I'll edit config.ini to reflect the static IP that I wanted on the 'peg which was the only reason that I wanted to use COM1 to connect anyway.

So, I ended up with an Empeg with V3A11 and Hijack 503 connected via Emplode on the IP I required. Great! Until I asked it to have some music on it.

I added just over a GB of files to Emplode and hit sync. I wandered off (as you do) and came back a bit later. The first thing I noticed was the message on the Empeg's display: "0000.-1 hdb: err: stat_timo" Not having seen that before, I opened my Terminal client (Tera Term) and watched the serial output (sorry, don't have a record). By this time, Emplode had popped up some warnings about files not being uploaded.

I killed the Emplode process as it seemed to be stuck and going nowhere and made the decision to re-build the disks (I'd also remembered a bug in A11 that used to cause me grief and was the reason that I wasn't running it prior to the new HDDs) with V2.0 final instead. I deleted the fids and did this, still using Mark's Big Disk builder, but using V2.0 Final without Hijack this time, adding 503 afterwards.

All went without a hitch and I was able to access COM1 again from within Emplode. Not sure what the problem with A11 and the COM access is, but never mind.

I tried uploading some songs again and got the same issues only worse. Log below.

Code:
end_request: I/O error, dev 03:44 (hdb), sector 553676
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 553678
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 553680
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 553682
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 553684
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 553686
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")


*****CUT TO SAVE SPACE (100s OF LINES)*****

Code:
end_request: I/O error, dev 03:44 (hdb), sector 33106
hdb: drive not ready for command
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 33106
hdb: drive not ready for command
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
Restart code received
Starting player
Timezone: GMT
Hijack: intercepting config.ini

hdb: stat_timo: status=0xff
hdb: drive not ready for command
  player.cpp        : 385:empeg-car 2.00 2003/04/01.
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0000.-1 hdb: err: stat_timo")
end_request: I/O error, dev 03:44 (hdb), sector 264
hdb: drive not ready for command
! tunedb_disk.cpp   :1274:Database size mismatch error.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000
hdb: stat_timo: status=0xff
hdb: drive not ready for command


*****AT THIS POINT EMPLODE/EMPEG GOT STUCK AND REQUIRED A HARD RESET*****

Code:
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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v503 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Thu Aug 14 22:07:32 EDT 2008
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102438) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9bb84
Tuner: loopback=1, ID=-1
show_message("Hijack v503 by Mark Lord")
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 d0004900).
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...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0x5f55
hda: TS32GSSD25-M, ATA DISK drive
hdb: TS32GSSD25-M, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TS32GSSD25-M, 30560MB w/0kB Cache, CHS=62090/16/63
hdb: TS32GSSD25-M, 30560MB w/0kB Cache, CHS=62090/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:26:09:86
Partition check:
 hda: 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.
EXT2-fs warning: checktime reached, running e2fsck is recommended
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
empeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
Timezone: GMT
Hijack: intercepting config.ini

hijack: removed menu entry: "Hard Disk Detection"
hijack: removed menu entry: "Serial Port Assignment"
kftpd: listening on port 21
khttpd: listening on port 80
  player.cpp        : 385:empeg-car 2.00 2003/04/01.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000
Dead temp.sensor, status=0x00


I checked the Empeg and only the 1st layer of my playlists had been added but no files. The bizarre thing about all this is that I don't think either of the SSDs is faulty. The builder worked ok and the player software installed without any problems. I tried running smartctl, but error logging is not supported by these drives (so smartctl said).

Any clues, clever friends? Should I try the regular disk builders on the drives individually and run the stress tests? Would this be safe on SSDs?
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 28/12/2008 14:12

Thought I'd try Jemplode quickly to see if it handled things any differently. I asked it to delete the playlists that had already been uploaded.

Code:
hda: stat_timo: status=0xd0
show_message("0120.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0120.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hdb: stat_timo: status=0xd0
show_message("0120.-1 hdb: err: stat_timo")
hdb: no DRQ after issuing WRITE
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0120.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0120.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hdb: stat_timo: status=0xd0
show_message("0120.-1 hdb: err: stat_timo")
hdb: no DRQ after issuing WRITE
ide0: reset: success
hdb: stat_timo: status=0xff
show_message("0120.-1 hdb: err: stat_timo")
hdb: drive not ready for command
ide0: reset: success
Restarting system.

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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v503 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Thu Aug 14 22:07:32 EDT 2008
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102438) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9bb84
Tuner: loopback=1, ID=-1
show_message("Hijack v503 by Mark Lord")
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 d0004a00).
empeg RDS driver initialised
empeg power-pic driver initialised
RAM disk driver initialized:  16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xbfaa
ide_data_test: wrote 0x5555 read 0x5f55
hda: TS32GSSD25-M, ATA DISK drive
hdb: TS32GSSD25-M, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TS32GSSD25-M, 30560MB w/0kB Cache, CHS=62090/16/63
hdb: TS32GSSD25-M, 30560MB w/0kB Cache, CHS=62090/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:26:09:86
Partition check:
 hda: 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.
EXT2-fs warning: checktime reached, running e2fsck is recommended
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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
Timezone: GMT
Hijack: intercepting config.ini

hijack: removed menu entry: "Hard Disk Detection"
hijack: removed menu entry: "Serial Port Assignment"
kftpd: listening on port 21
khttpd: listening on port 80
  player.cpp        : 385:empeg-car 2.00 2003/04/01.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000


It removed them ok, but there was a lot of garbage at the start.
Posted by: mlord

Re: SSD upgrade woes... - 28/12/2008 20:04

Maybe the SSD firmware has a master/slave bug (or maybe they're not jumpered correctly?).

So, for fun, remove one SSD, and rebuild from scratch. Any better?
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 07:24

Well, I've searched Transcend's website for firmware updates but with no joy. Just going to try individual builds now. Post back a little later.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 07:49

I've checked the jumper positions. Based on the label on the drive...



I would say that the positions are correct? One jumper for master, no jumper for slave.



When I had the empeg booted up yesterday with both drives in, she was happy to report both drives present and correct.

Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 10:01

OK, left the drive that was jumpered as master connected and rebuilt that. Just tried uploading two albums to it and got:

Code:
Adding Swap: 16596k swap-space (priority -3)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
hda: stat_timo: status=0xd0
show_message("0740.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0740.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Restart code received
Starting player
Timezone: GMT
Hijack: intercepting config.ini

  player.cpp        : 385:empeg-car 2.00 2003/04/01.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000


So, two timeout errors in about 25 songs. Not good. Just for shits and giggles, I deleted the songs and uploaded them again. This time I got three errors. In both upload attempts, the files were transferred successfully to the empeg, despite the errors, with no warnings from emplode. When I tried yesterday to upload significantly more music, emplode displayed errors and some tracks were not transferred.

Gonna do the same with the slave (jumpering it as master).
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 10:26

right in the middle of building the second drive and I've noticed something curious. The 'pumping partition' stage of the builder wizard was subject to long pauses in the progress bar during the building of the first drive, whereas the second drive was not and the partition was pumped in about 1/4 of the time. Not sure if it's relevant.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 11:11

Build of second drive done, going to install player software and hijack. Thought I'd post the log.

Code:
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v488 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Feb 15 10:29:26 EST 2008
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102438) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (992k code, 20k reserved, 368k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9bb84
Tuner: loopback=1, ID=-1
show_message("Hijack v488 by Mark Lord")
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 d0005080).
empeg RDS driver initialised
empeg power-pic driver initialised
RAM disk driver initialized:  16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS32GSSD25-M, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TS32GSSD25-M, 30560MB w/0kB Cache, CHS=62090/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:26:09:86
Partition check:
 hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
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 ... Freeing unused kernel memory: 4k init+ /bin/mount -n /proc
+ log 'Builder image'
+ echo 'Builder image'
Buildeshow_message("Builder image")
r image
+ echo 'POPUP 9999 Builder image'
+ DRIVE1=
+ '[' -e /proc/ide/hdb -a -e /proc/ide/hdc ']'
+ '[' -e /proc/ide/hdb ']'
+ '[' -e /proc/ide/hdc ']'
+ /bin/mount -n -t ext2 -o ro,nocheck /dev/hda4 /drive0
+ '[' -d /drive0/fids ']'
+ /bin/umount /drive0
+ /bin/mkswap /dev/hda6
Setting up swapspace version 0, size = 16994304 bytes
+ /bin/swapon /dev/hda6
Adding Swap: 16596k swap-space (priority -1)
+ /bin/mkswap /dev/hda3
Setting up swapspace version 0, size = 17027072 bytes
+ /bin/swapon /dev/hda3
Adding Swap: 16628k swap-space (priority -2)
+ log 'Tuning hda5'
+ echo 'Tuning hda5'
Tuning show_message("Tuning hda5")
hda5
+ echo 'POPUP 9999 Tuning hda5'
+ /bin/tune2fs -c -1 -i0 /dev/hda5
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
+ makedrive hda4 /drive0
+ dev=/dev/hda4
+ log 'Making hda4 filesystem'
+ echo 'Makishow_message("Making hda4 filesystem")
ng hda4 filesystem'
Making hda4 filesystem
+ echo 'POPUP 9999 Making hda4 filesystem'
+ /bin/mkfs.ext2 -v -s 1 -i 131072 -m 0 /dev/hda4
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=
243840 inodes, 31210200 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
3810 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:  258/3810Dead temp.sensor, status=0x00
done
Writing superblocks and filesystem accounting information: done
+ log 'Tuning hda4'
+ echo 'Tuning hda4'
Tuning hda4
+ echo 'POPUP 9999 Tuning hda4'
show_message("Tuning hda4")
+ /bin/tune2fs -c -1 -i0 /dev/hda4
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
+ /bin/sync
+ /bin/sync
+ log 'Mounting hda4'
+ echo 'Mounting hda4'show_message("Mounting hda4")

Mounting hda4
+ echo 'POPUP 9999 Mounting hda4'
+ /bin/mount -n -o rw,nocheck /dev/hda4 /drive0
+ /bin/sync
+ /bin/sync
+ log 'Making directories'
+ echo 'Making dishow_message("Making directories")
rectories'
Making directories
+ echo 'POPUP 9999 Making directories'
+ /bin/mkdir /drive0/fids
+ /bin/mkdir /drive0/var
+ echo '[hijack]'
+ log 'Remounting ro'
+ echo 'Remountingshow_message("Remounting ro")
 ro'
Remounting ro
+ echo 'POPUP 9999 Remounting ro'
+ /bin/mount -n -o remount,ro /dev/hda4 /drive0
+ /bin/sync
+ /bin/sync
+ log 'hda4 completed'
+ echo 'hda4 completeshow_message("hda4 completed")
d'
hda4 completed
+ echo 'POPUP 9999 hda4 completed'
+ '[' '' '!=' '' ']'
+ /bin/swapoff /dev/hda3
+ log 'Zeroing hda3'
+ echo 'Zeroing hda3'
Zeroing show_message("Zeroing hda3")
hda3
+ echo 'POPUP 9999 Zeroing hda3'
+ /bin/cat /dev/zero
/bin/cat: write error: No space left on device
+ /bin/swapoff /dev/hda6
+ log 'Done!  Testing disk..'
+ echo 'Done!  Testing disk..'
Done!  Testing disk..
+ echo 'POPUP 9999 Done!  Testing disk..'
show_message("Done!  Testing disk..")
+ /sbin/hdstress
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Speed checking /dev/hda3
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Read/write of 8Mb took 9.65 seconds
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Drive length is 62586880 blocks, seek testing
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Seek test complete:  2.01 seconds.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=1 on fd=5
hdstress.cpp   194 (   33): Read a button press
hdstress.cpp   194 (   33): Read a button press
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Speed checking /dev/hda3
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Read/write of 8Mb took 3.92 seconds
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Drive length is 62586880 blocks, seek testing
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Seek test complete:  2.02 seconds.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=1 on fd=5
hdstress.cpp   194 (   33): Read a button press
hdstress.cpp   194 (   33): Read a button press
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Speed checking /dev/hda3
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Read/write of 8Mb took 6.78 seconds
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Drive length is 62586880 blocks, seek testing
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Seek test complete:  2.01 seconds.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Speed checking /dev/hda3
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Read/write of 8Mb took 3.98 seconds
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Drive length is 62586880 blocks, seek testing
hdstress.cpp   189 (   33): Poll result=1 on fd=5
hdstress.cpp   194 (   33): Read a button press
hdstress.cpp   194 (   33): Read a button press
Seek test complete:  2.02 seconds.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp   189 (   33): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp   189 (   33): Poll result=0 on fd=5


Tony, I thought it worth mentioning that this is Mark's Big Disk Builder. In the FAQ it states that this version doesn't stress test the drives after build when in fact it does.
Posted by: tfabris

Re: SSD upgrade woes... - 29/12/2008 11:42

I was told bigdisk didn't stress. Who told me that?
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 11:48

Bugger. The second drive displayed five errors whilst uploading the same songs.

Any clues Mark? Could it be that these devices simply aren't compatible with the Empeg full stop?
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 11:51

Originally Posted By: tfabris
I was told bigdisk didn't stress. Who told me that?

It doesn't do that in my latest internal copy here
(I just checked it now), but it might (or apparently does)
in some of the released versions.

That thing really needs an update soon-ish,
but my MythTV box is calling for some TLC and VDPAU goodness.

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 11:56

Originally Posted By: Major_Sarcasm
Bugger. The second drive displayed five errors whilst uploading the same songs.

Any clues Mark? Could it be that these devices simply aren't compatible with the Empeg full stop?

That does appear to be the case -- the original thread showed
64GB devices working, but perhaps these 32GB ones still have
firmware bugs, or are very slow at writing small amounts of data.

Try hdparm -W0 -K1 (top link on Hijack page)
on them (once), and then send them some more tunes.

EDIT: actually, first dump/post here the hdparm -I results.

-ml
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 12:05

Oh, and I wouldn't panic too much just yet.
There's this guy around here somewhere who knows how
to hack IDE stuff at the lowest of levels, so odds
are good that these can be made to work just fine. smile

Quote:
hda: no DRQ after issuing WRITE

A longer than normal timeout in the Linux driver
might cure that one. Spec says 20msec, Linux waits 50msec.
But we could easily have it wait (much) longer, if it turns
out to be simply slow at write-prepare/erase time.

Another thing which will probably help a great deal
for SSD here (including CF cards), would be to turn on
the multi-sector write capabilities, if they're not already on.

Hijack used to do this, but I think (not sure) that I took
it out again after a complaint from somewhere.
This really should go back in for CF cards and SSDs.

Cheers
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 12:24

Hehe, that's why I'm grateful & glad you're on the case.

Being a complete linux n00b, can you tell me why when I try to execute the hdparm file, I get this:

**edited for brevity of the thread**

It seems to be ignoring the -I switch.
Posted by: LittleBlueThing

Re: SSD upgrade woes... - 29/12/2008 12:48

You need to tell it what drive to look at.

So try :

hdparm.bin -I /dev/hda
hdparm.bin -I /dev/hdb
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 12:55

Ah ha! Thank you indeed.

Code:
empeg:/drive0/var# ./hdparm.bin -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:       TS32GSSD25-M
        Serial Number:      00238605014A
        Firmware Revision:  V0826
Standards:
        Used: ATA/ATAPI-7 T13 1532D revision 4a
        Supported: 8 7 6 5 & some of 8
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:   62586880
        device size with M = 1024*1024:       30560 MBytes
        device size with M = 1000*1000:       32044 MBytes (32 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 1   Current = ?
        Recommended acoustic management value: 128, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
                Write cache
                Look-ahead
           *    Mandatory FLUSH_CACHE
           *    SATA-I signaling speed (1.5Gb/s)
           *    SATA-II signaling speed (3.0Gb/s)
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
        2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Integrity word not set (found 0x0000, expected 0xa8a5)
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 13:46

Okay, so was that before, or after, you did hdparm -W0 -K1 ?

If it was before, then you should instead try hdparm -W1 -K1
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 13:47

Added the 1st drive back in and hdparm'd it. Exactly the same (as expected) just a different serial no.

It appears that "hdparm.bin -I /dev/hda" works but "hdparm.bin -I /dev/hdb" doesn't when two devices are connected. I'll have to manually swap each drive into the master position to effect any changes it seems.

Originally Posted By: mlord
Try hdparm -W0 -K1 (top link on Hijack page)
on them (once), and then send them some more tunes.


I haven't done this yet as your post appeared to suggest holding off on these commands until I'd posted the results of "-I"
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 13:48

Oh.. and I now see that these are SATA SSDs.
Which cannot work as-is in an empeg (wrong connector, among other issues).

So.. how do you have them connected ?

EDIT: Mmm.. I suppose the maker might have built-in
a SATA-to-IDE convertor chip, which could explain that.
And those chips often cause other problems, too.


Thx.
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 13:54

Originally Posted By: Major_Sarcasm
It appears that "hdparm.bin -I /dev/hda" works but "hdparm.bin -I /dev/hdb" doesn't when two devices are connected. I'll have to manually swap each drive into the master position to effect any changes it seems.

Uh.. you'll need to fix that before wasting time on *anything* else here.
This is fundamental, and must work.

???
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 14:04

Code:
empeg:/drive0/var# ./hdparm.bin -W1 -K1 /dev/hda

/dev/hda:
 setting drive keep features to 1 (on)
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)


Just uploaded some files and got:

Code:
hda: stat_timo: status=0xd0
show_message("0000.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0000.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0000.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: stat_timo: status=0xd0
show_message("0000.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset: success

Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 14:05

Originally Posted By: mlord
EDIT: Mmm.. I suppose the maker might have built-in
a SATA-to-IDE convertor chip, which could explain that.
And those chips often cause other problems, too.

Okay, so the bridge chip is indeed built-in,
according to page 6 of the product datasheet.

So one might reasonably expect these things to actually be IDE (ATA) compliant. heh.
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 14:10

The dual drive hdparm thing is one issue,
but I suppose we should set that aside
and concentrate on getting a single drive config going first.

So unplug one drive, and use just a single SSD for now.

Here's a special hijack image that waits longer for DRQ on writes.

The theory is that they're pre-erasing the sectors before
allowing the data transfer to begin, and this is taking a
while. Especially when our transfers are so tiny, requiring
lots of erasing and data shuffling internal to the SSD.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 14:11

I've just done a "hdparm -I" and the write cache is now got an asterisk by it, so I guess that flag stuck.

The drives have a 44 pin connector and plug straight in. I noticed the SATA reference in the data earlier and wondered whether it would have significance to this app.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 14:12

Just hijacking now. Report back soon.
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 14:18

It's just an ordinary (but misnamed) zImage file, same as usual.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 14:55

*faints*

OK, just uploaded the same bunch of files (about 25) with no errors being reported via serial and none on the empeg's display either.

Mr Lord, I bow before thee.

Should I apply those W1 K1 switches to the other drive?
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 16:06

Well, first we need to know if the -W1 -K1 did it, or if the new hijack did it..

Did you try the -W1 -K1 with the original (released) Hijack ?

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 29/12/2008 16:08

Or more useful, perhaps, could you just do hdparm -W0 and then try some more uploads with the experimental hijack ?

If that still works, then I'll release that copy of Hijack, and *maybe* respin the bigdisk images to include it.

Cheers
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 16:25

Originally Posted By: mlord
Well, first we need to know if the -W1 -K1 did it, or if the new hijack did it..

Did you try the -W1 -K1 with the original (released) Hijack ?

Cheers


Yes, and that resulted in errors.

Originally Posted By: mlord
Or more useful, perhaps, could you just do hdparm -W0 and then try some more uploads with the experimental hijack ?

If that still works, then I'll release that copy of Hijack, and *maybe* respin the bigdisk images to include it.

Cheers


Will do. I'll report back in a bit.
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 29/12/2008 16:40

OK, W set to zero and uploaded tracks with no errors. I guess that means that your modified hijack is what fixed the problem.

Just out of interest, will enabling/disabling write-caching have any performance benefits/detriments in this environment?

Do you have any idea why I was unable to use /dev/hdb to specify the slave SSD with hdparm?
Posted by: mlord

Re: SSD upgrade woes... - 30/12/2008 02:23

Originally Posted By: Major_Sarcasm
OK, W set to zero and uploaded tracks with
no errors. I guess that means that your modified hijack is what
fixed the problem.

Great. I'll make it an "official" release shortly.

Quote:
Just out of interest, will enabling/disabling
write-caching have any performance benefits/detriments
in this environment?

I think I'd suggest disabling it, as our kernel doesn't know
anything about safely flushing the write cache, and
(contrary to common opinion) the empeg s/w *does*
write to the media (dynamic data partition)
during normal playback operation.

So just leave write-caching
off for safety with these slow-writing SSDs.
For regular hard disks, no issues either way.

Quote:
Do you have any idea why I was unable to use /dev/hdb
to specify the slave SSD with hdparm?

No. But that *has to work* if you want a two-drive system.
I'm probably just missing something obvious..

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 30/12/2008 02:40

Originally Posted By: mlord
Great. I'll make it an "official" release shortly.

Or maybe not. Sourceforge seems to have finally broken my scripts,
and removed the ability to easily upload binary files.

I refuse to use their absolutely STUPID "file release manager"
crap for Hijack, so this might be the end of Hijack availability
at Sourceforge
.

Hmmph.

EDIT: hacked it, working again. For now.
Posted by: mlord

Re: SSD upgrade woes... - 30/12/2008 03:28

I've also updated the bigdisk builder stuff on my server,
to include Hijack v504 in the images. Untested, of course. smile
Posted by: Major_Sarcasm

Re: SSD upgrade woes... - 30/12/2008 11:29

I added the second drive back in late last night and uploaded ~27GB of files with no problems whatsoever. I had a look in the fids folders on each drive and it seems to be balancing the files between the two.

Mark, as ever, I am most grateful for your assistance.
Posted by: tfabris

Re: SSD upgrade woes... - 30/12/2008 16:34

Mark, you are awesome.
Posted by: 101

Re: SSD upgrade woes... - 25/01/2009 04:57

I am using v504 disk builder image with a single 64 GB SSD of the same brand and getting a ton of these virtual memory errors:

VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")

This is on an old 12MB player, any ideas why?
Posted by: mlord

Re: SSD upgrade woes... - 25/01/2009 12:15

Which exact builder file are you using (name and bytecount, please)?

Can you capture a trace from the serial port while running it (helps a LOT)?

Thanks.
Posted by: 101

Re: SSD upgrade woes... - 25/01/2009 13:55

builder_bigdisk_v3.upgrade
2.16 MB (2,267,745 bytes)
MD5 0b8b1f793a7e2a7e8253fad6a35afc41

Code:
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v504 ([email protected]) (gcc version
2.95.3 20010315 (release)) #2 Mon Dec 29 23:29:04 EST 2008
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c0c00000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 80000512) 12MB DRAM
Command line: mem=12m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10944k/12M available (996k code, 20k reserved, 324k 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)
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 67706d65 'empg'
Tuner: loopback=0, ID=-1
show_message("Hijack v504 by Mark Lord")
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 d0005000).
empeg RDS driver initialised
empeg power-pic driver initialised
RAM disk driver initialized:  16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: TS64GSSD25-M, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TS64GSSD25-M, 61136MB w/0kB Cache, CHS=7793/255/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:10:02:0
0
Partition check:
 hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
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+ /bin/mount -n /proc
+ log 'Builder image'
+ echo 'Builder image'
Builder image
+ echo 'POPUP show_message("Builder image")
9999 Builder image'
+ DRIVE1=
+ '[' -e /proc/ide/hdb -a -e /proc/ide/hdc ']'
+ '[' -e /proc/ide/hdb ']'
+ '[' -e /proc/ide/hdc ']'
+ /bin/mount -n -t ext2 -o ro,nocheck /dev/hda4 /drive0
+ '[' -d /drive0/fids ']'
+ /bin/umount /drive0
+ /bin/mkswap /dev/hda6
Setting up swapspace version 0, size = 16412672 bytes
+ /bin/swapon /dev/hda6
Adding Swap: 16028k swap-space (priority -1)
+ /bin/mkswap /dev/hda3
Setting up swapspace version 0, size = 24670208 bytes
+ /bin/swapon /dev/hda3
Adding Swap: 24092k swap-space (priority -2)
+ log 'Tuning hda5'
+ echo 'Tuning hda5'
Tuning hda5show_message("Tuning hda5")

+ echo 'POPUP 9999 Tuning hda5'
+ /bin/tune2fs -c -1 -i0 /dev/hda5
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
+ makedrive hda4 /drive0
+ dev=/dev/hda4
+ log 'Making hda4 filesystem'
+ echo 'Makishow_message("Making hda4 filesystem")
ng hda4 filesystem'
Making hda4 filesystem
+ echo 'POPUP 9999 Making hda4 filesystem'
+ /bin/mkfs.ext2 -v -s 1 -i 131072 -m 0 /dev/hda4
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=
488256 inodes, 62492850 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
7629 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, 53747713,

Writing inode tables: done
Writing superblocks and filesystem accounting information: show_message("1530.-1
 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
Posted by: mlord

Re: SSD upgrade woes... - 25/01/2009 16:09

Mmm.. looks like you are doing everything The Right Way(tm).

So, the mkfs thinks it is running out of memory,
which is very odd given the amount of swap space
we allocate for its use.

If I can find my 32GB CF card, I'll give this a try
on that later today in a Mk2 12MB unit. And then perhaps
again with a larger hard disk.

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 25/01/2009 16:18

If you grok Linux, you could just finish off the process by hand.
A reboot (from its present state) will give you a shell prompt
at the serial console, where you could re-issue the mkfs.ext2
command from the script by hand.

Cheers
Posted by: 101

Re: SSD upgrade woes... - 25/01/2009 22:32

I know enough to fumble around, but I couldn't figure out how to get a prompt on the builder image as every reboot attempts to reformat the drive. Seems like it would be pretty easy to work around if I could get to a prompt. Is that mkfs cmd the end of the script?

Thank you so much for such a ridiculously fast response btw, and I really appreciate the help.
Posted by: mlord

Re: SSD upgrade woes... - 25/01/2009 22:48

Here's a builder version that logs you in, and tells you what to do.

Have fun. smile
Posted by: 101

Re: SSD upgrade woes... - 26/01/2009 01:09

Thanks for that new image. However, when I manually run the first cmd (mkfs.ext2) I get the same nomem error.
Posted by: mlord

Re: SSD upgrade woes... - 26/01/2009 01:30

Originally Posted By: 101
Thanks for that new image. However, when I manually run the first cmd (mkfs.ext2) I get the same nomem error.


Mmm.. bummer, but not completely unexpected.

I'm not sure why it fails to use the swap space for memory, but.. oh well.

Can you connect the drive to a Linux box (internally,
or externally via USB or whatever)
and just do the same commands to it from there?

That's the workaround at this point.

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 26/01/2009 01:41

I've scrounged up a Mk2 and a 60GB (hard) drive here now,
and we will see what happens with it.. gimme a few minutes..
Posted by: mlord

Re: SSD upgrade woes... - 26/01/2009 02:01

Mmm.. no problems here. But regardless, this might help:

builder_bigdisk_v3_alt.upgrade

This one has tweaked mkfs options to (hopefully) reduce the amount of RAM required.

Give it a whirl..
Posted by: 101

Re: SSD upgrade woes... - 26/01/2009 12:12

The alt one you posted (link is a little squirrely)seems to have made it through the script. There was one error "zeroing hda3":
/bin/cat: write error: No space left on device
Not sure if that was normal or not, just sounds like it wrote to the end.

Do you think the problem is related to the empeg-flash driver? Seems like something is being loaded that is bigger than normal and causing an issue with this SSD on a 12MB player.
Posted by: tman

Re: SSD upgrade woes... - 26/01/2009 13:32

Originally Posted By: 101
Do you think the problem is related to the empeg-flash driver? Seems like something is being loaded that is bigger than normal and causing an issue with this SSD on a 12MB player.

It doesn't mean flash as in SSD. There is a small amount of flash memory inside the empeg that stores some current state and config data.
Posted by: mlord

Re: SSD upgrade woes... - 26/01/2009 14:11

Originally Posted By: 101
The alt one you posted (link is a little squirrely)
seems to have made it through the script.
There was one error "zeroing hda3":
/bin/cat: write error: No space left on device
Not sure if that was normal or not

Yes, that's normal. Ignore it.

Quote:
Do you think the problem is related to the empeg-flash
driver? Seems like something is being loaded that is bigger
than normal and causing an issue with this SSD on a 12MB player.

No. Linux on the empeg doesn't even know you have an SSD.
It thinks of it and treats it exactly as a regular hard drive.

So, the _alt_ builder worked though, and you should now be all set.

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 26/01/2009 19:15

I've now updated the bigdisk builder images (at rtr.ca)
with Hijack v508. There's also now a new _v4_ builder
which uses a 4KB blocksize (rather than 1KB),
and a 4X higher bytes:inodes ratio.

These changes make it much more suitable for large disks
and/or low-memory usage.

Cheers
Posted by: 101

Re: SSD upgrade woes... - 26/01/2009 22:57

Thanks again so much for the help Mark, all seems to be working.

Only issues I have now are config related. I've been using the old 2.0 beta for like 7 years and I need to figure out how to get the fader back and now the player no longer shuts off in the car. So I'll need to do some searches to get up to speed on restoring that functionality, and what else is new.

SSD issues seem to be resolved.
Posted by: 101

Re: SSD upgrade woes... - 27/01/2009 23:44

Okay, I am completely baffled. I've done some searches and apparently I have "home mode in the car" syndrome and saw all these threads about a blown diode and HW replacement etc.

I will say that being a HW guy (encoder replacement was much more straight forward to me than swapping in an SSD) this is ridiculous. I put in my old drive with the old firmware and all functionality returned with 0 issues. Clearly this is a software problem, yet there's many threads on diode replacement and I couldn't find anything pointing to software.

What is the deal here? I have been out of the loop for years and just want to replace my dying mechanical HD with an SSD.

Can I just image my old drive to the SSD? At this point I could care less about losing a few gig to an LBA issue. I just want it to work with no hassle, as I don't have as much time to spend on this as I would like.

Suggestions? Please?

Posted by: mlord

Re: SSD upgrade woes... - 28/01/2009 13:05

What is shown on the Hijack Menu's "Force AC/DC Power Mode"
screen on your player?

Post the four lines here, please.
Posted by: haffi

Re: SSD upgrade woes... - 10/09/2014 19:18

Hi all I know this is an old thread but I am having similar problems...

I inserted a SSD 120GB Kingston SSD now into the Empeg with Adapter and It is getting the HDA timeout issues on the Display.
Can someone help me with this ? Is there a way to telnet into the empeg ? my Serial port does way to much of Crashing my computer ( since its a usb adapter ).
I used the Big disk Image first and then the hijack 5.18.

I am able to upload some tracks but it crashes the player all the time.
I have tried swapping out the SSD and the Adapter , plus the HDD cable with the same results.
Thanks
Posted by: mlord

Re: SSD upgrade woes... - 10/09/2014 21:18

Yeah, my apologies for putting this on the back burner. Hijack has a telnetd built-in, which can be enabled by putting "ktelnetd_port=23" into the "[hijack]" section of the player's config.ini file.

For the adapter, I don't yet know what's wrong, and haven't made the time to investigate yet. But I have seem similar behaviour with some adapters in the past, and might still have one on hand that misbehaves like that. So.. there's hope.

With luck, it's just a timing thing: SSDs respond _instantly_ to stuff that takes milliseconds with mechanical drives, and something may just not be ready for that as soon as it ought to be.

Cheers
Posted by: haffi

Re: SSD upgrade woes... - 02/05/2015 15:37

Any new Mlord ? my player works ok... but if I try to fast forward and randomly it freezez up , and I think your right with the timing issues.
Where can I start.

If I telnet to the empeg and try fsck -fay /dev/hda4 it just says

empeg:/# fsck -fay /dev/hda4
fsck -fay /dev/hda4
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (1): Memory allocation failed
Parallelizing fsck version 1.19 (13-Jul-2000)


my

empeg:/# hdparm -I /dev/hda
hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
Model Number: KINGSTON SVP200S3120G
Serial Number: 50026B72270195F5
Firmware Revision: 501ABBF0
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
Used: unknown (minor revision code 0x0110)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 234441648
LBA48 user addressable sectors: 234441648
device size with M = 1024*1024: 114473 MBytes
device size with M = 1000*1000: 120034 MBytes (120 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
Write-Read-Verify feature set
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* SATA-I signaling speed (1.5Gb/s)
* SATA-II signaling speed (3.0Gb/s)
* SMART Command Transport (SCT) feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
2min for SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50026b72270195f5
NAA : 5
IEEE OUI : 26b7
Unique ID : 2270195f5
Integrity word not set (found 0x0000, expected 0x6ea5)
Posted by: haffi

Re: SSD upgrade woes... - 03/05/2015 07:11

Player displays this and then the empeg is non responsive
0000.0 hda: err: stat_timo
Posted by: mlord

Re: SSD upgrade woes... - 03/05/2015 13:25

When that message appears on the display, there will be a corresponding, more detailed message at the serial port.
Something like: hda: stat_timo: status=0x80
followed by another line describing what it was trying to do at the time.

Any chance you could capture those messages and post them here?
Based on the value it prints for "status=0x..", it might be possible to work around the issue.

In particular, if it says "status=0x88", and "no DRQ after issuing WRITE", then it's a very easy fix.

Thanks.
Posted by: mlord

Re: SSD upgrade woes... - 03/05/2015 13:41

Originally Posted By: haffi

If I telnet to the empeg and try fsck -fay /dev/hda4 it just says

empeg:/# fsck -fay /dev/hda4
fsck -fay /dev/hda4
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (1): Memory allocation failed


To work around that problem with fsck, just do "swapon -a" before starting the fsck command.
Posted by: djc

Re: SSD upgrade woes... - 09/01/2019 23:02

Hi all, it's time to bring this thread up one more time. I decided to bring a few Mk2a players back to life with 128GB SSDs, and I am experiencing similar timeout symptoms as those above. I am running in a single-drive configuration, and the errors occur in read-only playback mode (haven't tried uploading new music yet).

The errors generally follow this pattern:

Code:
hda: stat_timo: status=0xd0
show_message("0000.42 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.42 hda: err: stat_timo")
end_request: I/O error, dev 03:04 (hda), sector 1080024
hda: drive not ready for command
hda: stat_timo: status=0xd0
show_message("0000.42 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.42 hda: err: stat_timo")
hda: drive not ready for command

And a clean boot log is below. Any advice is appreciated. Thanks.

--Dan.

Code:
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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v524 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Dec 15 08:52:50 EST 2017
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103799) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 14992k/16M available (1000k code, 20k reserved, 368k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9cb88
Tuner: loopback=0, ID=-1
show_message("Hijack v524 by Mark Lord")
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 d0005c00).
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...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: PA25-128, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: PA25-128, 120832MB w/1kB Cache, CHS=15403/255/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:0e:d7
Partition check:
 hda: 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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To Com&#65533;Starting player
Timezone: EST
Hijack: intercepting config.ini

kftpd: listening on port 21
khttpd: listening on port 80

Dead temp.sensor, status=0x00
Prolux 4 empeg car - 2.1434 Jul  5 2004


Code:
empeg:/drive0/var# hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:       PA25-128
        Serial Number:      978052500008
        Firmware Revision:  20150807
Standards:
        Supported: 9 8 7 6 5
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           15      15
        sectors/track   63      63
        --
        CHS current addressable sectors:   15481935
        LBA    user addressable sectors:  247463936
        LBA48  user addressable sectors:  247463936
        device size with M = 1024*1024:      120832 MBytes
        device size with M = 1000*1000:      126701 MBytes (126 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Standby timer values: spec'd by Vendor, no device specific minimum
        R/W multiple sector transfer: Max = 1   Current = 1
        DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
                Write cache
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    48-bit Address feature set
                Mandatory FLUSH_CACHE
                FLUSH_CACHE_EXT
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
        6min for SECURITY ERASE UNIT.
HW reset results:
        CBLID- above Vih
        Device num = 0
Checksum: correct
Posted by: djc

Re: SSD upgrade woes... - 10/01/2019 16:43

Here's an example of a problem log from a different player with the same model drive (Kingspec PA25-128). Once the problems begin, the player will not recover until I reboot. After a restart, it will happily pick up where it left off and continue to play for a while (sometimes minutes, sometimes hours).

Thanks to Tony and anyone else who had a hand in creating and restoring the lost FAQ. It's greatly appreciated to have it back again as a troubeshooting resource.

--Dan.

Code:
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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v524 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Dec 15 08:52:50 EST 2017
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40104006) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 14992k/16M available (1000k code, 20k reserved, 368k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9cb88
Tuner: loopback=0, ID=-1
show_message("Hijack v524 by Mark Lord")
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 d0005500).
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...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: PA25-128, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x044a
ide_data_test: wrote 0xffff read 0x3fff
ide_data_test: wrote 0xaaaa read 0x044a
ide_data_test: wrote 0x5555 read 0x3fff
hda: PA25-128, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: PA25-128, 120832MB w/1kB Cache, CHS=15403/255/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:a6
Partition check:
 hda: 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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To Com&#65533;Starting player
Timezone: EST
Hijack: intercepting config.ini

kftpd: listening on port 21
khttpd: listening on port 80

Prolux 4 empeg car - 2.1434 Jul  5 2004

attempt to access beyond end of device
03:04: rw=0, want=1972874128, limit=117113850
dev 03:04 blksize=4096 blocknr=-580523293 sector=-349219048 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1972874128, limit=117113850
dev 03:04 blksize=4096 blocknr=-580523293 sector=-349219048 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=2100117676, limit=117113850
dev 03:04 blksize=4096 blocknr=-1085583318 sector=-94731952 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=626265808, limit=117113850
dev 03:04 blksize=4096 blocknr=1767179187 sector=1252531608 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=2100117676, limit=117113850
dev 03:04 blksize=4096 blocknr=-1085583318 sector=-94731952 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=626265808, limit=117113850
dev 03:04 blksize=4096 blocknr=1767179187 sector=1252531608 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1728074060, limit=117113850
dev 03:04 blksize=4096 blocknr=2042631250 sector=-838819184 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1476157000, limit=117113850
dev 03:04 blksize=4096 blocknr=-1778444399 sector=-1342653304 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1728074060, limit=117113850
dev 03:04 blksize=4096 blocknr=2042631250 sector=-838819184 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1476157000, limit=117113850
dev 03:04 blksize=4096 blocknr=-1778444399 sector=-1342653304 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=208150996, limit=117113850
dev 03:04 blksize=4096 blocknr=-1558574988 sector=416301984 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1019703664, limit=117113850
dev 03:04 blksize=4096 blocknr=-1892557733 sector=2039407320 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=208150996, limit=117113850
dev 03:04 blksize=4096 blocknr=-1558574988 sector=416301984 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1019703664, limit=117113850
dev 03:04 blksize=4096 blocknr=-1892557733 sector=2039407320 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1463961632, limit=117113850
dev 03:04 blksize=4096 blocknr=1439732231 sector=-1367044040 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1730637140, limit=117113850
dev 03:04 blksize=4096 blocknr=1506401108 sector=-833693024 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1463961632, limit=117113850
dev 03:04 blksize=4096 blocknr=1439732231 sector=-1367044040 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1730637140, limit=117113850
dev 03:04 blksize=4096 blocknr=1506401108 sector=-833693024 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1355300268, limit=117113850
dev 03:04 blksize=4096 blocknr=1949437802 sector=-1584366768 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=492459404, limit=117113850
dev 03:04 blksize=4096 blocknr=1196856674 sector=984918800 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=1355300268, limit=117113850
dev 03:04 blksize=4096 blocknr=1949437802 sector=-1584366768 size=4096 count=1
attempt to access beyond end of device
03:04: rw=0, want=492459404, limit=117113850
dev 03:04 blksize=4096 blocknr=1196856674 sector=984918800 size=4096 count=1
hda: irq_timo: status=0xd0
show_message("0000.51 hda: err: irq_timo")
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
end_request: I/O error, dev 03:04 (hda), sector 50593832
hda: drive not ready for command
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
end_request: I/O error, dev 03:04 (hda), sector 50593840
hda: drive not ready for command
hda: stat_timo: status=0xd0
show_message("0000.51 hda: err: stat_timo")
hda: drive not ready for command


Code:
empeg:/empeg/bin# hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:       PA25-128
        Serial Number:      978052500014
        Firmware Revision:  20150807
Standards:
        Supported: 9 8 7 6 5
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           15      15
        sectors/track   63      63
        --
        CHS current addressable sectors:   15481935
        LBA    user addressable sectors:  247463936
        LBA48  user addressable sectors:  247463936
        device size with M = 1024*1024:      120832 MBytes
        device size with M = 1000*1000:      126701 MBytes (126 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Standby timer values: spec'd by Vendor, no device specific minimum
        R/W multiple sector transfer: Max = 1   Current = 1
        DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
                Write cache
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    48-bit Address feature set
                Mandatory FLUSH_CACHE
                FLUSH_CACHE_EXT
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
        6min for SECURITY ERASE UNIT.
HW reset results:
        CBLID- above Vih
        Device num = 0
Checksum: correct


Code:
empeg:/empeg/bin# fdisk -l /dev/hda

Disk /dev/hda: 255 heads, 63 sectors, 15403 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1         5     40131    5  Extended
/dev/hda2             6        10     40162+  83  Linux
/dev/hda3            11        13     24097+  10  OPUS
/dev/hda4            14     14593 117113850   83  Linux
/dev/hda5             1         3     24034+  83  Linux
/dev/hda6             4         5     16033+  82  Linux swap
Posted by: tfabris

Re: SSD upgrade woes... - 10/01/2019 17:06

Credit where due: The restoration of the lost FAQ was entirely Faolan's doing. We are very indebted to him.
Posted by: djc

Re: SSD upgrade woes... - 14/01/2019 00:40

One more data point. In addition to the Kingspec PA25-128 drives, which are exhibiting the problems above, I set up a couple of players with IDE/mSATA adaptors. Specifically, the Chenyang mSATA mini PCI-E SATA enclosure, with a Goldendisk mSATA 128GB mini SSD. That combo seems to work just fine in the player. I've got one that's been running for over 48 hours straight with no issues.

All of the Kingspec drives are byte-copies of a master disk created using the Chenyang/Goldendisk combo, copied using dd on a Mac.

Here's the relevant logs for the good drive, in case it helps shed light on any differences with the errors on the Kingspec drives. I'm especially confused by the "attempt to access beyond end of drive" errors on the Kingspec.

Thanks for any insight or suggestions,
--Dan.

Code:
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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v515 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Wed Jul 20 09:24:02 EDT 2011
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103926) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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 20706d65 'emp '
Found custom animation at offset 0x9cb88
Tuner: loopback=0, ID=-1
show_message("Hijack v515 by Mark Lord")
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...
ide_data_test: wrote 0x0000 read 0x0100
ide_data_test: wrote 0xffff read 0x0100
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0004
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0100
ide_data_test: wrote 0xffff read 0x0100
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0100
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffea
ide_data_test: wrote 0x5555 read 0xffff
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: YCdisk YCMSA-128MS, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: YCdisk YCMSA-128MS, 114473MB w/0kB Cache, CHS=14593/255/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:56
Partition check:
 hda: 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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To Com&#65533;Starting player
Timezone: Jamaica
Hijack: intercepting config.ini

hijack: removed menu entry: "Serial Port Assignment"
kftpd: listening on port 21
khttpd: listening on port 80
  player.cpp        : 385:empeg-car 2.01 2004/07/06.
Prolux 4 empeg car - 2.1434 Jul  5 2004
Vcb: 0x40892000

Code:
empeg:/empeg/bin# hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:       YCdisk YCMSA-128MS
        Serial Number:      YC0415171221128M0799
        Firmware Revision:  Q0407A
        Media Serial Num:   &#65533;
        Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
        Supported: 9 8 7 6 5
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  234441648
        LBA48  user addressable sectors:  234441648
        device size with M = 1024*1024:      114473 MBytes
        device size with M = 1000*1000:      120034 MBytes (120 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 1   Current = 1
        Advanced power management level: disabled
        DMA: mdma0 *mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
                Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    DOWNLOAD_MICROCODE
                Advanced Power Management feature set
           *    SET_MAX security extension
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    WRITE_{DMA|MULTIPLE}_FUA_EXT
           *    64-bit World wide name
           *    SATA-I signaling speed (1.5Gb/s)
           *    SATA-II signaling speed (3.0Gb/s)
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 0000
        NAA             : 0
        IEEE OUI        : 0
        Unique ID       : 00
Integrity word not set (found 0x0000, expected 0x43a5)

Code:
empeg:/empeg/bin# fdisk -l /dev/hda

Disk /dev/hda: 255 heads, 63 sectors, 14593 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1         5     40131    5  Extended
/dev/hda2             6        10     40162+  83  Linux
/dev/hda3            11        13     24097+  10  OPUS
/dev/hda4            14     14593 117113850   83  Linux
/dev/hda5             1         3     24034+  83  Linux
/dev/hda6             4         5     16033+  82  Linux swap
Posted by: mlord

Re: SSD upgrade woes... - 14/01/2019 14:09

My rambling thoughts:

Note that your mSATA drive is a different size (capacity) than the PA25-128 drive.

And the PA25-128 might also be a different size (capacity) than your "master" drive. So doing a bit copy from, say, a larger master drive to a slightly smaller PA25-128 could result in the access errors you see. The PA25-128 simply does not have as many sectors as the software thinks it has.

03:04: rw=0, want=1972874128, limit=117113850

In this case, the capacity of the erring /dev/hda4 appears to be 117113850 blocks, where a block is two sectors. 117113850 * 2 = 234227702 sectors for that specific partition. This of course matches what fdisk also reports (234227700), since the two numbers come from exactly the same place.

Most of the errors show "want" blocks that are believable but slightly too large for the partition, but a few of the later ones are quite obviously WAYYY out of range.

I suggest perhaps you should run filesystem checks on /dev/hda4 on the failing drive to see what it says. Something there really looks mucked up from the diskcopy, or ??

Another way things could get messed up is if the old kernel on the empeg somehow has decided to use CHS addressing rather than LBA. That could also confuse the situation. Unfortunately, that kernel doesn't appear to print any indicator of which type of addressing it is using. Except for drives larger than 128GB where it will print LBA48 in the log.

EDIT: I suppose we can rule out CHS addressing, because it reduces the addressable capacity by QUITE A LOT more that what we are seeing here. So that part is likely just fine.

Posted by: tfabris

Re: SSD upgrade woes... - 14/01/2019 22:13

Are any of these issues similar to the ones I encountered when I upgraded to an SSD?
https://empegbbs.com/ubbthreads.php/ubb/showflat/Number/369021

Posted by: mlord

Re: SSD upgrade woes... - 15/05/2019 23:05

As a very late follow-up here, see this slightly newer thread, where I describe findings from using an identical counterfeit Kingspec drive:

https://empegbbs.com/ubbthreads.php/topics/371821/Replacement_SSD
Posted by: suomi35

Re: SSD upgrade woes... - 09/09/2019 22:24

I recently ran out of room on a 64GB SSD and decided to upgrade to a 128GB CF configuration.

I got the 128GB CF setup using the builder_bigdisk_v21.upgrade, restored all fids and dynamic data partition from the 'old' 64GB SSD drive (using a USB<>PATA adapter and a linux box), and things were going seemingly well. Music played fine, reboots were fine, etc.

I tried to add a new album to the player this morning and ran into all kinds of issues during the sync (tried with emplode and jemplode). Namely, the timeout issue that others have mentioned sporadically. Mine is repeatedly giving this message:


"2a40.3 hda: err: stat_timo"

Player infos:
Model: mk2a
Player: v2.01
Hijack: v525
PATA/CF adapter: https://smile.amazon.com/gp/product/B07QW5NRMH/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
CF card: https://smile.amazon.com/gp/product/B07M5M5KYZ/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1
(The CF card adapter is the only device on the IDE)

Has anyone else run into something similar and figured out a solution?

Cheers!
Posted by: tfabris

Re: SSD upgrade woes... - 09/09/2019 22:54

Question: Have you tried, with that new 128gb CF, plain-formatting it (builder_bigdisk_v21.upgrade), and then see if you get errors when you sync an album to it, i.e., without copying fids or the dynamic partition first?

That way, you rule out any potential problems that may have been induced with the copy operation with the PATA adapter that you performed on the linux box.

If that works, then you could try doing the copying inside the player, with the instructions here (scroll to Step 7: Copying files (special circumstances only)).

Posted by: suomi35

Re: SSD upgrade woes... - 09/09/2019 23:04

I have not tried that, but will. Thanks for the tip!!
Posted by: tfabris

Re: SSD upgrade woes... - 09/09/2019 23:33

Also, I'd like to ask Mark Lord his opinion about the CF card itself. You linked this card:

https://smile.amazon.com/gp/product/B07M5M5KYZ/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1

The labeling and text on that card seem to indicate that it is something slightly different than an ordinary CF card. Instead of "CF card" on the label it says "CFF Card". And the accompanying text says things like "features UDMA 7 to deliver fast transfer speeds when used with your DSLR or CF enabled Camera" and "incredible read speeds over traditional CF cards".

I'm wondering if that means it's not following the same specification as a normal CF card, and might be a SATA drive under the hood, instead of a PATA drive. I don't know enough about it though. Mark, do you know?
Posted by: mlord

Re: SSD upgrade woes... - 10/09/2019 10:49

The card description (and Amazon reviews) look a bit iffy, yes. Kingston is being very cagey in the descriptions, but it sounds as if their firmware is doing "special things" for cameras, possibly at the expense of full compatibility.

Bummer. I suppose someday I should try and figure out those "status timeout" errors and introduce a workaround for them. Except I don't think I have anything on-hand that produces them.

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 10/09/2019 11:11

Originally Posted By: mlord
I suppose someday I should try and figure out those "status timeout" errors and introduce a workaround for them.


Okay, here's a rough guess. Give this Hijack kernel a try (attached).
Posted by: suomi35

Re: SSD upgrade woes... - 10/09/2019 15:03

You are great. I flashed builder_bigdisk_v21.upgrade and then immediately applied hijack_v525+.zImage before rebooting. Everything came back fine, no error messages, at least on the VFD wink

I loaded a few albums and changed a few config.ini items via emplode without issue, sync'ing several times.

Here is a boot log, for good measure...everything looks dandy to me:
Code:
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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v525 ([email protected]) (gcc version 2.95.3 20010315 (release)) #7 Tue Sep 10 07:21:38 EDT 2019
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read 00000000
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102452) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 14992k/16M available (1000k code, 20k reserved, 368k 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)
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 67706d65 'empg'
Found custom animation at offset 0x9cb88
Tuner: loopback=0, ID=-1
show_message("Hijack v525+ by Mark Lord")
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 d0005c80).
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...
ide_data_test: wrote 0x0000 read 0x3962
ide_data_test: wrote 0xffff read 0x0343
ide_data_test: wrote 0xaaaa read 0xe787
ide_data_test: wrote 0x5555 read 0x66c3
hda: CF Card, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: CF Card, 119280MB w/0kB Cache, CHS=15206/255/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:26:09:94
Partition check:
 hda: 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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To Comrting player
Timezone: Singapore
Hijack: intercepting config.ini

kftpd: listening on port 21
khttpd: listening on port 80
ktelnetd: listening on port 23

Prolux 4 empeg car - 2.1434 Jul  5 2004


Gotta update that timezone hahaha

Next, I think I will attempt to load all of the fids/dyn_data via USB-PATA adapter/linux and see how that behaves.

I will reply back with results cool

Cheers!
Posted by: mlord

Re: SSD upgrade woes... - 10/09/2019 16:08

Originally Posted By: suomi35
You are great. I flashed builder_bigdisk_v21.upgrade and then immediately applied hijack_v525+.zImage before rebooting. Everything came back fine, no error messages, at least on the VFD wink


Good! Now we just need somebody with one of those non-Kingspec "Yansen" SSDs to give it a whirl. They were also failing with messages like that, I think -- gotta re-read the relevant thread.

Tony?
Posted by: suomi35

Re: SSD upgrade woes... - 10/09/2019 16:38

I notice that there is a 'new' file structure within ~/fids...I think I missed that while doing drive-shuffling last week.

When I added music to the player after flashing (detailed in the above post) it wrote all tracks to /drive0/fids/_00000/

If I have a directory of fids backed on a server, should I now restore them to /drive0/fids/_00000/ or restore them alongside _00000 in /drive0/fids/ ?

If so, I wonder if that would screw up a backed up image of /dev/hda3 (dyn_data)...
Posted by: mlord

Re: SSD upgrade woes... - 10/09/2019 16:41

Restore them straight to /drive0/fids/ as they were before.

When done, login to the player and do this:

rwm ; fidsift.sh ; rom
Posted by: suomi35

Re: SSD upgrade woes... - 10/09/2019 19:11

I am ecstatic!

1. Copied the fids/dyn data onto the CF via linux box
2. Put it back in the empeg
3. Restored dyn data
4. Ran fidsift.sh
5. Sync'd via Emplode
6. Loaded a new album via emplode and changed some config.ini bits
7. Rebooted a few times...zero issues(!)
8. Finally, flashed hijack v526 over v525+

It's flawless now.

Mark, you are a wonderful human. Massive thanks!
And thank you Tony, for all of the hints!
Posted by: suomi35

Re: SSD upgrade woes... - 11/09/2019 18:33

I spoke too soon smirk

I just deleted an album via Emplode and it got stuck on "Remounting disks..." during the sync.

The drive activity LED on the adapter is fully lit (no fluctuation).

Everything else has been perfect though...and I am still ecstatic wink
Posted by: suomi35

Re: SSD upgrade woes... - 11/09/2019 18:44

aaaand, strangely, I just did the same operation (deleted an album) and it worked fine...
Posted by: suomi35

Re: SSD upgrade woes... - 11/09/2019 19:55

I am loving the new setup...somehow the music sounds 'better' than before laugh
Posted by: mlord

Re: SSD upgrade woes... - 12/09/2019 10:21

Originally Posted By: suomi35
I spoke too soon smirk

I just deleted an album via Emplode and it got stuck on "Remounting disks..." during the sync.


Writing (including the "remount" part) can take _ages_ on PATA SSDs and CF Cards. Some are quicker than others on the empeg, and some are not. It doesn't always seem to be strictly related to the rated speed of the card/SSD.

So.. when it gets "stuck", give it a good 20 minutes at least before "pulling the plug"!

Cheers
Posted by: mlord

Re: SSD upgrade woes... - 01/08/2021 16:57

Originally Posted By: mlord
Originally Posted By: suomi35
You are great. I flashed builder_bigdisk_v21.upgrade and then immediately applied hijack_v525+.zImage before rebooting. Everything came back fine, no error messages, at least on the VFD wink


Good! Now we just need somebody with one of those non-Kingspec "Yansen" SSDs to give it a whirl. They were also failing with messages like that, I think -- gotta re-read the relevant thread.

Has anyone here still got a Yansen drive on hand? It would be very useful to know if Hijack-v526 "fixed" the issues with them.
Posted by: elperepat

Re: SSD upgrade woes... - 02/08/2021 10:06

I do have one right here still brand new in box.

Yansen 128GB model PA25-128.
Posted by: mlord

Re: SSD upgrade woes... - 02/08/2021 11:34

That's the one, I believe. Would you be able to run the bigdisk_v21 builder on it and see if it succeeds?

http://rtr.ca/bigdisk/