Bug 592090
|
Description
Aaron Gee
2010-05-13 20:01:05 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Please attach /tmp/syslog, /tmp/anaconda.log, and /tmp/storage.log to this bug report. Thanks. Created attachment 413937 [details]
/root/install.log.syslog
Created attachment 413938 [details]
/root/install.log
No /tmp log files were on my system (I went back UNDID the raid and then continued with the install).
No /tmp log files were on my system (I went back UNDID the raid and then continued with the install). In my /tmp I have some sosreport-servers files. Should I upload these as well? Aaron, Could you reproduce the original problem, and then when at the screen which only shows the 1 raid set, switch to tty2 (ctrl + alt + f2) And do: dmraid -ay -t -vvv > log And attach the resulting log file here ? (you can use scp to get the file out of the installer environment). While at it please also collect /tmp/syslog and attach it here too. Thanks, Hans Created attachment 414282 [details]
results of dmraid -ay -t -vvv
results of dmraid -ay -t -vvv as per request
Created attachment 414283 [details]
/tmp/syslog at point in install where drives are shown
/tmp/syslog as per request.
Ok, so dmraid only recognizes your 2 normal harddisks as part of a BIOS RAID set and even there I wonder if it is finding the correct metadata as it finds Promise RAID metadata, and I don't believe you have a promise controller in your system ? My current hunch is that dmraid is not recognizing the dmraid metadata used by your BIOS RAID, and that the 2 regular disks used to be part of a promise RAID set once upon a time and it is using that data now. So I'm moving this over the dmraid and keeping myself in the CC. Could you collect the following data to help out Heinz (the dmraid maintainer): 1) Tell us what sort of Firmware RAID you are using (nvidia / intel / jmicron or ...) 2) For each disk (after configuring it as part of a RAID set in the RAID BIOS) do: dd if=/dev/sdX of=sdX-begin.dump bs=1M count=1 dd if=/dev/sdX of=sdx-end.dump bs=1M count=4 skip=xxxx Where by skip needs to be such a value that dd runs of the end of the disk and thus the resulting dump is smaller then 4MB (and larger then 1MB) And then attach the dumps here. 3 items 1. None of the drives had ever been used in any system, the are literally brand new just out of the packaging. 2. The RAID controller is part of the AMD SB850 southbridge, while it "looks and feels" like promise, I believe it is AMD specific and supports RAID 0,1,5,10 3. Is it possible to manually create MD devices and install on them, and or manually handle the partitioning schema? I did not find such an option when I did the installation which is frustrating in my situation where I was trying to test a mixed SSD/Conventional disk environment for virtualization. The default disk arrangement chosen by the installer worked - but I'd like some more flexibility. I will get the dumps later and attach. (In reply to comment #12) > 3 items > > 1. None of the drives had ever been used in any system, the are literally brand > new just out of the packaging. > Thx, that is useful info. > 2. The RAID controller is part of the AMD SB850 southbridge, while it "looks > and feels" like promise, I believe it is AMD specific and supports RAID > 0,1,5,10 > And yet more useful info :) > 3. Is it possible to manually create MD devices and install on them, and or > manually handle the partitioning schema? I did not find such an option when I > did the installation which is frustrating in my situation where I was trying to > test a mixed SSD/Conventional disk environment for virtualization. The default > disk arrangement chosen by the installer worked - but I'd like some more > flexibility. > Yes it is possible to use a custom disklayout, when asked if you want to remove pre-existing linux / entirely clear disks or use free space you can also choose custom partitioning, from there you can create mdraid partitions and then on top of those partitions mdraid sets. Created attachment 415167 [details]
dmesg from anaconda prompt during install
Created attachment 415169 [details]
lspci from anaconda prompt
Created attachment 415171 [details]
dd dump of the beginning sda a corsair SSD
Created attachment 415172 [details]
dd dump of the end of sda a corsair SSD
Created attachment 415173 [details]
dd dump of the beginning of sdb a corsair SSD
Created attachment 415174 [details]
dd dump of the end of sdb a corsair SSD
Created attachment 415177 [details]
dd dump of the beginning sdc a Seagate Barracuda 7200.12 750G
Created attachment 415178 [details]
dd dump of the end of sdc a Seagate Barracuda 7200.12 750G
Created attachment 415179 [details]
dd dump of the beginning sdd a Seagate Barracuda 7200.12 750G
Created attachment 415180 [details]
dd dump of the end of sdd a Seagate Barracuda 7200.12 750G
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. It has been denied for the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** (In reply to comment #17) > Created attachment 415172 [details] > dd dump of the end of sda a corsair SSD This looks like Promise metadata in an unsupported offset on the disk, hence you can't use them as BIOS RAID, just mdraid. |