Tory M Blue wrote: > To end this story, since it kicked my behind and I put it down for a > bit. I have it working and none of this was a systemimager issue (for > the most part) > > Appears that my original non raid image contained the correct > /etc/blkid/blkid.tab file for standard disks, but it was not modified > when imaging a raid array (systemimager/configurator, may want to > think about doing something with this file!). It still had /dev/sd* > entries which caused issues when trying to boot (it would attempt to > fsck them, however they were mounted (ala the MD device)) and thus > were unavailable, so I couldn't get behind single user. > > So cleaning up the /etc/blkid/blkid.tab file cured all my heartache > and I have a easily imaged raid1 setup via systemimager (FC6), via a > non raid origin image. > > I'm happy (still playing with xen, but at least the raid 1 issue has > been put to bed) >
Interesting! I think we should automatically exclude this file when cloning an image, that means adding a new entry in /etc/systemimager/getimage.exclude In Ubuntu the file is called /etc/blkid.tab (so two entries at least). I'll do a test with ubuntu later to see if adding the exclusion breaks anything. Do you confirm that removing/cleaning the file _inside the image_ fixed the problem? Thanks for posting this info! -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
