HD Access Problem On Boot

This problem does not happen on every boot so I am confused about the cause. Here is the section of the boot log when it does not happen -


<6> 1.475099] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
<6> 1.475101] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
<6> 1.689008] usb 1-7.2: New USB device found, idVendor=054c, idProduct=0268
<6> 1.689010] usb 1-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6> 1.689012] usb 1-7.2: Product: PLAYSTATION(R)3 Controller
<6> 1.689013] usb 1-7.2: Manufacturer: Sony
<6> 1.783911] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:02.1/usb1/1-7/1-7.2/1-7.2:1.0/input/input2
<6> 1.783987] sony 0003:054C:0268.0001: input,hiddev96,hidraw0: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:02.1-7.2/input0
<6> 1.820249] ata1.00: HPA unlocked: 234439535 -> 234441648, native 234441648
<6> 1.820253] ata1.00: ATA-6: ST3120026A, 8.01, max UDMA/100
<6> 1.820255] ata1.00: 234441648 sectors, multi 16: LBA48
<6> 1.820272] ata1.01: ATAPI: PIONEER DVR-113NP, 1.01, max UDMA/66
<7> 1.820286] ata1: nv_mode_filter: 0x3f39f&0x3f39f->0x3f39f, BIOS=0x3f000 (0xc6c50000) ACPI=0x3f01f (20:30:0x1f)
<7> 1.820290] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc6c50000) ACPI=0x1f01f (20:30:0x1f)
<6> 1.842378] ata1.00: configured for UDMA/100
<6> 1.848197] ata1.01: configured for UDMA/66


Here is the section when it does-


<6> 1.474721] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
<6> 1.474723] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
<6> 1.688034] usb 1-7.2: New USB device found, idVendor=054c, idProduct=0268
<6> 1.688036] usb 1-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6> 1.688038] usb 1-7.2: Product: PLAYSTATION(R)3 Controller
<6> 1.688040] usb 1-7.2: Manufacturer: Sony
<6> 1.782691] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:02.1/usb1/1-7/1-7.2/1-7.2:1.0/input/input2
<6> 1.782767] sony 0003:054C:0268.0001: input,hiddev96,hidraw0: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:02.1-7.2/input0
<6> 1.872514] usb 1-7.1.1: new high speed USB device using ehci_hcd and address 5
<6> 2.036115] usb 1-7.1.1: New USB device found, idVendor=0424, idProduct=2228
<6> 2.036117] usb 1-7.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6> 2.036118] usb 1-7.1.1: Product: Flash Card Reader
<6> 2.036120] usb 1-7.1.1: Manufacturer: Generic
<6> 2.036121] usb 1-7.1.1: SerialNumber: 080131202378
<6> 2.109481] usb 1-7.1.4: new full speed USB device using ehci_hcd and address 6
<6> 2.259961] usb 1-7.1.4: New USB device found, idVendor=054c, idProduct=0268
<6> 2.259963] usb 1-7.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6> 2.259965] usb 1-7.1.4: Product: PLAYSTATION(R)3 Controller
<6> 2.259966] usb 1-7.1.4: Manufacturer: Sony
<6> 2.336242] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:02.1/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.0/input/input3
<6> 2.336300] sony 0003:054C:0268.0002: input,hiddev97,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:02.1-7.1.4/input0
<4> 6.674015] ata1: link is slow to respond, please be patient (ready=0)
<3> 11.519017] ata1: SRST failed (errno=-16)
<4> 16.719017] ata1: link is slow to respond, please be patient (ready=0)
<3> 21.564014] ata1: SRST failed (errno=-16)
<4> 26.764019] ata1: link is slow to respond, please be patient (ready=0)
<7> 52.621048] ata1.01: link status unknown, clearing UNKNOWN to NONE
<6> 52.643248] ata1.00: HPA unlocked: 234439535 -> 234441648, native 234441648
<6> 52.643251] ata1.00: ATA-6: ST3120026A, 8.01, max UDMA/100
<6> 52.643253] ata1.00: 234441648 sectors, multi 16: LBA48
<7> 52.643267] ata1: nv_mode_filter: 0x3f39f&0x3f39f->0x3f39f, BIOS=0x3f000 (0xc6c50000) ACPI=0x3f01f (20:30:0x1f)
<6> 52.665378] ata1.00: configured for UDMA/100
<5> 52.665458] scsi 0:0:0:0: Direct-Access ATA ST3120026A 8.01 PQ: 0 ANSI: 5
<7> 52.665558] ata2: port disabled. ignoring.
<7> 52.669358] sata_nv 0000:00:05.0: version 3.5


