https://bugzilla.novell.com/show_bug.cgi?id=474879
User DOlsson@WEB.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=474879#c4
--- Comment #4 from Dennis Olsson 2009-02-11 11:44:12 MST ---
Created an attachment (id=271996)
--> (https://bugzilla.novell.com/attachment.cgi?id=271996)
Tar (-cjf) file containing: boot.msg lsmod lspci-nn messages
partitions-0before partitions-1after
Booting with
brokenmodules=pata_hpt37x,pata_hpt3x2n
results in disc order:
usb: sda
sil: sd[bcde]
hpt: hda, hdc, hdd !!!
meaning that the "1" = "/dev/hda1" and "" = "/dev/hdc1".
- Doing a "fsck -fn 1" => always results in OK.
- Doing a "fsck -f 1" => always results in OK.
- Doing a "fsck -fn 1" => always results in OK.
- Doing a "fsck -f 1" => always results in OK!!!
This works without any crashing!!
I can even do a
fsck -f[n] /dev/os103/root
of the LVMs that are stripped over the three discs!
But, unfortunately, the discs are now "hd*"s instead of "sd*"s!!
Do not know, if this is OK -- i.e. of the driver is good for the HighPoint
controller as for my purposes!!
I am sceptical about using this driver, just as it is not "good" for my system
I
have on the discs, that the discs "suddently" are "hd*"s instead of "sd*"s
(although I suppose, I could workaround this;-).
Anyway, I find it much more interessing to know, what is wrong with these
HighPoint drivers, and why they do not work.
Rebooting works here (naturally;-).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.