IDE read: device 0 not ready with U-Boot 2014.07-tld-2

Hello,

I have a boot problem with a 6G/s SSD. (1.5 G/s WD drive works fine)

U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:58:11)
Seagate GoFlex Net
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: SanDisk SDSSDP128G Firm: 3.2.0 Ser#: 15105740
Type: Hard Disk
Supports 48-bit addressing
Capacity: 120196.6 MB = 117.3 GB (246162672 x 512)
IDE read: device 0 not ready
IDE read: device 0 not ready

Any advise on how to continue investigating this problem?

P.S. I already tried a sleep after the ide reset.

erwin Wrote:
-------------------------------------------------------
> Hello,
>
> I have a boot problem with a 6G/s SSD. (1.5 G/s WD
> drive works fine)
>
> U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:58:11)
> Seagate GoFlex Net
> gcc (Debian 4.6.3-14) 4.6.3
> GNU ld (GNU Binutils for Debian) 2.22
> Hit any key to stop autoboot: 0
> (Re)start USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 1 USB Device(s)
> found
> scanning usb for storage devices... 0
> Storage Device(s) found
>
> Reset IDE: Bus 0: OK Bus 1: not available
> Device 0: Model: SanDisk SDSSDP128G Firm: 3.2.0
> Ser#: 15105740
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 120196.6 MB = 117.3 GB
> (246162672 x 512)
> IDE read: device 0 not ready
> IDE read: device 0 not ready
>
> Any advise on how to continue investigating this
> problem?
>
> P.S. I already tried a sleep after the ide reset.

Erwin, is the info showed above what you expect to see for the SSD? ie. Model, capacity, serial number are all correct?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

The info seams correct for me. (I have reported 4 chars to less in ser#, copy paste error)
I cannot find the firmware version on sandisk site.
Its this thing. http://www.sandisk.com/products/ssd/sata/standard/#Specifications

dmesg | grep ata[12]
[ 12.784613] ata1: SATA max UDMA/133 irq 21
[ 12.812508] ata2: SATA max UDMA/133 irq 21
[ 13.335624] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 13.715798] ata1.00: ATA-7: WDC WD1600BEVS-75RST0, 04.01G04, max UDMA/133
[ 13.722907] ata1.00: 312581808 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 13.794574] ata1.00: configured for UDMA/133
[ 14.345618] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 19.345623] ata2.00: qc timeout (cmd 0xec)
[ 19.349751] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 24.905604] ata2: link is slow to respond, please be patient (ready=0)
[ 29.405602] ata2: SRST failed (errno=-16)
[ 34.955603] ata2: link is slow to respond, please be patient (ready=0)
[ 39.455602] ata2: SRST failed (errno=-16)
[ 45.005603] ata2: link is slow to respond, please be patient (ready=0)
[ 74.465715] ata2: SRST failed (errno=-16)
[ 74.469749] ata2: limiting SATA link speed to 1.5 Gbps
[ 79.475607] ata2: SRST failed (errno=-16)
[ 79.479642] ata2: reset failed, giving up

erwin Wrote:
-------------------------------------------------------
> The info seams correct for me. (I have reported 4
> chars to less in ser#, copy paste error)
> I cannot find the firmware version on sandisk
> site.
> Its this thing.
> http://www.sandisk.com/products/ssd/sata/standard/
> #Specifications
>
> dmesg | grep ata[12]
> [ 12.784613] ata1: SATA max UDMA/133 irq 21
> [ 12.812508] ata2: SATA max UDMA/133 irq 21
> [ 13.335624] ata1: SATA link up 1.5 Gbps
> (SStatus 113 SControl F300)
> [ 13.715798] ata1.00: ATA-7: WDC
> WD1600BEVS-75RST0, 04.01G04, max UDMA/133
> [ 13.722907] ata1.00: 312581808 sectors, multi
> 0: LBA48 NCQ (depth 31/32)
> [ 13.794574] ata1.00: configured for UDMA/133
> [ 14.345618] ata2: SATA link up 3.0 Gbps
> (SStatus 123 SControl F300)
> [ 19.345623] ata2.00: qc timeout (cmd 0xec)
> [ 19.349751] ata2.00: failed to IDENTIFY (I/O
> error, err_mask=0x4)
> [ 24.905604] ata2: link is slow to respond,
> please be patient (ready=0)
> [ 29.405602] ata2: SRST failed (errno=-16)
> [ 34.955603] ata2: link is slow to respond,
> please be patient (ready=0)
> [ 39.455602] ata2: SRST failed (errno=-16)
> [ 45.005603] ata2: link is slow to respond,
> please be patient (ready=0)
> [ 74.465715] ata2: SRST failed (errno=-16)
> [ 74.469749] ata2: limiting SATA link speed to
> 1.5 Gbps
> [ 79.475607] ata2: SRST failed (errno=-16)
> [ 79.479642] ata2: reset failed, giving up

This behavior is the reverse of what we saw in Sandisk Readycache 32GB. U-boot could not identify that disk, but Debian was OK. Here with this SSD, u-boot did identify it correctly, but then it went offline (that's probably why Debian was reporting Identify error in desmg when it tried to inititialze).

Which kernel was this dmesg snippet extracted from, ie. uname -a?

All these errors I think is probably because of the timing in Sandisk SSDs controllers. I would have to look again in the mv sata driver to think of a workaround.

In the mean time, instead of sleep, you could try placing other commands such as "ide part" after the "ide reset" to see if the partition was recognized. And place that right before the "ext2load ide ...."

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

uname -a
Linux debian 3.16.0-kirkwood-tld-2 #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014 armv5tel GNU/Linux

From the console:

U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:58:11)
Seagate GoFlex Net
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 8
0
GoFlexNet> ide reset
i d e r e s e t

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?� Firm: ?�?�?�?� Ser#: ?�?�?�?�?�?�?�?�?�?�
Type: Hard Disk
Supports 48-bit addressing
Capacity: 427923841.5 MB = 417894.3 GB (4611474908973580287 x 512)
IDE read: device 0 not ready
IDE read: device 0 not ready
GoFlexNet> ide part
i d e p a r t

no IDE devices available
GoFlexNet> ide reset
i d e r e s e t

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: not available
GoFlexNet> ide reset
i d e r e s e t

Reset IDE: Bus 0: .......................

Ok. I managed to get some part info from this SSD.

Partition Map for IDE device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 63 289073547 00000000-01 83
loading envs from ide 0 ...
1 bytes read in 54 ms (0 Bytes/s)
importing envs ...
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
ERROR: Environment import failed: errno = 22

at common/cmd_nvedit.c:1055/do_env_import()



Edited 2 time(s). Last edit at 06/14/2015 06:33AM by erwin.

Ah! looks like it is the same problem as the Readycache Sandisk SSD.

Reset IDE: Bus 0: OK Bus 1: not available 
Device 0: Model: ?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?� Firm: ?�?�?�?� Ser#: ?�?�?�?�?�?�?�?�?�?� 
Type: Hard Disk 
Supports 48-bit addressing 
Capacity: 427923841.5 MB = 417894.3 GB (4611474908973580287 x 512) 
IDE read: device 0 not ready

I think if you boot with USB rootfs then it will be recognized OK in Debian, as same as the Readycache SSD.

In fact, the work around is:

- Format the USB stick with a single partition type Ext3, label it "boot" (something other than "rootfs").
- Copy the /boot folders from the SSD rootfs to the USB stick,
- Keep the rootfs on the SSD. Label it "rootfs"

Try booting with this configuration, see if you can. If you can't, please post listing of printenv while in netconsole:

printenv

Notes:

1. This work around is the only known solution currently to enable using the SSD for rootfs. Some u-boot envs adjustments might be needed if you can't boot into Debian. See this for the reason.
2. You could choose to use the USB for rootfs and kernel, and the SSD for data.
3. If you have serial console, it will be much easier to troubleshoot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I do not understand how can you boot from a SSD IDE that is not ready?
The workaround sounds impossible and as expected no success.
When booted from USB with ext3 rootfs, fdisk -l does not list the SSD device, because it is not ready. (The SSD contains a valid ext3 rootfs)
Using the SSD as data disk is also not possible, because it is not available, because the IDE is not ready.

@erwin,

Try this: unplug the SSD, boot with USB. After it booted into Debian, plug in the Sandisk SDD. Do you see the kernel recognizing and initializing the SSD ?

I am hoping the behavior is the same as we've seen with the Sandisk Readycache SSD. Eventhough u-boot failed to detect the identity of the SSD, Debian will detect it just fine. If that is the case, then it can be used as the Debian rootfs (but the kernel uImage and uInitrd have to be loaded by u-boot, so the /boot directory must reside on a USB drive).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/14/2015 01:28PM by bodhi.

Booting with USB then plug in SSD and Debian will detect it just fine.

Ok. This ssd goes back to the store.
Any advise which SSD >= 128gb does boot properly? Brand and type?