Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 90649
Summary: | can't --useexisting or --noformat raid device | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | Alexandre Oliva <aoliva> | ||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | beta1 | CC: | aoliva, chris.ricker | ||||
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: | 2003-10-25 20:26:01 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 100644 | ||||||
Attachments: |
|
Description
Alexandre Oliva
2003-05-11 23:20:18 UTC
Still present in Severn (beta1) You shouldn't have to specify the devices that make up the raid for noformat, iirc. Just raid /oldboot --noformat --device=md0 (And also don't define raid.5, etc) If you do that, does it work? The closest I tried on Severn was this: raid /l/root/boot --noformat --device=md0 --level=RAID1 --fstype ext3 and it didn't work just the same. Could --level and --fstype be causing problems? I'll try without them when I get a chance. Quite possibly -- how does it look with test2 if you leave those off? I can't test this any more, at least for now, because my laptop's RAID devices all have one replica in an internal disk and one in an external disk, which the installer can't cope with (see bug 105602) Ok, I managed to recreate a set up in which I can duplicate this. raid /oldboot --noformat --device=md5 doesn't work. The installer halts saying: Unable to locate raid device None to use for /oldboot :-( Created attachment 95305 [details]
Get raid --device all the way to partRequest.device
The problem was that the --device passed to raid never made it to the
partRequest. This patch fixes it. Anaconda got all the way to `reading
package information' after this patch, with a kickstart file that would
formerly cause it to error out as described.
Below is committed and should have the same effect. I just avoid introducing another variable and continue to allow the device to be passed as just an int (as well as only setting the device on preexisting just to be paranoid) RCS file: /cvs/devel/anaconda/kickstart.py,v retrieving revision 1.212 diff -u -u -r1.212 kickstart.py --- kickstart.py 16 Oct 2003 16:46:38 -0000 1.212 +++ kickstart.py 21 Oct 2003 16:38:29 -0000 @@ -1044,6 +1044,8 @@ if uniqueID: request.uniqueID = uniqueID + if preexist and raidDev is not None: + request.device = "md%s" %(raidDev,) self.addPartRequest(id.partitions, request) It is actually not entirely equivalent, in that it doesn't support raid devices that are not named md#, but I guess we don't care. I'll give this a try soon, along with the fix for 107518. Thanks! anaconda won't work with raid devices not named md# anyway :) Yeah, I remember that from my very first contact with raid in anaconda, when I had absolutely no clue it was supposed to be named md# :-) I thought explicitly naming a raid device without following this convention, in kickstart installs, might still work, which was why I did it the way I did, but it's not that I really care about that any more. Thanks, verified. |