I have two 300Gb sata2 drives configured as a stripped raid one 120Gb PATA and one PATA DVDRW drive. This is mostly an annoyance because of the slow boot time since every thing seems to work fine otherwise. I never had this problem until I update SUSE 11.3>:( I have done a fresh install of 11.3 after that with no change. I also tried removing my playstation 3 controllers and I still have the problem -


<6> 1.474722] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
<6> 1.474724] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
<6> 1.627537] usb 1-7.1.1: new high speed USB device using ehci_hcd and address 4
<6> 1.791261] usb 1-7.1.1: New USB device found, idVendor=0424, idProduct=2228
<6> 1.791264] usb 1-7.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6> 1.791265] usb 1-7.1.1: Product: Flash Card Reader
<6> 1.791267] usb 1-7.1.1: Manufacturer: Generic
<6> 1.791269] usb 1-7.1.1: SerialNumber: 080131202378
<4> 6.674017] ata1: link is slow to respond, please be patient (ready=0)
<3> 11.519013] ata1: SRST failed (errno=-16)
<4> 16.719016] ata1: link is slow to respond, please be patient (ready=0)
<3> 21.564019] ata1: SRST failed (errno=-16)
<4> 26.764019] ata1: link is slow to respond, please be patient (ready=0)
<7> 52.621046] ata1.01: link status unknown, clearing UNKNOWN to NONE
<6> 52.659247] ata1.00: HPA unlocked: 234439535 -> 234441648, native 234441648
<6> 52.659251] ata1.00: ATA-6: ST3120026A, 8.01, max UDMA/100
<6> 52.659253] ata1.00: 234441648 sectors, multi 16: LBA48
<7> 52.659268] ata1: nv_mode_filter: 0x3f39f&0x3f39f->0x3f39f, BIOS=0x3f000 (0xc6c50000) ACPI=0x3f01f (20:30:0x1f)
<6> 52.681351] ata1.00: configured for UDMA/100
<5> 52.681437] scsi 0:0:0:0: Direct-Access ATA ST3120026A 8.01 PQ: 0 ANSI: 5
<7> 52.681564] ata2: port disabled. ignoring.


Any Ideas?

What about if you boot the Failsafe option?

Apart from the

<4> 6.674017] ata1: link is slow to respond, please be patient (ready=0)
<3> 11.519013] ata1: SRST failed (errno=-16)

lines that show when you say it is slow, I got the idea that the flash card reader is not connected in the first , but is in the two last (slow) ones. I do not know if that has anything to do with your problem, but it comes to mind.

Else I would say it is something hardware when one of the disks does not respond in a normal slice of time. In any case, I would make fresh backups (when you haven’t done this allready) and try to run disk diagnostics programs.

Very oldfashioned: shutdown the system, reconnect the disks’ cables. See what happens if the DVD/CD device is disconnected.

It hangs with a failsafe boot as well, but less often.

On 2010-10-20 05:06, 2fry wrote:

> I have two 300Gb sata2 drives configured as a stripped raid one 120Gb
> PATA and one PATA DVDRW drive. This is mostly an annoyance because of
> the slow boot time since every thing seems to work fine otherwise. I
> never had this problem until I update SUSE 11.3>:( I have done a fresh
> install of 11.3 after that with no change. I also tried removing my
> playstation 3 controllers and I still have the problem -

I would try to install 11.2 again and see it if the problem persist there - so as to know if it
software or hardware. If it is software → bugzilla.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I re-seated all the drive cable but no luck.

I would try to install 11.2 again and see it if the problem persist there - so as to know if it
software or hardware. If it is software → bugzilla.

I do not know how to do that without wiping the drive and starting over. Also, where would I download the DVD iso file for 11.2? I agree that it is a worthy experiment and if it eliminates the boot problem I would just stay with 11.2.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)[/QUOTE]

On 2010-10-25 00:36, 2fry wrote:
>
>> I would try to install 11.2 again and see it if the problem persist
>> there - so as to know if it
>> software or hardware. If it is software → bugzilla.
>
> I do not know how to do that without wiping the drive and starting
> over.

Obviously. But as you say that you wiped and installed 11.3 again, a second time… it is just one
time more. If the problem is big enough for you, try.

Anyway, I always test the next version in all machines before committing to install. Some versions
do not work.

> Also, where would I download the DVD iso file for 11.2?

Same place as for 11.3. As for any opensuse distro and version, from our site. Where else? >:-o

> I agree
> that it is a worthy experiment and if it eliminates the boot problem I
> would just stay with 11.2.

That’s the point… if you have problem booting and you get tired of that…


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Well I tried a long experiment. I wiped the drive and installed Open Suse 11.0 and then did all the updates to 11.2. I was tring to solve some other problems as well. I do not have the boot problem any more so I will stick to 11.2 until they solve the drive access problem in 11.3. Turns out that when I have the boot problem a cannot access my CD-RW (big problem). I am not sure how to file a bug report but there seems to be some problem with the Nvidia nForce 570-SLI driver tring to access my Pioneer DVR-1910LS. The motherboard I am using is the Gigabyte GA-M57SLI-S4 Rev. 2.0.

Good news, I found the cause. When I upgrade the kernel from 2.6.31.5-0.1 to 2.6.31.14-0.4 I have disk access problems. Does any one know how to report a kernel bug?

So, I figured out how to roll back my kernel, however, every time I do a software update Yast2 updates my kernel. Is there any way to tell Yast2 to keep the kernel?

Right click the kernel you want to keep in Software Manager
Select Protect do Not Modify
Apply

Thank you caf4926, I should have noticed that. Nice to know it is a simple solution.

On 2010-11-12 06:36, 2fry wrote:
>
> So, I figured out how to roll back my kernel, however, every time I do a
> software update Yast2 updates my kernel. Is there any way to tell Yast2
> to keep the kernel?

Unselect the kernel in the YOU window. Never do automatic updates, always
check. Or mark the kernel patch as “taboo”.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)