Hard Disk Being Ide Not Scsi

[Thatch]

Lately my computer is freezing. E.g., I'm reading with Konqueror and that's it. I can only forcibly turn off the computer. Upon reboot I can't even get an OS to run. Not openSUSE or Windows. As openSUSE is loading the following eventually gets displayed and that's it.

drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver (pauses at this point for a while)
..............................Could not find /dev/disk/by-id/scsi-SATA_ST340016A_3HS56HLD-part5.
Want me to fall back to /dev/disk/by-id/scsi-SATA_ST340016A_3HS56HLD-part5? (Y/N)
y
Waiting for device /dev/disk/by-id/scsi-SATA_ST340016A_3HS56HLD-part5 to appear
..............................not found -- exiting to /bin/sh
sh: no job control in this shell
$[/b]

Usually I have to wait a period of time before I can try and see if openSUSE will boot properly. And when that happens I see quite a few "Recovering journal" messages.

I showed this to my father and he said the hard disks are IDE, not SCSI. I'm not knowledgeable about these things, but is this the problem? If so, how can I correct the situation?

[metal1633]

Lately my computer is freezing. E.g., I'm reading with Konqueror and that's it. I can only forcibly turn off the computer. Upon reboot I can't even get an OS to run. Not openSUSE or Windows. As openSUSE is loading the following eventually gets displayed and that's it.
Usually I have to wait a period of time before I can try and see if openSUSE will boot properly. And when that happens I see quite a few "Recovering journal" messages.

I showed this to my father and he said the hard disks are IDE, not SCSI. I'm not knowledgeable about these things, but is this the problem? If so, how can I correct the situation?
[/b]

10.2 uses libata for all drives. libata uses /dev/sda for the first harddisk instead of /dev/hda. etc etc.
If your drives are not SATA or SCSI but rather IDE drives then You can disable libata by booting with the following kernel parameter:

hwprobe=-modules.pata

If that works for you then add it to Grub.

That is IF the drives are NOT SATA or SCSI.

And also your problem could be something other.

[Thatch]

Thanks for the reply, I've made the changes and I'll wait and see if the problem is resolved. Hopefully.

[welan]

I,ve been having the same issue, but it started after i added a pata drive to box. Before when i only had the orignal sata drive it wasn't happening. The sata drive is setup as the primary and the pata drive is set as extended.
Do i need to change something in the bios to avoid this in the future?
Seems that it wants to boot from the pata drive not the sata drive.
As i said before the sata is set as primary and the pata is set as slave... :blink:

[metal1633]

I,ve been having the same issue, but it started after i added a pata drive to box. Before when i only had the orignal sata drive it wasn't happening. The sata drive is setup as the primary and the pata drive is set as extended.
Do i need to change something in the bios to avoid this in the future?
Seems that it wants to boot from the pata drive not the sata drive.
As i said before the sata is set as primary and the pata is set as slave... :blink:
[/b]

Yeah you may want to check the boot order in your bios.

[welan]

Done and done. seems ok now :unsure: