Bug 209103
Summary: | Problem with install RHEL on IBM HS20 + FC Storage (EMC) | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Andrzej Nakonieczny <anakonieczny.bugzilla-redhat> | ||||
Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-10-01 19:15:05 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Andrzej Nakonieczny
2006-10-03 08:23:05 UTC
Created attachment 137630 [details]
debug file from anaconda
I looked for similar bugs like my and I found #201235. I see that it's closed now. I tried to replace part of anaconda to check if it helps in my situation. I got new version of dmraid.py from CVS (revision 1.19) and I replaced this one in minstg2.img and stage2.img. Now installer goes on but can't see multipath device. I don't know why but now anaconda try to access direct storage devices like sda, sdb, sdc and sdd (all these devices are the same one hardware disk on emc storage but sees trough different fc path). Two from these devices are unaccesable (sdb and sdd if I remember correctly) what's alerted by anaconda. If I choose (in anacodna's window box) to ignore these errors anaconda goes on and system is installed. But there still is something wrong because disk seems to be empty. On the end of installation grub failed on root hd(0,0) command. I switched to text console and I tried to list content of disk but it looks empty. There is not any partition even though these partitions are mounted. It's very strange. In /proc/partitions I can see sda disk with 2 partitions (sda1 and sda2) but fdisk or parted shows empty list. I tried to run partprobe (in chroot on /mnt/sysimages) to refresh partition table but without results. It's look like something is erased existing partition in time of installation. Is it possible? After boot again from cdrom in rescue mode I can't see anything on that disk. Any ideas? Is this still a problem in 5.1? I know a lot of work went into storage there so this could be fixed up. (In reply to comment #3) > Is this still a problem in 5.1? I know a lot of work went into storage there so > this could be fixed up. No, it doesn't if you add 'mpath' to boot parameters before install. But if I remeber correctly the same problem still exists when you install on FC storage with multipath and multiple disks defined. Now I haven't time to check it again so when I have to install a new system I'm adding only one disk (still with multipath) and after installation I adding next one. |