-mark
Mark Seger wrote:
When I run SystemImager on by brand new DL360s, it fails after the images are downloaded. Specifically, when it runs 'grub-install' it generates the following;
Probing devices to guess BIOS drives. This may take a long time. end_request: I/O error, dev 02:00 (floppy), sector 0 ide-floppy driver 0.99.newide hda: driver not present df: Warning: cannot read table of mounted filesystems df: Warning: cannot read table of mounted filesystems Could not find device for /boot: No found or not a block device
shortly thereafter the function find_grub_root gets called in Grub.pm which ultimately calls 'devfs_lookup' in Devfs.pm, looking for devices that match /ide|scsi|md/ in the 'smells_like_devfs' routine. To try and see why, I printed out the contents of /proc/partitions and found the devices in it had names that would never pass this test, specifically:
cciss/disc0/dics cciss/disc0/part1 cciss/disc0/part2 cciss/disc1/disc cciss/disc1/part1
does anyone have a clue what is going on here and what (if any) workarounds there might be to get past this? Since the partitions structure are getting named by the 'master' SI script which is being built by mkautoinstallscript, is this the actual root of the problem?
-mark
------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
