Bug 112076
Summary: | anaconda does not support HD upgrade with ISOs on single member of RAID set | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alik Widge <aswst16> | ||||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 1 | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2004-10-05 15:48:49 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
Alik Widge
2003-12-14 02:00:28 UTC
Created attachment 96513 [details]
Anaconda dump file.
I did review this trace briefly, and I think maybe the problem is one of
filesystems. The trace seems to think that the images are on an ext2 filesystem
on /dev/hda2, but that filesystem is actually ext3 last I checked.
Is hda2 part of one of the raid arrays on the system? Yes, hda2 is part of the RAID. I'm attaching the raidtab to help. Comment on attachment 96520 >Last login: Sat Dec 13 21:51:26 2003 from pittmed.medschool.pitt.edu >[alik@mdphd alik]$ cls >cls >bash: cls: command not found >[alik@mdphd alik]$ clr >clr >bash: clr: command not found >[alik@mdphd alik]$ clear >clear >[alik@mdphd alik]$ reset >reset >Erase is delete. >Kill is control-U (^U). >Interrupt is control-C (^C). >[alik@mdphd alik]$ cat /etc/raidtab >cat /etc/raidtab >raiddev /dev/md0 >raid-level 1 >nr-raid-disks 2 >chunk-size 64k >persistent-superblock 1 >#nr-spare-disks 0 > device /dev/hda1 > raid-disk 0 > device /dev/hdc1 > raid-disk 1 >raiddev /dev/md1 >raid-level 1 >nr-raid-disks 2 >chunk-size 64k >persistent-superblock 1 >#nr-spare-disks 0 > device /dev/hda2 > raid-disk 0 > device /dev/hdc2 > raid-disk 1 >raiddev /dev/md2 >raid-level 1 >nr-raid-disks 2 >chunk-size 64k >persistent-superblock 1 >#nr-spare-disks 0 > device /dev/hda5 > raid-disk 0 > device /dev/hdc5 > raid-disk 1 >raiddev /dev/md3 >raid-level 1 >nr-raid-disks 2 >chunk-size 64k >persistent-superblock 1 >#nr-spare-disks 0 > device /dev/hda6 > raid-disk 0 > device /dev/hdc6 > raid-disk 1 >raiddev /dev/md4 >raid-level 1 >nr-raid-disks 2 >chunk-size 64k >persistent-superblock 1 >#nr-spare-disks 0 > device /dev/hda7 > raid-disk 0 > device /dev/hdc7 > raid-disk 1 > >[alik@mdphd alik]$ Created attachment 96521 [details]
raidtab file from the system
We don't currently support using a single member of a RAID set as the source for a hard drive install as we have to do weird mount/umount magic for things at various points and once the RAID device has been started, we can't do that. So, in other words, the only known solution for this problem is to try to find a system that's got both broadband and a CD burner and burn the ISOs to CDs. If I do that (which I can, even though it's a hassle), is there anything else I should be aware of when trying to do an upgrade install on a RAID? That's the only caveat I can think of. At this point, not really planning on implementing support for doing this. |