In my case the HPA fix with hdparm was done on one of the physical
drives of the array, like /dev/sda in your setup. However, I only had 2
drives in raid.
You can probably check the HPA settings on each of those drives and see
whether they are inconsistent or messed up by the Linux kernel. Beware
phdb: I am quite sure that hdparm will not work on a raid array
directly, because it is not a physical drive. Your first try seems
plausible if /dev/sde was the physical drive. Probably the HPA
modification of the live CD was invalid. I never tried raid 10 however.
On my machine a total "cold boot
Because the HPA is now spanning my entire array, to reproduce the
original problem now I should back up 1TB data from three operating
systems to some other place which I do not have, format everything,
install Windows on the RAID, put in the live CD and test the bug, then
pray that restoring everyt
Jouke74 you can probably fix it by installing Windows on a separate 3rd
drive, starting the Intel RAID tool and selecting "recover volume" on
the failed HDD pair. Maybe you can try dmsetup to re-create the arrays
as well, but no idea whether it works.
--
booting live cd breaks intel matrix raid
h
I can confirm that indeed HPA was the problem in my case. dmesg log
showed the "HPA locked" message in the libata part for the ata0 drive.
This forced value made my arrays accessible until the next hard boot.
Only /dev/sda was affected. Finally, I got the total sector num with the
live CD with
# h
Two related bugs:
https://bugs.launchpad.net/ubuntu/+bug/141435
https://bugzilla.novell.com/show_bug.cgi?id=328388
These turned my attention to HPA issues.
>From hdparm man page:
[...] The difference between these two values indicates how many sectors
of the disk are currently h
I was a bit early about that fix.
Now what I have is that the everything works perfectly until a *hard*
power-off (cold boot, e.g. when the computer is entirely turned off).
Then the drives are again marked "offline member".
It can be fixed by simply booting into the live CD, not touching
anythin
Looks like I found a fix by messing around (which I do not understand
why it works).
I became aware that the metadata had quite different content on both
drives. Earlier when I got to the "offline member" screen in BIOS, I
marked the second drive as non-RAID, then the first drive became "live"
but
It is indeed opensuse 11.1 release. Tried both the installation DVD and
the live cd - according to distrowatch, it has kernel 2.6.27.7 (64-bit
version).
--
booting live cd breaks intel matrix raid
https://bugs.launchpad.net/bugs/383001
You received this bug notification because you are a member o
One more: I can confirm that the bug exists in SuSE 11.1 as well on this
config, so it must be in something common. SuSE breaks my onboard lan as
well - at least Ubuntu does not do that ;)
--
booting live cd breaks intel matrix raid
https://bugs.launchpad.net/bugs/383001
You received this bug not
Here is a more detailed casper.log (with debug=). It is not the actual
boot when the spoil happened but one after.
** Attachment added: "casper.log"
http://launchpadlibrarian.net/27436444/casper.log
--
booting live cd breaks intel matrix raid
https://bugs.launchpad.net/bugs/383001
You receive
Public bug reported:
Ubuntu 9.04 64-bit live CD, kernel 2.6.28.11.15
Hardware: Intel i720, GA-EX58-UD5 motherboard (ICH10R), 6GB RAM
2x500GB HDD in Intel matrix RAID dual configuration: 250GB in RAID1 mirroring,
rest is RAID0 striping. Windows XP64 is installed on a 150GB partition of RAID1
driv
** Attachment added: "logs.tgz"
http://launchpadlibrarian.net/27435944/logs.tgz
** Tags added: livecd
** Tags removed: cd live
--
booting live cd breaks intel matrix raid
https://bugs.launchpad.net/bugs/383001
You received this bug notification because you are a member of Ubuntu
Bugs, which
13 matches
Mail list logo
