10.10 LiveCD fails install the bootloader on RAID

[rtrask]

Does any one know if the fix ever made it in to 10.10 for the grub install as discussed in this link? http://ubuntuforums.org/showthread.php?t=1573192&page=7

If so, I think that there are still issues. Perhaps it is my configuration, but it seems like it should work.

Here is my set up:
Intel S5500HCV dual CPU 5520
latest BIOS
software raid 3 Arrays
RAID 0 - configured as boot 1 SSD 90G 3 partitions Windows 7 installed first 2, 10.10 installed on 3rd
RAID 0 - 2 158 gig disks 2 partitions swap first partition, and remainder /opt
RAID 1 - 2 1T drives 1 partition /home

(an aside: My thinking is to use SSD for the software, and mirrored disks for user data, and the raid 0 with swap so I don't waste the limited SSD for swap that will probably never be used. The of the raid 0 /opt for transient data like video that I am working on)

This is the process that I followed to install


Loaded Windows 7 - create 50 G partition for windows leave remainder for linux -- no issues
load live CD to try, then in console do a "sudo dmraid -ay" (the install see the raid arrays asks to install raid software, but does not activate the raid arrays. what's up with that)
click install and go through normal steps until partition
I do manual partition, create 3rd partition on SSD format EXT4 set as root
create partitions on other 2 disks as described above
set boot device to /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0 which is the device for the first array containing the SSD
let it rip

The rest of the install is uneventful until the grub install fails. I've tried mounting the intall on /target/ and chroot to it. and then

root@ubuntu:/# grub-install --root-directory=/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
My problem seems very similar to the one described in the link above. The fact hat it is closed would lead me to believe that the patch was incorporated in 10.10 when it went GA, but maybe not. Any ideas?

I have attached the RESULTS.txt file from running boot_info_script055.sh

[rtrask]

Update :

I installed 10.04 (Lucid Lynx) using the alternate installer, and ran into the same issue

[ronparent]

Your results.txt is not viewable.

Have you tried the live cd two step approach to grub install which involves 1st mounting your partition to /mnt and 2nd installs the grub to your boot raid (/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0 )? This has been my 1st resort and has always worked for me (but is not necessarily surefire), You can verify that the target filesystem is properly mounted at /mnt.

Note: Does a space actually exist between the 2 and the 8 above (that doesn't look kosher)?

[rtrask]

Hi RonParent,

Thanks for your response.

Yes I have tried the 2 step


Have you tried the live cd two step approach to grub install which involves 1st mounting your partition to /mnt and 2nd installs the grub to your boot raid (/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0 )?

Yes that was the first thing I tried, and you can see the result from my first post.


The rest of the install is uneventful until the grub install fails. I've tried mounting the intall on /target/ and chroot to it. and then
root@ubuntu:/# grub-install --root-directory=/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.

I got the exact same result if I did a chroot first or not.

Note: Does a space actually exist between the 2 and the 8 above (that doesn't look kosher)?

No the space does not exist, it is an artifact om me cutting and pasting to the web page.


Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Windows is installed in the MBR of /dev/sda
=> No boot loader is installed in the MBR of /dev/sdb
=> No boot loader is installed in the MBR of /dev/sdc
=> No boot loader is installed in the MBR of /dev/sdd
=> Windows is installed in the MBR of
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
=> No boot loader is installed in the MBR of
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8
=> No boot loader is installed in the MBR of
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0

sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy

sda2: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy

sda3: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy

sdb1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy
mount: /dev/sdb1 already mounted or sdb1 busy

sdc1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy
mount: /dev/sdb1 already mounted or sdb1 busy
mount: /dev/sdc1 already mounted or sdc1 busy

sdd1: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

sdd2: __________________________________________________ _______________________

File system: ddf_raid_member
Boot sector type: -
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy
mount: /dev/sdb1 already mounted or sdb1 busy
mount: /dev/sdc1 already mounted or sdc1 busy
mount: unknown filesystem type 'ddf_raid_member'

ddf1_4c5349202020202080862925000000004711471100002 8a01: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /bootmgr /Boot/BCD

ddf1_4c5349202020202080862925000000004711471100002 8a02: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files/dirs: /Windows/System32/winload.exe /wubildr.mbr
/ubuntu/winboot/wubildr.mbr /wubildr
/ubuntu/winboot/wubildr /ubuntu/disks/root.disk
/ubuntu/disks/swap.disk

ddf1_4c5349202020202080862925000000004711471100002 8a02/Wubi: __________________________________________________ _______________________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy
mount: /dev/sdb1 already mounted or sdb1 busy
mount: /dev/sdc1 already mounted or sdc1 busy
mount: unknown filesystem type 'ddf_raid_member'
mount: unknown filesystem type ''

ddf1_4c5349202020202080862925000000004711471100002 8a03: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.10
Boot files/dirs: /etc/fstab

ddf1_4c5349202020202080862925000000004711471100003 2c81: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

ddf1_4c5349202020202080862925000000004711471100003 cf01: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

ddf1_4c5349202020202080862925000000004711471100003 cf02: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

sde: __________________________________________________ _______________________

File system: ddf_raid_member
Boot sector type: -
Boot sector info:
Mounting failed:
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
fuse: mount failed: Device or resource busy
mount: /dev/sda3 already mounted or sda3 busy
mount: /dev/sdb1 already mounted or sdb1 busy
mount: /dev/sdc1 already mounted or sdc1 busy
mount: unknown filesystem type 'ddf_raid_member'
mount: unknown filesystem type ''
mount: unknown filesystem type 'ddf_raid_member'

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 90.0 GB, 90028302336 bytes
255 heads, 63 sectors/track, 10945 cylinders, total 175836528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 206,847 204,800 7 HPFS/NTFS
/dev/sda2 206,848 104,857,599 104,650,752 7 HPFS/NTFS
/dev/sda3 104,857,600 173,826,047 68,968,448 83 Linux


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdb1 63 1,951,158,509 1,951,158,447 83 Linux


Drive: sdc ___________________ __________________________________________________ ___

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdc1 63 1,951,158,509 1,951,158,447 83 Linux


Drive: sdd ___________________ __________________________________________________ ___

Disk /dev/sdd: 164.7 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders, total 321672960 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdd1 63 50,331,644 50,331,582 82 Linux swap / Solaris
/dev/sdd2 50,331,645 640,607,939 590,276,295 83 Linux

/dev/sdd2 ends after the last sector of /dev/sdd

Drive: ddf1_4c5349202020202080862925000000004711471100002 8a0 ___________________ __________________________________________________ ___

Disk /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0: 89.0 GB, 88999985152 bytes
255 heads, 63 sectors/track, 10820 cylinders, total 173828096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a01 * 2,048 206,847 204,800 7 HPFS/NTFS
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a02 206,848 104,857,599 104,650,752 7 HPFS/NTFS
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a03 104,857,600 173,826,047 68,968,448 83 Linux


Drive: ddf1_4c5349202020202080862925000000004711471100003 2c8 ___________________ __________________________________________________ ___

Disk /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8: 999.0 GB, 998999326720 bytes
255 heads, 63 sectors/track, 121454 cylinders, total 1951170560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c81 63 1,951,158,509 1,951,158,447 83 Linux


Drive: ddf1_4c5349202020202080862925000000004711471100003 cf0 ___________________ __________________________________________________ ___

Disk /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0: 328.0 GB, 327998767104 bytes
255 heads, 63 sectors/track, 39876 cylinders, total 640622592 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf01 63 50,331,644 50,331,582 82 Linux swap / Solaris
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf02 50,331,645 640,607,939 590,276,295 83 Linux


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/dm-7 c10762d7-89c7-4ee4-b40b-627d67d9794d swap
/dev/loop0 squashfs
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a01 EABCD6A7BCD66E17 ntfs System Reserved
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a02 2814EBB114EB7FE4 ntfs
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a03 c52e0fc4-96bd-4014-b82d-58baa39c47da ext4
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0: PTTYPE="dos"
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c81 a3ced5d8-923a-46b9-82fe-636a09374124 ext3
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8: PTTYPE="dos"
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf01 c10762d7-89c7-4ee4-b40b-627d67d9794d swap
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf02 ff8a743c-3f26-44dd-be3e-b4565b74d134 ext3
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0: PTTYPE="dos"
/dev/sda1 EABCD6A7BCD66E17 ntfs System Reserved
/dev/sda2 2814EBB114EB7FE4 ntfs
/dev/sda3 c52e0fc4-96bd-4014-b82d-58baa39c47da ext4
/dev/sda LSI ۠)% ddf_raid_member
/dev/sdb1 a3ced5d8-923a-46b9-82fe-636a09374124 ext3
/dev/sdb LSI ۠)% ddf_raid_member
/dev/sdc1 a3ced5d8-923a-46b9-82fe-636a09374124 ext3
/dev/sdc LSI ۠)% ddf_raid_member
/dev/sdd1 c10762d7-89c7-4ee4-b40b-627d67d9794d swap
/dev/sdd2 LSI ۠)% ddf_raid_member
/dev/sdd LSI ۠)% ddf_raid_member
/dev/sde LSI ۠)% ddf_raid_member

=============================== "ls -R /dev/mapper/" output: ===============================
/dev/mapper:
control
ddf1_4c5349202020202080862925000000004711471100002 8a0
ddf1_4c5349202020202080862925000000004711471100002 8a01
ddf1_4c5349202020202080862925000000004711471100002 8a02
ddf1_4c5349202020202080862925000000004711471100002 8a03
ddf1_4c5349202020202080862925000000004711471100003 2c8
ddf1_4c5349202020202080862925000000004711471100003 2c81
ddf1_4c5349202020202080862925000000004711471100003 cf0
ddf1_4c5349202020202080862925000000004711471100003 cf01
ddf1_4c5349202020202080862925000000004711471100003 cf02

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a03 / ext4 (rw,relatime,errors=remount-ro,barrier=1,data=ordered)
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf02 /home ext3 (rw,relatime,errors=continue,barrier=0,data=ordere d)
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c81 /opt ext3 (rw,relatime,errors=continue,barrier=0,data=ordere d)
/dev/scd0 /cdrom iso9660 (ro,noatime)


====== ddf1_4c5349202020202080862925000000004711471100002 8a03/etc/fstab: ======

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a03 / ext4 errors=remount-ro 0 1
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf02 /home ext3 defaults 0 2
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c81 /opt ext3 defaults 0 2
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf01 none swap sw 0 0

ddf1_4c5349202020202080862925000000004711471100002 8a03: Location of files loaded by Grub:


54.2GB: boot/initrd.img-2.6.35-22-generic
60.3GB: boot/vmlinuz-2.6.35-22-generic
54.2GB: initrd.img
60.3GB: vmlinuz
=========================== Unknown MBRs/Boot Sectors/etc =======================

Unknown BootLoader on ddf1_4c5349202020202080862925000000004711471100002 8a02/Wubi

00000000 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 |0000000000000000|
*
00000200

[psusi]

You are inserting a space in the name where there isn't one, and you need to mount the target fs somewhere and use that instead of / for --root.

[rtrask]

Hi Psusi
No I did not insert the space, that was a copy/paste error when I created the forum entry. I have tried to run the the command without doing the chroot, with the exact same result, both on 10.04, and on 10.10. i.e. the first thing that I did prior to doing the chroot was to try and run.

root@ubuntu:/# grub-install --root-directory=/target/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.




Note: Does a space actually exist between the 2 and the 8 above (that doesn't look kosher)?
No the space does not exist, it is an artifact om me cutting and pasting to the web page.

[ronparent]

ddf1_4c5349202020202080862925000000004711471100002 8a03: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.10
Boot files/dirs: /etc/fstab

The above boot files look wrong - all the files required to boot should be shown. Why don't you mount that partition and verify that the boot files are present (ie /boot, /boot/grub)?

[rtrask]

I'm not sure why the space keeps showing up, I have tried to edit the page and remove it but when I save it it is always there

[ronparent]

I see what you mean - the space shows up in the generation of results.txt. Besides that, this error mesage:

Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
seem to indicate that somehow needed system files didn't get written to the install. Why? In any event they seem required to be included in the install to permit writing grub 2 to the /boot/grub location.

[ronparent]

The space is apparently an artifact of this site. Copying and pasting to a text file doesn't produce a space at that location!!!

[rtrask]

I have worked at this some more, and I am convinced that the issue is with grub-probe failing because of the SW RAID. I went into the bios, and turned it off, and grub-install worked fine. But of course grub could not find the /boot when RAID was turned back on.

I think it possible, that if I could supply a device.map file for grub-install --grub-probe=FILE option that I could get around the issue that stops it, but I have not been able to find out what the contents of that file should be.

grub-probe works for some of its options but fails on architecture & fs things. I think that there must be a bug, at least for my hardware.

[psusi]

Disabling the bios support has no effect on Ubuntu; it will still use the raid array if it finds the signatures.

I think the problem is the odd device name of your array. Other types end up with names like nvidia_ahhfci... with no numbers in them. It looks like the DDF format doesn't and since the name has numbers in it, it becomes tricky to identify where the name of the disk ends and where the partition number begins. Upstream has moved to inserting a 'p' in the name to separate the base disk name from the partition number, but Ubuntu still has a patch to revert that behavior.

I have a modified version at home that puts it back in. I will try to upload it to my PPA tonight for you to test and see if that fixes it.

[ronparent]

At this point I am completely confused as to where the /boot is located and where you are trying to place the boot loader. But I think I do know this - the likeliest places you are trying to install grub to is one of the raid0 locations. Since they are raid0 in bios those locations would not be accessibly if raid is turned off in bios. This makes me suspect that the raid0 location you are successfully installing grub 2 to with the raid turned off in bios is a software raid not a fakeraid! Correct me if I'm wrong. If that were the case then the raid is bios should probably be turned off on all you raids unless one or two of them are actually fakeraid. In any case, if you are mixing fakeraid with software raid your machine must be as mixrd up as I am.

[rtrask]

Sorry for the long pause in getting back to this. I have not been idle, but distracted by a bunch of other things including my real job. :)

As a result this is a long post, sorry.

Let me see if I can answer some questions.


psusi says --
Disabling the bios support has no effect on Ubuntu; it will still use the raid array if it finds the signatures.

I think the problem is the odd device name of your array. Other types end up with names like nvidia_ahhfci... with no numbers in them. It looks like the DDF format doesn't and since the name has numbers in it, it becomes tricky to identify where the name of the disk ends and where the partition number begins. Upstream has moved to inserting a 'p' in the name to separate the base disk name from the partition number, but Ubuntu still has a patch to revert that behavior.

I have a modified version at home that puts it back in. I will try to upload it to my PPA tonight for you to test and see if that fixes it.

You may be right that the issue is the strange / extremely long device names of the raid array. I'm not sure what causes that perhaps the LSI BIOS?? I don't know. I have a ASUS MB, that I had the same CPU's and disks in, and it also had the long device names for the raid arrays. It also had LSI BIOS for configuring the RAID array. I could not get that system to boot either in Windows 7 or in Ubuntu properly with the SSD in a RAID array. I got around that issue by first enabling RAID in BIOS, then configuring the other RAID arrays, then turning off the RAID in BIOS. Windows 7 honored the RAID arrays, and if I added "dmraid -ay" to the initramfs configuration (initramfs-tools/hooks & scripts ... see Ubuntu 5.10: Reconfigure Initramfs for RAID (https://help.ubuntu.com/community/FakeRaidHowto) to get Ubuntu to recognize the raid arrays, but I got it to work. Now with the Intel MB. Windows boots fine with the SSD in a RAID array by it'self but I have been running into this brick wall on getting grub to install for Ubuntu. I have been wondering if the long / strange device names are why I have to monkey with initram-fs, and run "dmraid -ay" by hand prior to attempting to install Ubuntu.

I'm not sure how to gain access to your PPA (sorry for the stupid question), but I think it is possible this might help, because I notices when I installed Open SUSE, that "p" occurred before the partition number in the RAID array names.


ronparent -- says
At this point I am completely confused as to where the /boot is located and where you are trying to place the boot loader. But I think I do know this - the likeliest places you are trying to install grub to is one of the raid0 locations. Since they are raid0 in bios those locations would not be accessibly if raid is turned off in bios. This makes me suspect that the raid0 location you are successfully installing grub 2 to with the raid turned off in bios is a software raid not a fakeraid! Correct me if I'm wrong. If that were the case then the raid is bios should probably be turned off on all you raids unless one or two of them are actually fakeraid. In any case, if you are mixing fakeraid with software raid your machine must be as mixrd up as I am.

Well I'm kind of confused by what you are suggesting (no offense) Maybe I can clear things up by detailing exactly how I set it up step by step.


I plugged the disks into the system, turned it on and went into the system BIOS, set the mass storage device to RAID and set the first boot device to (RAID/DVD). Then when the LSI configuration BIOS came up, I went into it wiped out all existing configuration, defined the raid arrays with the single SSD disk in the first RAID array as RAID-0, 2 1T drives in the second raid array as RAID-1 and 2 158 G disks as in a third RAID array as RAID-0. I made the first RAID-0 device with a single disk (the SSD) as the boot device, and formatted all 3 raid arrays.
I then installed Windows 7, there were no partitions. I configured windows to create a 50 Gig partition to install into on the SSD. The Windows 7 installation created an additional 100 Meg partition, and installed in the remaining 50 GIG.
Because I have run into issues before with gparted on the 10.04 version of Ubuntu, I used a Live CD from 9.04 and booted into "try" mode. I then dropped into a terminal window and ran "sudo dmraid -ay" to bring bring up the raid arrays. Then I ran gparted which saw all three devices, and configured a partition on the SSD to hold Ubuntu, and a swap partition on the second RAID-0 device. I also created the other partitions on the other disk as can be seen from the output of boot info.


Finally, this is what I have done on my own in the interim. There are a couple of different threads and I apologize in advance for the adding to the confusion of an already long post.


Ubuntu -- I played around with the grub-probe utility which I believe is the component which is having issues. If I run "grub-probe /boot -t drive" it returns a valid response pointing to the raid array. If I run "grub-probe /boot -t device" it returns "/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0" as one would expect. But when I run "grub-probe /boot -t fs" it fails with "/usr/sbin/grub-probe: error: no such disk." which is the same error message that I get for "grub-probe /boot -t abstraction" or "grub-probe /boot -t partmap"

As an experiment I went into the BIOS, and turned off the software raid. With raid turned off grub 2 installed with out a hitch. the problem was that when I turned RAID back on grub would try to start, but then could not find /boot. So it dropped into command line mode. I had hoped that I might be able to play around with the grub configuration a bit to tell it how to find the /boot directory, but was ultimately unsuccessful.

Open SUSE -- Open SUSE installs with no problem. So I think a problem must have been introduced into the grub-probe that comes with Ubuntu. I want to get Ubuntu running, and I think I will uninstall Open SUSE and try again with Ubuntu. If that fails, I think what I can do is to leave Ubuntu on my SSD without installing grub, then install open SUSE on my striped raid drive, to see if Open SUSE will detect it and give me the option to boot it from grub.

[psusi]

As an experiment I went into the BIOS, and turned off the software raid. With raid turned off grub 2 installed with out a hitch. the problem was that when I turned RAID back on grub would try to start, but then could not find /boot. So it dropped into command line mode. I had hoped that I might be able to play around with the grub configuration a bit to tell it how to find the /boot directory, but was ultimately unsuccessful.


This does not make any sense. As I said before, disabling the raid in the bios has no effect on Ubuntu. What do you mean grub installed without a hitch? Did you install it to the raid device or directly to sda?

You can add my ppa by running sudo apt-add-repository ppa:psusi/ppa then upgrade dmraid.

[rtrask]

This does not make any sense. As I said before, disabling the raid in the bios has no effect on Ubuntu. What do you mean grub installed without a hitch? Did you install it to the raid device or directly to sda?

I installed it to the sda, there was no RAID device present. I did not execute "dmraid -ay" by hand before attempting the installation.

Here is the thing, Ubuntu does not execute "dmraid -ay" automatically on either this system or the ASUS MB that I had before. I have to start it either by hand before installing the OS, or by adding scripts in initramfs-tools as I described in the previous post. I assume that Ubuntu must detect the RAID components, and execute dmaraid automatically for most systems, as Open SUSE does for me on this system.

Here is the content of /dev/mapper under Open SUSE:


ddf1_4c5349202020202080862925000000004711471100002 8a0
ddf1_4c5349202020202080862925000000004711471100002 8a0_part1
ddf1_4c5349202020202080862925000000004711471100002 8a0_part2
ddf1_4c5349202020202080862925000000004711471100002 8a0_part3
ddf1_4c5349202020202080862925000000004711471100002 8a0_part4
ddf1_4c5349202020202080862925000000004711471100003 2c8
ddf1_4c5349202020202080862925000000004711471100003 2c8_part1
ddf1_4c5349202020202080862925000000004711471100003 cf0
ddf1_4c5349202020202080862925000000004711471100003 cf0_part1
ddf1_4c5349202020202080862925000000004711471100003 cf0_part2
ddf1_4c5349202020202080862925000000004711471100003 cf0_part3


Before, on the ASUS MB system, once I execute "dmraid -ay" Ubuntu was quite happy with using it, and with the current Intel MB it uses & access it just fine up until it tries to install grub. If while using the alternate installer, I tell it not to install the Grub boot loader it finishes loading with no warnings other than that I need to add a boot loader manually afterward.

Before anyone asks, Yes in the install it detects that there are raid components and asks me if I want to load drivers for them. I always say yes.

It loads the software just fine. From the alternate install CD in rescue a broken system mode it will boot the partition that I tell it has the Ubuntu root.

I really don't think that the problem is with dmraid. I think that the problem is with

[psusi]

dmraid is automatically run so you should never have to run it yourself, except to see why it fails. Check /dev/mapper and you should see the devices there automatically. The problem seems to be that grub does not like installing there, which is what my version of dmraid should fix, have you tried it yet?

I just noticed that the forum interpreted part of it as an emoticon. It should be:



sudo apt-add-repository ppa:psusi/ppa


You are running a mirror not a stripe right? Then if you install grub to sda you only get it on that drive, so if it fails, you won't be able to boot with the other half of the mirror.

[rtrask]

dmraid is automatically run so you should never have to run it yourself, except to see why it fails.

I agree that dmaraid should run automatically, and I believe in most systems it does run automatically. However, for whatever reason it does not run automatically on either of the two mother boards I have tried it. Intel S5500 HCV (http://www.intel.com/products/server/motherboards/s5500hcv/s5500hcv-overview.htm) the current system, or the ASUS Z8PE-D18 (http://www.asus.com/product.aspx?P_ID=sqbdCm0nmFxn3sS4&content=specifications)
On both Systems dmraid did not report any kind of error, and it behaved well once up. I really think that the problem is not with dmraid, but with either grub-probe, or something that grub-probe is reliant upon.

One other clue, might be that when I configured initram-fs to start dmraid on the ASUS system, I had to also add a pause so that the system would wait for the dmraid to finish coming up. I guess that this could be a root problem to why dmraid just does not start automatically. I can't remember the details of how it was done, I'll dig that up later.


Check /dev/mapper and you should see the devices there automatically. The problem seems to be that grub does not like installing there, which is what my version of dmraid should fix, have you tried it yet?

I have not tried your version of dmaraid yet. I currently have Open SUSE loaded, and I need to reorganize a bit.


You are running a mirror not a stripe right? Then if you install grub to sda you only get it on that drive, so if it fails, you won't be able to boot with the other half of the mirror.

No, one of the RAID arrays is mirrored, but the raid array that I am trying to install to is a single SSD that is RAID-0. With raid turned off, it installs, but as I said, it is then not able to find root, because it is now in a raid array.

[Fayce66]

I found a very interesting video on youtube on how to set up raid0 with ubuntu 10.10, hope this helps fixing your problem!

http://www.youtube.com/watch?gl=US&feature=player_embedded&v=-x2rZe2Z9as

[Fayce66]

I actually have the same problem. I tried to install Ubuntu 10.10 as the sole OS on my desktop PC with nvidia raid1 array (2 disks) from the LiveCD, and the install does not even work.

I then tried the install with the alternate CD and it worked just fine (I could reboot and login). Problems started when I used the 'update manager' to get the latest packages and did a reboot: The PC does not boot anymore (I get to the grub2 menu, select 1st option but get a bad magic number error).

I then turned off RAID at the bios level, reboot and voila: it works just fine, I get the Ubuntu login screen again except that I don't have raid anymore. I tried psusi dmraid package (
sudo apt-add-repository ppa:psusi/ppa) and then updated dmraid but it still does not work with RAID on at BIOS level. If I turn off RAID again at BIOS level, I can login again...

I have seen another thread about serious issues with dmraid, I will put the link here if it's any help to anyone.

[wkhasintha]

You are inserting a space in the name where there isn't one, and you need to mount the target fs somewhere and use that instead of / for --root.

[psusi]

Fayce, it sounds like you installed directly to the first drive rather than to the mirror, which broke the mirror. It is now in an inconsistent state where the two disks do not contain the same data.

The bios fake raid mirroring is inherently unreliable, so I suggest you not use it. Unless you are dual booting with Windows, just delete the raid arrays in the bios utility and install with the alternate cd, and set up a pure software raid mirror.

[rtrask]

wkhasintha:


You are inserting a space in the name where there isn't one
I'm not sure who you were referring to here, but I assume that this was meant for me. The extra space was discussed at length later in the forum. It is a artifact of the web site. So please do not waste additional time on that.


, and you need to mount the target fs somewhere and use that instead of / for --root. This was also discussed later additional posts. Actually --root if not specified defaults to /, there really was no issue with what I posted first, but just to address remove all doubt I did it again with a different mount point. This also has nothing to do with the problem.

[rtrask]

I found a very interesting video on youtube on how to set up raid0 with ubuntu 10.10, hope this helps fixing your problem!

http://www.youtube.com/watch?gl=US&feature=player_embedded&v=-x2rZe2Z9as

I watched the video, it was interesting, but not particularly relevant, because what they are doing is setting up a software raid that is totally managed by Ubuntu. I have set up my raid partitions in BIOS using the LSI BIOS that is on the mother board. The reason that I am doing it that way, is because I have Windows 7 on the system, as well as Ubuntu, and now Open SUSE. A better link to describe what I am doing is FakeRaidHowto (https://help.ubuntu.com/community/FakeRaidHowto)

[rtrask]

I actually have the same problem. I tried to install Ubuntu 10.10 as the sole OS on my desktop PC with nvidia raid1 array (2 disks) from the LiveCD, and the install does not even work.

I then tried the install with the alternate CD and it worked just fine (I could reboot and login). Problems started when I used the 'update manager' to get the latest packages and did a reboot: The PC does not boot anymore (I get to the grub2 menu, select 1st option but get a bad magic number error).

I then turned off RAID at the bios level, reboot and voila: it works just fine, I get the Ubuntu login screen again except that I don't have raid anymore. I tried psusi dmraid package (
sudo apt-add-repository ppa:psusi/ppa) and then updated dmraid but it still does not work with RAID on at BIOS level. If I turn off RAID again at BIOS level, I can login again...

I have seen another thread about serious issues with dmraid, I will put the link here if it's any help to anyone.

This may be the same problem, but it seems like a different thread to me. I'm assuming that you set it up using the software raid which was demoed in the YouTube video you referenced previously. I think that you are more likely to get help for your specific problem by starting a new thread.

[rtrask]

I'm still having no luck, and I am convinced that this is not a matter of user error. I am willing and competent enough to debug this issue, but I am not sure where to start, since the problem seems to occur pretty early in the boot sequence.

This is the sequence of events for my latest attempt:

Un-installed Open SUSE from the SSD (set up as a single device in a RAID-0 array)
Using the Alternate installer in Rescue a broken system mode, I first started the Raid array with "dmraid -ay", then installed 10.10
Configured initramfs to start dmraid, and added a udevadmin settle -- timeout=100
Installed Open SUSE on a different RAID array, and then configured menu.lst to point to the partition in the first raid array with the SSD to start Ubuntu (a little tricky because the dmraid under Open SUSE names the partitions differently, and I had to tweak it to get it right.
Ubuntu fails to come up and drops into initramfs (busy box), after issuing "dmraid -ay" and waiting until it the partitions are activated, I exit, and Ubuntu boots as normal.


Can someone confirm what the normal boot sequence should for a system running fake raid? I'm assuming that it just works.
In particular I assume that.

When the LiveCD attempts to install after detecting the RAID arrrays, it shows those raid arrays when you get to the partition stage, and that dmraid does not have to be run by hand.
grub-install just works, and is able to find the device and install
There is no need to configure initramfs-tools & generate a new initramfs image


I also assume that the issues I am seeing are due to the server class hardware I am installing on, but perhaps that is a bad assumption. Has any one gotten this to work correctly?

[psusi]

Your assumptions are correct, that is how things normally work. My theory is that grub fails to install for you because your array name has numbers in it. The version of dmraid in my PPA should fix that. Throwing other distributions into the mix needlessly complicates things and confuses the issue, so can you please try to just do a normal desktop install of Ubuntu by itself, and install the dmraid from my PPA prior to running the installer?

Oh, and you will also have to chroot into the newly installed system and install the new dmraid there, and update the initramfs.

[SeattleJoe98101]

I'm not sure if this is the right thread, but here's my situation:

I dual boot Windows 7 and Ubuntu. I have a Gigabyte motherboard with fake Raid. The motherboard has two controllers, but I used the one from Gigabyte, which I believe is a jmicron386. I presently have a Raid 1 array on two 2 TB drives.

I tried several times to install with the Maverick CD (both desktop and alternate --AMD 64 bit), but it failed every time. When I got to the partitioning page it would show nothing to partition. Finally I tried an old Karmic 64 bit CD. That worked perfectly, and I was able to see my raid array. I then partitioned the drive and installed Windows.l The CD also allowed me to use DD to copy a raid disk partiton to an img file on another raid partition. Windows sees both of these files OK and in fact, Windows has no problem whatsoever with the Raid partitions.

I then installed Karmic to a partition. I tried upgrading to lucid, but after the upgrade, it wouldn't function properly. I then reinstalled Karmic and did the upgrades (but not an upgrade to Lucid). I then began having some of the same problems with booting mentioned elsewhere in this thread.

The question I have is whether there is a way to install the newer versions of unbuntu on a fake raid array. It looks to me like they changed something after Karmic and dropped support for my type of Fake Raid. So is there some way I can get it to work. And will Natty have support for this type of fake raid? If not, does one of the other Linux distros have such support?

Alternatively, is there something that I can do with Maverick to make it work? I have tried using the alternate CD and also installing kpartx before trying an install. This appears to let the system see the Raid Array, but doesn't permit an installation to it. I don't know how to install kpartx from the alternate CD and so I haven't tried that.

If replying, please assume that I know nothing and need step by step instructionsl

Thanks in advance.

[rtrask]

Hi SeattleJoe


Finally I tried an old Karmic 64 bit CD. That worked perfectly, and I was able to see my raid array. I then partitioned the drive and installed Windows.l The CD also allowed me to use DD to copy a raid disk partiton to an img file on another raid partition. Windows sees both of these files OK and in fact, Windows has no problem whatsoever with the Raid partitions.

I ran into problems using GParted from the Live CD starting with 10.4, and read some place to use 9.10 i.e. Karmic. I wonder the same thing, 'if things got broken between 9.10 and 10.04'. I tried to install Karmic on my system, and it got past the issue of installing GRUB, but when I tried to boot. I would get a Error 15, which I'm pretty sure means that it is not mounting the RAID array.


The question I have is whether there is a way to install the newer versions of unbuntu on a fake raid array. It looks to me like they changed something after Karmic and dropped support for my type of Fake Raid. So is there some way I can get it to work. And will Natty have support for this type of fake raid? If not, does one of the other Linux distros have such support?

Alternatively, is there something that I can do with Maverick to make it work? I have tried using the alternate CD and also installing kpartx before trying an install. This appears to let the system see the Raid Array, but doesn't permit an installation to it. I don't know how to install kpartx from the alternate CD and so I haven't tried that.

If replying, please assume that I know nothing and need step by step instructionsl

Thanks in advance.

I think that this set of instructions can get you to the same point that I am at, but if you are luckier than me it may just work.


Use the 10.10 alternate installer
When you get to the splash page select rescue a broken system.
Follow the prompts, it is pretty straight forward until you get to the part where it wants you to mount a root partition. I suspect that it will show the individual disks, but not the raid arrays. If this is the case, select the option not mount a disk. at the next prompt select the option to run a command in the installer environment.
in the installer command line run "dmraid -ay" with out the quotes.
I suspect that your raid arrays will be reported as activated. If not then there is some other issue.
exit out of the installer environment
When the prompt comes up to select the partition to mount to enter rescue mode again tab to the "Go Back" option and hit return. (You may need to do this twice I cant remember)
You should now be at a numbered list of tasks use the down arrow to move past the Rescue Mode option to the partition option
When the Partition option comes up select manual and tell it where you want the root partition etc.
It should continue with no issue, and install 10.10, ( I assume that you want the desk top environment, if so besure to select that option when it asks you to choose what you want to install)
After this step it will try to install Grub. If you are lucky this will just work for you. If not, you are in the same boat as me.
if it fails to install grub, the install will put you back at the list of tasks. If you want to, use the up arrow and go to the rescue mode selection again. When you select it this time choose the partition where you loaded linux at.
If that mounts, then Linux loaded OK. You might try to follow the instructions that were given early in this thread, to mount your root partition, and then do an install-grub --root=/mnt/ "your raid device"


Let me know if this works for you, and if you would, please post the contents of your /dev/mapper directory. In particular, I would like to see if your raid arrays have the same long device names.

I will try PSUSI's suggestion and try his version of dmraid, and let you know / give instructions on how to do this if I am successful.

[rtrask]

Your assumptions are correct, that is how things normally work. My theory is that grub fails to install for you because your array name has numbers in it. The version of dmraid in my PPA should fix that. Throwing other distributions into the mix needlessly complicates things and confuses the issue, so can you please try to just do a normal desktop install of Ubuntu by itself, and install the dmraid from my PPA prior to running the installer?

Oh, and you will also have to chroot into the newly installed system and install the new dmraid there, and update the initramfs.

OK, I will give it a try next, otherwise I am out of ideas. It will be a bit tricky, because I am in a catch 22 situation to do it. I have to use the dmraid that comes with the distro to start the raid array to install to the point that I can chroot to it. Then after it is installed, download your version of dmraid. I will then try to reboot to the alternate installer, and go back to rescue mode, and fire up your version of dmraid, and try to install grub. I may also have to do some tweaking of the mount points if the UUIDs change etc. I don't think it will be straight forward.

[Fayce66]

Hi Psusi,

Thanks for the feedback.

No I made the install on the raid device in /dev/mapper. I started to have issues ONLY when I used the 'Update Manager' for the 1st time to get the latest packages. I probably did a bad manip in between to deserve that bad magic number...

I will follow your advice and turn off the raid controller in the bios, reinstall everything from the alternate CD and setup a software raid. I will let you know the outcome. Cheers.

[psusi]

I will follow your advice and turn off the raid controller in the bios, reinstall everything from the alternate CD and setup a software raid. I will let you know the outcome. Cheers.

No, you need to actually remove the raid metadata from the drives. Ubuntu does not know or care whether the raid support is enabled in the bios, it only knows whether the disks say they are part of a raid or not. You can either use the bios utility to destroy the array, or run sudo dmraid -E /dev/sdX to erase the signature from a drive.

[wkhasintha]

wkhasintha:


I'm not sure who you were referring to here, but I assume that this was meant for me. The extra space was discussed at length later in the forum. It is a artifact of the web site. So please do not waste additional time on that.

This was also discussed later additional posts. Actually --root if not specified defaults to /, there really was no issue with what I posted first, but just to address remove all doubt I did it again with a different mount point. This also has nothing to do with the problem.

My bad. My apologies bro.. http://ubuntuforums.org/images/icons/icon14.gif

[Fayce66]

No, you need to actually remove the raid metadata from the drives. Ubuntu does not know or care whether the raid support is enabled in the bios, it only knows whether the disks say they are part of a raid or not. You can either use the bios utility to destroy the array, or run sudo dmraid -E /dev/sdX to erase the signature from a drive.

I tried two things previously:

1- At boot enter the RAID setup (F10) to delete the array and clear the MBR. I left the RAID enabled at BIOS level, reinstalled everything in /dev/mapper/nvidia_XXX but I end up in the same situation/issue after the first "update Manager' manip. Can't boot anymore...unless I disable RAID and then I can boot again. I don't have enough knowledge to explain this.

2- I disabled the RAID at BIOS level. In here, I might have forgotten to delete the RAID arry first and clear the MBR. I will try that first, then disable RAID, then reinstall everything. Hope it will work this time.

Thanks again for your feedback. Will keep you posted on my progress.

[Fayce66]

Finally managed to make it work (for now) !

I did the setup with software raid (1) as advised above, did all packages and drivers upgrades, and I have no reboot issues so far, I can use the system. Thanks a lot for your help Psusi! I ran the boot script info and I don't see any issues there.


Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #3 for (,msdos3)/grub.
=> No boot loader is installed in the MBR of /dev/sdb

sda1: __________________________________________________ _______________________

File system: linux_raid_member
Boot sector type: -
Boot sector info:

sda2: __________________________________________________ _______________________

File system: linux_raid_member
Boot sector type: -
Boot sector info:

sda3: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/grub.cfg /grub/core.img

sdb1: __________________________________________________ _______________________

File system: linux_raid_member
Boot sector type: -
Boot sector info:

sdb2: __________________________________________________ _______________________

File system: linux_raid_member
Boot sector type: -
Boot sector info:

md1: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

md0: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.10
Boot files/dirs: /etc/fstab

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 14,653,440 488,396,799 473,743,360 fd Linux raid autodetect
/dev/sda2 2,934,784 14,653,439 11,718,656 fd Linux raid autodetect
/dev/sda3 * 2,048 2,934,783 2,932,736 83 Linux


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdb1 14,653,440 488,396,799 473,743,360 fd Linux raid autodetect
/dev/sdb2 2,934,784 14,653,439 11,718,656 fd Linux raid autodetect


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/md0 9f1368e2-f08a-407a-bb74-116b20aa852c ext4
/dev/md1 fe232eb5-0eb8-4261-a498-a8b8b0c26c44 swap
/dev/sda1 b3ee756b-755c-cfc5-3359-bbc02fad5ddc linux_raid_member
/dev/sda2 7d582f18-41b9-ba6d-00d8-d4f36bbdf680 linux_raid_member
/dev/sda3 f1ec7609-16c4-42d5-88fc-f643789b033d ext4
/dev/sda: PTTYPE="dos"
/dev/sdb1 b3ee756b-755c-cfc5-3359-bbc02fad5ddc linux_raid_member
/dev/sdb2 7d582f18-41b9-ba6d-00d8-d4f36bbdf680 linux_raid_member
/dev/sdb: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/md0 / ext4 (rw,errors=remount-ro,commit=0)
/dev/sda3 /boot ext4 (rw,commit=0)


============================= sda3/grub/grub.cfg: =============================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
}

insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(md0)'
search --no-floppy --fs-uuid --set 9f1368e2-f08a-407a-bb74-116b20aa852c
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set f1ec7609-16c4-42d5-88fc-f643789b033d
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set f1ec7609-16c4-42d5-88fc-f643789b033d
linux /vmlinuz-2.6.35-22-generic root=UUID=9f1368e2-f08a-407a-bb74-116b20aa852c ro quiet splash
initrd /initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set f1ec7609-16c4-42d5-88fc-f643789b033d
echo 'Loading Linux 2.6.35-22-generic ...'
linux /vmlinuz-2.6.35-22-generic root=UUID=9f1368e2-f08a-407a-bb74-116b20aa852c ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set f1ec7609-16c4-42d5-88fc-f643789b033d
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set f1ec7609-16c4-42d5-88fc-f643789b033d
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

=================== sda3: Location of files loaded by Grub: ===================


.1GB: grub/core.img
.1GB: grub/grub.cfg
.1GB: initrd.img-2.6.35-22-generic
.1GB: vmlinuz-2.6.35-22-generic

================================ md0/etc/fstab: ================================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/md0 during installation
UUID=9f1368e2-f08a-407a-bb74-116b20aa852c / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda3 during installation
UUID=f1ec7609-16c4-42d5-88fc-f643789b033d /boot ext4 defaults 0 2
# swap was on /dev/md1 during installation
UUID=fe232eb5-0eb8-4261-a498-a8b8b0c26c44 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

==================== md0: Location of files loaded by Grub: ====================


.1GB: initrd.img
.1GB: vmlinuz


I still have a major issue with the nvidia driver not detecting my other monitors but I will work this issue in another thread.

Thanks & Regards,
Fayce

[rtrask]

Your assumptions are correct, that is how things normally work. My theory is that grub fails to install for you because your array name has numbers in it. The version of dmraid in my PPA should fix that. Throwing other distributions into the mix needlessly complicates things and confuses the issue, so can you please try to just do a normal desktop install of Ubuntu by itself, and install the dmraid from my PPA prior to running the installer?

Oh, and you will also have to chroot into the newly installed system and install the new dmraid there, and update the initramfs.

I was unable to make this work, and I am unsure of how it could ever be made to work unless I build a version of the installation CD with your version of dmraid. The problem is that to install the system, you have to run dmraid, but the only version of dmraid that is available is the one in the install environment until it gets installed. I guess that I might be able to try and do an apt-get of your version of dmraid in the installer environment, but to do so I will need some help to figure out how to pin it to your version. Even if that works, do we know if that will be the version that gets installed? or will it get it from the CD? Do you understand the problem? or am I missing something?

Here is what I did. If you tell me how to get apt-get to pin it to your version, I'll try that, but I am still not sure what good it can do unless there is some way to replace what is on the Alternate CD.


booted the alternate CD in rescue mode
chose option to not mount a file system, and dropped into command line in installer environment.
issued dmraid command
issued commands to mount on /target/ and chroot to it
added your repository
did an apt-get install on dmraid -- it was already at latest version
issued a apt-get --purge remove dmraid
issued an apt-get install dmraid
rebooted, then I realized that I could not just do a dmraid, because the version that would be executed was from alternate cd, and not your version
so I mounted the SSD partition rather than the raid version
issued the dmraid -ay command, which mounted the other raid arrays, but could not mount the disk I was in of course. The partition names did not have the alpha between the device and partition, so the one that loaded was the original, not your version.


The apt-get install following the remove had these lines on it

unpacking from .../dmraid_1.0.p.rdb-3ubunt2_amd64.deb

[psusi]

You don't need to pin, just boot the desktop cd, add my ppa, and upgrade dmraid and it will pull in my version. You might then need to refresh by running dmraid -an and then dmraid -ay to reactivate, and the partition devices in /dev/mapper should then show up with a 'p' just before the partition number on the end. Then you should be able to run the installer, make sure you set grub to be installed to the base /dev/mapper/blah device ( without the p1 ) and it should go smoothly.

[rtrask]

You don't need to pin, just boot the desktop cd, add my ppa, and upgrade dmraid and it will pull in my version. You might then need to refresh by running dmraid -an and then dmraid -ay to reactivate, and the partition devices in /dev/mapper should then show up with a 'p' just before the partition number on the end. Then you should be able to run the installer, make sure you set grub to be installed to the base /dev/mapper/blah device ( without the p1 ) and it should go smoothly.

OK, What am I doing wrong, because after attempting to upgrade dmraid, the raid partitions are still the same as before.?

Note: for readability I have alternated colors between commands.



ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# apt-add-repository ppa:psusi/ppa
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 2224BB10BC7DD84E9BC2B29E266319E6B8D488BC
gpg: requesting key B8D488BC from hkp server keyserver.ubuntu.com
gpg: key B8D488BC: public key "Launchpad PPA for Phillip Susi" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
root@ubuntu:/home/ubuntu# apt-get install dmraid
Reading package lists... Done
Building dependency tree
Reading state information... Done
dmraid is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ubuntu:/home/ubuntu# apt-get --purge remove dmraid
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
dmraid*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 188kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 121714 files and directories currently installed.)
Removing dmraid ...
update-initramfs is disabled since running on read-only media
Purging configuration files for dmraid ...
update-initramfs is disabled since running on read-only media
Processing triggers for man-db ...
root@ubuntu:/home/ubuntu# apt-get install dmraid
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
dmraid
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 38.3kB of archives.
After this operation, 188kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ maverick/main dmraid amd64 1.0.0.rc16-3ubuntu2 [38.3kB]
Fetched 38.3kB in 0s (48.6kB/s)
Selecting previously deselected package dmraid.
(Reading database ... 121698 files and directories currently installed.)
Unpacking dmraid (from .../dmraid_1.0.0.rc16-3ubuntu2_amd64.deb) ...
Processing triggers for man-db ...
Setting up dmraid (1.0.0.rc16-3ubuntu2) ...
update-initramfs is disabled since running on read-only media
root@ubuntu:/home/ubuntu# dmraid -an
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a0" is not active
RAID set "ddf1_4c5349202020202080862925000000004711471100003 2c8" is not active
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf0" is not active
root@ubuntu:/home/ubuntu# dmraid -ay
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a0" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 2c8" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf0" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a01" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a02" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a03" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a04" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 2c81" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf01" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf05" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf06" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf07" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf08" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf09" was activated

[psusi]

What does apt-cache policy dmraid show? It should have picked up the one from my ppa but doesn't seem to have.

[rtrask]

What does apt-cache policy dmraid show? It should have picked up the one from my ppa but doesn't seem to have.


root@ubuntu:/etc/apt# apt-cache policy dmraid
dmraid:
Installed: 1.0.0.rc16-3ubuntu2
Candidate: 1.0.0.rc16-3ubuntu2
Version table:
*** 1.0.0.rc16-3ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
100 /var/lib/dpkg/status

both before, and after adding your PPA

[ronparent]

I have lost track of where this tread has been and where it is going. But, just some impressions.

You may be getting hung up on naming conventions. The raid partition names may be just too long and not getting parsed properly. I would propose some experimentation with the /dev/dm-* set of links. What would happen if the dm-* symbolic links were named in place of the corresponding /dev/mapper symbolic link name? This might just be too flaky because on my boot up's I get inconsistent error messages that seem to be related to inconsistent identification of the array and extended partition as not being file systems (of course that error should be trapped)?

I should note that begining with 10.10 when the /dev/mapper symbolic links are set up a parallel corresponding set of links are created with names beginning with /dev/dm-0 thru whatever. During a session those links can be used to mount any raid partition. The question is whether or not the naming is consistent enough to be useful in say ftab or mtab? Is it worth the experimentation.

I have to disclaim that I have no idea where the developer is headed with those links or if they will remain unchanged as the system evolves.

[psusi]

Did you forget to apt-get update after adding the ppa?

[rtrask]

Did you forget to apt-get update after adding the ppa?

I did not forget, I just did not know you wanted me to run it before apt-cache

I'm not sure if you changed something on your end, but in the interim I booted via Open SUSE grub -> busy box -> dmraid -> boot ubuntu 10.10, then I created a pendrive boot disk / Live CD. and rebooted using it. Now I am getting slightly different results, in that I think it loaded your version of dmraid, but after executing it the array names do not appear to have changed. Here are the results


ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# apt-add-repository ppa:psusi/ppa
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 2224BB10BC7DD84E9BC2B29E266319E6B8D488BC
gpg: requesting key B8D488BC from hkp server keyserver.ubuntu.com
gpg: key B8D488BC: public key "Launchpad PPA for Phillip Susi" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
root@ubuntu:/home/ubuntu#
root@ubuntu:/home/ubuntu# apt-get install dmraid
Reading package lists... Done
Building dependency tree
Reading state information... Done
dmraid is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up dkms (2.1.1.2-3ubuntu1) ...
Setting up fakeroot (1.14.4-1ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.
Setting up nvidia-settings (260.19.06-0ubuntu1) ...
Setting up patch (2.6-2ubuntu1) ...
root@ubuntu:/home/ubuntu# dmraid -ay
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a0" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 2c8" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf0" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a01" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a02" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a03" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100002 8a04" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 2c81" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf01" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf05" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf06" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf07" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf08" was activated
RAID set "ddf1_4c5349202020202080862925000000004711471100003 cf09" was activated
root@ubuntu:/home/ubuntu# apt-cache policy dmraid
dmraid:
Installed: 1.0.0.rc16-3ubuntu2
Candidate: 1.0.0.rc16-3ubuntu2
Version table:
*** 1.0.0.rc16-3ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
100 /var/lib/dpkg/status

[psusi]

Nope, nothing changed there. You must update after adding the ppa for it to take effect.

[rtrask]

You may be getting hung up on naming conventions. The raid partition names may be just too long and not getting parsed properly. I would propose some experimentation with the /dev/dm-* set of links. What would happen if the dm-* symbolic links were named in place of the corresponding /dev/mapper symbolic link name? This might just be too flaky because on my boot up's I get inconsistent error messages that seem to be related to inconsistent identification of the array and extended partition as not being file systems (of course that error should be trapped)?

I sort-of agree, It seems like the dm-* is the direction of the future. When I start up with the alternate installer in rescue mode, and then go down the path of "do not mount a disk -> command line prompt in installer environment" when I exit out of the command line mode, and then go back to the screen where you are able to select a partition to mount, it no longer shows the /dev/mapper/ddf1_4c53492020... names, but instead shows the dm-* names as options. The only problem with this, is that I have never been able to make it work to even select one of these options. I always get the red screen not a boot partition, even for every choice of dm-*. I have been at this so long and have tried so many permutations of things, I am not sure is I have ever tried to install the grub partition on dm-0 (which is my best guess of the device with the MBR) I will try that, but I am dubious of my chances for success.

First I'll try mounting a few of teh dm-* devices to see try and verify the contents so I know which device is which.


Now the other side of the coin. :) I believe that the issue goes deeper. and the question that needs to be answered is why is it that "dmraid -ay" does not seem to ever get run automatically? That has to happen before the dm-* devices are available. Also once it has run successfully, mounting /dev/mapper/ddf1_... seems to work just fine. So I think that the problem comes about either prior to the execution of dmraid, or in the script / program which is responsible for running it.

Also, I think that the issue seems to be in the grub-probe portion of the grub-install script. I think that there is some issue that was introduced around the 10.04 time frame which will require a code change, and tweaking configuration to get around it is not going to resolve it.

[ronparent]

Now the other side of the coin. I believe that the issue goes deeper. and the question that needs to be answered is why is it that "dmraid -ay" does not seem to ever get run automatically?

Yes, that may be at the crux of the problem. It begin with 9.04 which until I had been able to mount my raid devices on boot, but, could no longer (that is fixed -at least for now)? It may well be that in your system a delay elsewhere is preventing the dmraid -ay from activating your raids. That may be cause for a bug report, although a bug report doesn't usually get acted upon unless someone else reports also. The cause may be hard to ID in the boot logs unless some significant error pops out.

On my system, dm-0 seem to be my first win 7 partition. When I get the error message that dm-0 (or soemtimes dm-1) contains no file system The notation still seems to be picked up for the 1st raid partition. I doubt that it would be a candidate for a MBR.

[rtrask]

psusi

Nope, nothing changed there. You must update after adding the ppa for it to take effect.I think you missed a couple of things:


Setting up dkms (2.1.1.2-3ubuntu1) ...
Setting up fakeroot (1.14.4-1ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.
Setting up nvidia-settings (260.19.06-0ubuntu1) ...
Setting up patch (2.6-2ubuntu1) ...
Previously after adding your PPA, when I did the "apt-get install dmraid", it did not print the messages in the code fragment above.

Also in the code section of my previous post, I did the apt-get install dmraid after adding your repository, followed by the apt-cache dmraid. What else do you want me to do?

[rtrask]

Phillip,

I was able to get your version of dmraid installed on my SSD installation. The /dev/mapper directory now contains:

ddf1_4c5349202020202080862925000000004711471100002 8a0
ddf1_4c5349202020202080862925000000004711471100002 8a0p1
ddf1_4c5349202020202080862925000000004711471100002 8a0p2
ddf1_4c5349202020202080862925000000004711471100002 8a0p3
ddf1_4c5349202020202080862925000000004711471100002 8a0p4
ddf1_4c5349202020202080862925000000004711471100003 2c8
ddf1_4c5349202020202080862925000000004711471100003 2c8p1
ddf1_4c5349202020202080862925000000004711471100003 cf0
ddf1_4c5349202020202080862925000000004711471100003 cf0p1
ddf1_4c5349202020202080862925000000004711471100003 cf0p5
ddf1_4c5349202020202080862925000000004711471100003 cf0p6
ddf1_4c5349202020202080862925000000004711471100003 cf0p7
ddf1_4c5349202020202080862925000000004711471100003 cf0p8
ddf1_4c5349202020202080862925000000004711471100003 cf0p9
But this does not seem to make any difference. After booting to this environment, I tried the grub-install, and got the exact same result.


[root@Hosea-14-4:/boot# mkdir /target
root@Hosea-14-4:/boot# mount /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3 /target/
root@Hosea-14-4:/boot# ls /target
bin etc lib lost+found opt sbin sys usr
boot home lib32 media proc selinux target var
dev initrd.img lib64 mnt root srv tmp vmlinuz
root@Hosea-14-4:/boot# grub-install --root-directory=/target/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.As I said to ronparent, I don't think that the issue is with dmraid, but with whatever is calling dmraid.

[psusi]

Also in the code section of my previous post, I did the apt-get install dmraid after adding your repository, followed by the apt-cache dmraid. What else do you want me to do?

I'll say it again: you need to run apt-get update after apt-add-repository.



root@Hosea-14-4:/boot# grub-install --root-directory=/target/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.

What do you get when you run sudo grub-probe -t fs -v -d /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3

[ronparent]

I imagine you are getting fed-up with this topic. If I may make one suggestion.

If, booted to a live session, you look in 'Log File Viewer' and do a search on your bootloader target you will find the dm-# reference for it. I would use only part of the string and be sure to end it with a space (ie 250000000047114711000028a0 ). This will take you to a block of text where you will find the corresponding dm-# reference. In that block of text you will be looking for 'DEVNAME=/dev/dm-?'. I tried it and on my setup the two step grub install as you have been using did a grub install and placed my boot loader on the proper raid root. At this point it may be worth the effort. Good luck.

[rtrask]

psusi

I'll say it again: you need to run apt-get update after apt-add-repository.I'm not sure what the disconnect is. I did run apt-get update. And as I told you in the previous post, your version of dmraid was installed. I booted with it. What am I missing here?

Below is the output of grub-probe you requested.

root@Hosea-14-4:/boot# grub-probe -t fs -v -d /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3
grub-probe: info: cannot open `/boot/grub/device.map'.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd5 is 1951170560.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd6 is 640622592.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: the size of hd7 is 173828096.
grub-probe: info: opening ddf1_4c5349202020202080862925000000004711471100002 8a0p3.
grub-probe: error: no such disk.ronparent

I imagine you are getting fed-up with this topic.I look at it like I have invested all this time, I want a return on that investment even if that return is just to help someone else out. I want to see this to completion.


If, booted to a live session, you look in 'Log File Viewer' and do a search on your bootloader target you will find the dm-# reference for it. I would use only part of the string and be sure to end it with a space (ie 250000000047114711000028a0 ). This will take you to a block of text where you will find the corresponding dm-# reference. In that block of text you will be looking for 'DEVNAME=/dev/dm-?'. I tried it and on my setup the two step grub install as you have been using did a grub install and placed my boot loader on the proper raid root. At this point it may be worth the effort. Good luck. Thanks ronparent, this has been fruitful. I have not used the Log File viewer before. it is a nice tool. I did a bit of hunting around, and found the following in the udev log


UDEV [1289672418.731916] add /devices/virtual/block/dm-0 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/virtual/block/dm-0
SUBSYSTEM=block
DEVNAME=/dev/dm-0
DEVTYPE=disk
SEQNUM=2320
DM_NAME=ddf1_4c53492020202020808629250000000047114 711000028a0
DM_UUID=DMRAID-ddf1_4c5349202020202080862925000000004711471100002 8a0
DM_SUSPENDED=0
DM_UDEV_RULES=1
ID_PART_TABLE_TYPE=dos
UDISKS_PRESENTATION_NOPOLICY=1
MAJOR=252
MINOR=0
DEVLINKS=/dev/block/252:0 /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0 /dev/disk/by-id/dm-name-ddf1_4c5349202020202080862925000000004711471100002 8a0 /dev/disk/by-id/dm-uuid-DMRAID-ddf1_4c5349202020202080862925000000004711471100002 8a0
This opens a number of possibilities, but I don't have time to track them all down right now. I'll look at it in the morning.

The initial results aren't quite there, but we may be on to something.

root@Hosea-14-4:/boot# grub-install --root-directory=/target/ /dev/dm-0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
root@Hosea-14-4:/boot# grub-probe -t fs -v -d /dev/dm-0
grub-probe: info: cannot open `/boot/grub/device.map'.
grub-probe: info: opening /dev/dm-0.
grub-probe: info: the size of /dev/dm-0 is 173828096.
grub-probe: error: unknown filesystem.Getting back to an earlier question, does anyone know what goes into device.map? I think it might be worth a try to do what the error message is telling us to do and "specify the module with '--modules' explicitly"

[psusi]

psusi
I'm not sure what the disconnect is. I did run apt-get update. And as I told you in the previous post, your version of dmraid was installed. I booted with it. What am I missing here?

You had made two posts. The first one you hadn't updated and asked what to do, then you made a second post before I got back where it seems you did.


Getting back to an earlier question, does anyone know what goes into device.map? I think it might be worth a try to do what the error message is telling us to do and "specify the module with '--modules' explicitly"

device.map maps bios disk numbers to kernel disk devices. It should not be needed these days, but you might try setting one up and see if it helps. In your case it should have a line that looks like:

(hd0) /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0

Can you run the grub-probe again but with two more -v's this time?

[ronparent]

You are probably getting the correct response for the command:

grub-probe -t fs -v -d /dev/dm-0
That location has no file system - it is the root of the array. I get a similar response on my system for the root. However I am getting size info for every partition and for each (hd?) device in my device.map. The missing /boot/grub/device.map seems to be significant. I don't know right now what generates it.

My own device.map is much simpler than yours would be. It reads:
(
hd0) /dev/disk/by-id/ata-HDS722516VLSA80_VNRD3EC4CE516M
(hd1) /dev/disk/by-id/ata-HDS722516VLSA80_VNRD3EC4CE6EVM
(hd2) /dev/disk/by-id/ata-ST3640323AS_9VK0G5GV
(hd3) /dev/disk/by-id/ata-OCZ-VERTEX_M20568X5WUJBU8177X91
(hd4) /dev/mapper/nvidia_aebhdfib
The first two are the disk components of my raid 0.

psusi may be on to something here.

It just hit me. You have a non standard grub fs. It doesn't contain /boot/grub thus:

Auto-detection of a filesystem module failed
We may have to research how your fs module would be specified.

I love your attitude:

I look at it like I have invested all this time, I want a return on that investment even if that return is just to help someone else out. I want to see this to completion.
I'm already learning some things I didn't know before.

[ronparent]

Continuing from last night to examine your grub-probe errors.

grub-probe: info: cannot open `/boot/grub/device.map'.
Your device.map location would be '/grub' if there!

grub-probe: error: unknown filesystem.
The grub-probe is looking for '/' or maybe 'boot/grub'.

On grub-install - could '--modules=/grub' be what grub-install is looking for?

[psusi]

ronparent, device.map is not used anymore.

[ronparent]

psusi, I don't disagree with you. But my system has one and rtrask had inquired what one looked like.

Your comment:

device.map maps bios disk numbers to kernel disk devices. It should not be needed these days, but you might try setting one up and see if it helps. In your case it should have a line that looks like:

[rtrask]

Can you run the grub-probe again but with two more -v's this time?


grub-probe: info: cannot open `/boot/grub/device.map'.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
util/deviceiter.c:376: Already seen /dev/disk/by-id/scsi-SATA_OCZ-AGILITY2_3.OCZ-H9SLQW1RT880622A (/dev/sda)
util/deviceiter.c:376: Already seen /dev/disk/by-id/wwn-0x5e83a97f8acbf2e9 (/dev/sda)
util/deviceiter.c:376: Already seen /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-22_WD-WCAV53609703 (/dev/sdb)
util/deviceiter.c:376: Already seen /dev/disk/by-id/wwn-0x50014ee20391a7e6 (/dev/sdb)
util/deviceiter.c:376: Already seen /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-22_WD-WCAV53609317 (/dev/sdc)
util/deviceiter.c:376: Already seen /dev/disk/by-id/wwn-0x50014ee2ae3b5b08 (/dev/sdc)
util/deviceiter.c:376: Already seen /dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VNRD3EC4CE6DPM (/dev/sdd)
util/deviceiter.c:376: Already seen /dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VNRD3EC4CE1BVM (/dev/sde)
util/deviceiter.c:376: Already seen /dev/sda (/dev/sda)
util/deviceiter.c:376: Already seen /dev/sdb (/dev/sdb)
util/deviceiter.c:376: Already seen /dev/sdc (/dev/sdc)
util/deviceiter.c:376: Already seen /dev/sdd (/dev/sdd)
util/deviceiter.c:376: Already seen /dev/sde (/dev/sde)
util/deviceiter.c:376: Already seen /dev/sdf (/dev/sdf)
util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8 (/dev/dm-1)
util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0 (/dev/dm-2)
disk/raid.c:658: Scanning for RAID devices on disk hd0
kern/disk.c:245: Opening `hd0'...
kern/emu/hostdisk.c:594: opening the device `/dev/sda' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sda'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda'
kern/disk.c:334: Closing `hd0'.
kern/disk.c:245: Opening `hd0'...
partmap/apple.c:121: bad magic (found 0xeb48; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/emu/hostdisk.c:594: opening the device `/dev/sda1' in open_device()
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/emu/hostdisk.c:594: opening the device `/dev/sda2' in open_device()
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
kern/emu/hostdisk.c:594: opening the device `/dev/sda3' in open_device()
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/emu/hostdisk.c:594: opening the device `/dev/sda4' in open_device()
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd0'.
disk/raid.c:658: Scanning for RAID devices on disk hd0,msdos4
kern/disk.c:245: Opening `hd0,msdos4'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/emu/hostdisk.c:594: opening the device `/dev/sda4' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sda4'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda4'
kern/disk.c:334: Closing `hd0,msdos4'.
disk/raid.c:658: Scanning for RAID devices on disk hd0,msdos3
kern/disk.c:245: Opening `hd0,msdos3'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
kern/emu/hostdisk.c:594: opening the device `/dev/sda3' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sda3'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda3'
kern/disk.c:334: Closing `hd0,msdos3'.
disk/raid.c:658: Scanning for RAID devices on disk hd0,msdos2
kern/disk.c:245: Opening `hd0,msdos2'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/emu/hostdisk.c:594: opening the device `/dev/sda2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sda2'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda2'
kern/disk.c:334: Closing `hd0,msdos2'.
disk/raid.c:658: Scanning for RAID devices on disk hd0,msdos1
kern/disk.c:245: Opening `hd0,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/emu/hostdisk.c:594: opening the device `/dev/sda1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sda1'
kern/emu/hostdisk.c:584: reusing open device `/dev/sda1'
kern/disk.c:334: Closing `hd0,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd1
kern/disk.c:245: Opening `hd1'...
kern/emu/hostdisk.c:594: opening the device `/dev/sdb' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb'
kern/disk.c:334: Closing `hd1'.
kern/disk.c:245: Opening `hd1'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/sdb' in open_device()
kern/emu/hostdisk.c:594: opening the device `/dev/sdb1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb1'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd1'.
disk/raid.c:658: Scanning for RAID devices on disk hd1,msdos1
kern/disk.c:245: Opening `hd1,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/sdb1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb1'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdb1'
kern/disk.c:334: Closing `hd1,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd2
kern/disk.c:245: Opening `hd2'...
kern/emu/hostdisk.c:594: opening the device `/dev/sdc' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc'
kern/disk.c:334: Closing `hd2'.
kern/disk.c:245: Opening `hd2'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/sdc' in open_device()
kern/emu/hostdisk.c:594: opening the device `/dev/sdc1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc1'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd2'.
disk/raid.c:658: Scanning for RAID devices on disk hd2,msdos1
kern/disk.c:245: Opening `hd2,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/sdc1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc1'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdc1'
kern/disk.c:334: Closing `hd2,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd3
kern/disk.c:245: Opening `hd3'...
kern/emu/hostdisk.c:594: opening the device `/dev/sdd' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd'
kern/disk.c:334: Closing `hd3'.
kern/disk.c:245: Opening `hd3'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.cgrub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd6 is 1951170560.
grub-probe: info: the size of hd6 is 1951170560.
:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/emu/hostdisk.c:594: opening the device `/dev/sdd' in open_device()
kern/emu/hostdisk.c:594: opening the device `/dev/sdd1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd1'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/emu/hostdisk.c:594: opening the device `/dev/sdd' in open_device()
kern/disk.c:334: Closing `hd3'.
disk/raid.c:658: Scanning for RAID devices on disk hd3,msdos1
kern/disk.c:245: Opening `hd3,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/emu/hostdisk.c:594: opening the device `/dev/sdd1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd1'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdd1'
kern/disk.c:334: Closing `hd3,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd4
kern/disk.c:245: Opening `hd4'...
kern/emu/hostdisk.c:594: opening the device `/dev/sde' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sde'
kern/emu/hostdisk.c:584: reusing open device `/dev/sde'
kern/emu/hostdisk.c:584: reusing open device `/dev/sde'
kern/disk.c:334: Closing `hd4'.
kern/disk.c:245: Opening `hd4'...
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd4'.
disk/raid.c:658: Scanning for RAID devices on disk hd5
kern/disk.c:245: Opening `hd5'...
kern/emu/hostdisk.c:594: opening the device `/dev/sdf' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/disk.c:334: Closing `hd5'.
kern/disk.c:245: Opening `hd5'...
partmap/apple.c:121: bad magic (found 0xeb58; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0xb, start 0x3f, len 0xe7f81
kern/emu/hostdisk.c:594: opening the device `/dev/sdf' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
partmap/apple.c:121: bad magic (found 0xd25f; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd5'.
disk/raid.c:658: Scanning for RAID devices on disk hd5,msdos1
kern/disk.c:245: Opening `hd5,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0xb, start 0x3f, len 0xe7f81
kern/emu/hostdisk.c:594: opening the device `/dev/sdf' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/emu/hostdisk.c:584: reusing open device `/dev/sdf'
kern/disk.c:334: Closing `hd5,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd6
kern/disk.c:245: Opening `hd6'...
kern/emu/hostdisk.c:594: opening the device `/dev/dm-1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/disk.c:334: Closing `hd6'.
kern/disk.c:245: Opening `hd6'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/dm-1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd6'.
disk/raid.c:658: Scanning for RAID devices on disk hd6,msdos1
kern/disk.c:245: Opening `grub-probe: info: the size of hd6 is 1951170560.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
hd6,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/dm-1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
kern/disk.c:334: Closing `hd6,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd7
kern/disk.c:245: Opening `hd7'...
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7'.
kern/disk.c:245: Opening `hd7'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x6205a7d, len 0x360d3e1
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4a03d00, len 0x360d300
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
kern/disk.c:334: Closing `hd7'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos9
kern/disk.c:245: Opening `hd7,msdos9'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:9grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
1: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x6205a7d, len 0x360d3e1
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4a03d00, len 0x360d300
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos9'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos8
kern/disk.c:245: Opening `hd7,msdos8'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos8'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos7
kern/disk.c:245: Opening `hd7,msdos7'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmgrub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
ap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos7'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos6
kern/disk.c:245: Opening `hd7,msdos6'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos6'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos5
kern/disk.c:245: Opening `hd7,msdos5'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos5'.
disk/raid.c:658: Scanning for RAID devices on disk hd7,msdos1
kern/disk.c:245: Opening `hd7,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/emu/hostdisk.c:594: opening the device `/dev/dm-2' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-2'
kern/disk.c:334: Closing `hd7,msdos1'.
disk/raid.c:658: Scanning for RAID devices on disk hd8
kern/disk.c:245: Opening `hd8'...
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/disk.c:334: Closing `hd8'.
kern/disk.c:245: Opening `hd8'...
partmap/apple.c:121: bad magic (found 0xeb48; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, legrub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd0 is 175836528.
n 0x41c1bc4
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd8'.
disk/raid.c:658: Scanning for RAID devices on disk hd8,msdos4
kern/disk.c:245: Opening `hd8,msdos4'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/disk.c:334: Closing `hd8,msdos4'.
disk/raid.c:658: Scanning for RAID devices on disk hd8,msdos3
kern/disk.c:245: Opening `hd8,msdos3'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/disk.c:334: Closing `hd8,msdos3'.
disk/raid.c:658: Scanning for RAID devices on disk hd8,msdos2
kern/disk.c:245: Opening `hd8,msdos2'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/disk.c:334: Closing `hd8,msdos2'.
disk/raid.c:658: Scanning for RAID devices on disk hd8,msdos1
kern/disk.c:245: Opening `hd8,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/emu/hostdisk.c:594: opening the device `/dev/dm-0' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-0'
kern/disk.c:334: Closing `hd8,msdos1'.
kern/disk.c:245: Opening `hd0'...
kern/disk.c:334: Closing `hd0'.
kern/disk.c:245: Opening `hd0'...
partmap/apple.c:121: bad magic (found 0xeb48; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd0'.
kern/disk.c:245: Opening `hd0,msdos4'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/disk.c:334: Closing `hd0,msdos4'.
kern/disk.c:245: Opening `hd0,msdos3'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
kern/disk.c:334: Closing `hd0,msdos3'.
kern/disk.c:245: Opening `hd0,msdos2'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partgrub-probe: info: the size of hd0 is 175836528.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd1 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd2 is 1953525168.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd3 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd4 is 321672960.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd5 is 7601672.
grub-probe: info: the size of hd6 is 1951170560.
grub-probe: info: the size of hd6 is 1951170560.
grub-probe: info: the size of hd6 is 1951170560.
map/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/disk.c:334: Closing `hd0,msdos2'.
kern/disk.c:245: Opening `hd0,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/disk.c:334: Closing `hd0,msdos1'.
kern/disk.c:245: Opening `hd1'...
kern/disk.c:334: Closing `hd1'.
kern/disk.c:245: Opening `hd1'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd1'.
kern/disk.c:245: Opening `hd1,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/disk.c:334: Closing `hd1,msdos1'.
kern/disk.c:245: Opening `hd2'...
kern/disk.c:334: Closing `hd2'.
kern/disk.c:245: Opening `hd2'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/sdc1' in open_device()
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd2'.
kern/disk.c:245: Opening `hd2,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/disk.c:334: Closing `hd2,msdos1'.
kern/disk.c:245: Opening `hd3'...
kern/disk.c:334: Closing `hd3'.
kern/disk.c:245: Opening `hd3'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd3'.
kern/disk.c:245: Opening `hd3,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/disk.c:334: Closing `hd3,msdos1'.
kern/disk.c:245: Opening `hd4'...
kern/disk.c:334: Closing `hd4'.
kern/disk.c:245: Opening `hd4'...
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd4'.
kern/disk.c:245: Opening `hd5'...
kern/disk.c:334: Closing `hd5'.
kern/disk.c:245: Opening `hd5'...
partmap/apple.c:121: bad magic (found 0xeb58; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0xb, start 0x3f, len 0xe7f81
partmap/apple.c:121: bad magic (found 0xd25f; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd5'.
kern/disk.c:245: Opening `hd5,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0xb, start 0x3f, len 0xe7f81
kern/disk.c:334: Closing `hd5,msdos1'.
kern/disk.c:245: Opening `hd6'...
kern/disk.c:334: Closing `hd6'.
kern/disk.c:245: Opening `hd6'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/emu/hostdisk.c:594: opening the device `/dev/dm-1' in open_device()
kern/emu/hostdisk.c:584: reusing open device `/dev/dm-1'
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
kern/disk.c:334: Closing `hd6'.
kern/disk.c:245: Opening `hd6,msdos1'...
partmap/msdogrub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
s.c:91: partition 0: flag 0x0, type 0x7, start 0x3f, len 0x744c50af
kern/disk.c:334: Closing `hd6,msdos1'.
kern/disk.c:245: Opening `hd7'...
kern/disk.c:334: Closing `hd7'.
kern/disk.c:245: Opening `hd7'...
partmap/apple.c:121: bad magic (found 0xfab8; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x6205a7d, len 0x360d3e1
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4a03d00, len 0x360d300
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4a03c1f, len 0x0
kern/disk.c:334: Closing `hd7'.
kern/disk.c:245: Opening `hd7,msdos9'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x6205a7d, len 0x360d3e1
partmap/msdos.c:91: partition 2: grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd7 is 640622592.
flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x4801f5c, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4a03d00, len 0x360d300
kern/disk.c:334: Closing `hd7,msdos9'.
kern/disk.c:245: Opening `hd7,msdos8'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x4801f5d, len 0x201ca4
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000ff, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x4802000, len 0x201c00
kern/disk.c:334: Closing `hd7,msdos8'.
kern/disk.c:245: Opening `hd7,msdos7'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b23, len 0x1801e01
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x9399b22, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3000100, len 0x1801e00
kern/disk.c:334: Closing `hd7,msdos7'.
kern/disk.c:245: Opening `hd7,msdos6'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x9399b22, len 0x1cf54ba2
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x30000fe, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x9399b61, len 0x1cf54b63
kern/disk.c:334: Closing `hd7,msdos6'.
kern/disk.c:245: Opening `hd7,msdos5'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
partmap/msdos.c:91: partition 1: flag 0x0, type 0x5, start 0x30000fe, len 0x232ee5c6
partmap/msdos.c:91: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
partmap/msdos.c:91: partition 0: flag 0x0, type 0x83, start 0x8011026, len 0x1388afc
kern/disk.c:334: Closing `hd7,msdos5'.grub-probe: info: the size of hd7 is 640622592.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: the size of hd8 is 173828096.
grub-probe: info: opening ddf1_4c5349202020202080862925000000004711471100002 8a0.
grub-probe: error: no such disk.

kern/disk.c:245: Opening `hd7,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x0, type 0x82, start 0x3f, len 0x2ffffbe
kern/disk.c:334: Closing `hd7,msdos1'.
kern/disk.c:245: Opening `hd8'...
kern/disk.c:334: Closing `hd8'.
kern/disk.c:245: Opening `hd8'...
partmap/apple.c:121: bad magic (found 0xeb48; wanted 0x4552
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/apple.c:121: bad magic (found 0xeb52; wanted 0x4552
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
partmap/apple.c:121: bad magic (found 0x0; wanted 0x4552
kern/disk.c:334: Closing `hd8'.
kern/disk.c:245: Opening `hd8,msdos4'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
partmap/msdos.c:91: partition 3: flag 0x0, type 0x83, start 0x6400000, len 0x3980
kern/disk.c:334: Closing `hd8,msdos4'.
kern/disk.c:245: Opening `hd8,msdos3'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
partmap/msdos.c:91: partition 2: flag 0x0, type 0x83, start 0x6403980, len 0x41c1bc4
kern/disk.c:334: Closing `hd8,msdos3'.
kern/disk.c:245: Opening `hd8,msdos2'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
partmap/msdos.c:91: partition 1: flag 0x0, type 0x7, start 0x32800, len 0x63cd800
kern/disk.c:334: Closing `hd8,msdos2'.
kern/disk.c:245: Opening `hd8,msdos1'...
partmap/msdos.c:91: partition 0: flag 0x80, type 0x7, start 0x800, len 0x32000
kern/disk.c:334: Closing `hd8,msdos1'.
kern/disk.c:245: Opening `ddf1_4c534920202020208086292500000000471147110000 28a0'...
kern/disk.c:320: Opening `ddf1_4c534920202020208086292500000000471147110000 28a0' failed.
kern/disk.c:334: Closing `ddf1_4c534920202020208086292500000000471147110000 28a0'.

[rtrask]

It just hit me. You have a non standard grub fs. It doesn't contain /boot/grub thus:

We may have to research how your fs module would be specified.

It does contain /boot/grub, here is the contents:


root@Hosea-14-4:/home/rtrask# ls -l /boot/grub
total 1576
-rw-r--r-- 1 root root 8208 2010-11-13 16:12 915resolution.mod
-rw-r--r-- 1 root root 10488 2010-11-13 16:12 acpi.mod
-rw-r--r-- 1 root root 4536 2010-11-13 16:12 affs.mod
-rw-r--r-- 1 root root 4896 2010-11-13 16:12 afs_be.mod
-rw-r--r-- 1 root root 4872 2010-11-13 16:12 afs.mod
-rw-r--r-- 1 root root 1048 2010-11-13 16:12 aout.mod
-rw-r--r-- 1 root root 8036 2010-11-13 16:12 ata.mod
-rw-r--r-- 1 root root 2228 2010-11-13 16:12 ata_pthru.mod
-rw-r--r-- 1 root root 2672 2010-11-13 16:12 at_keyboard.mod
-rw-r--r-- 1 root root 4792 2010-11-13 16:12 befs_be.mod
-rw-r--r-- 1 root root 4776 2010-11-13 16:12 befs.mod
-rw-r--r-- 1 root root 4288 2010-11-13 16:12 biosdisk.mod
-rw-r--r-- 1 root root 2400 2010-11-13 16:12 bitmap.mod
-rw-r--r-- 1 root root 2904 2010-11-13 16:12 bitmap_scale.mod
-rw-r--r-- 1 root root 2020 2010-11-13 16:12 blocklist.mod
-rw-r--r-- 1 root root 512 2010-11-13 16:12 boot.img
-rw-r--r-- 1 root root 2568 2010-11-13 16:12 boot.mod
-rw-r--r-- 1 root root 19612 2010-11-13 16:12 bsd.mod
-rw-r--r-- 1 root root 1964 2010-11-13 16:12 bufio.mod
-rw-r--r-- 1 root root 2388 2010-11-13 16:12 cat.mod
-rw-r--r-- 1 root root 512 2010-11-13 16:12 cdboot.img
-rw-r--r-- 1 root root 2476 2010-11-13 16:12 chain.mod
-rw-r--r-- 1 root root 1340 2010-11-13 16:12 cmostest.mod
-rw-r--r-- 1 root root 2144 2010-11-13 16:12 cmp.mod
-rw-r--r-- 1 root root 2033 2010-11-13 16:12 command.lst
-rw-r--r-- 1 root root 1784 2010-11-13 16:12 configfile.mod
-rw-r--r-- 1 root root 2864 2010-11-13 16:12 cpio.mod
-rw-r--r-- 1 root root 1608 2010-11-13 16:12 cpuid.mod
-rw-r--r-- 1 root root 1784 2010-11-13 16:12 crc.mod
-rw-r--r-- 1 root root 825 2010-11-13 16:12 crypto.lst
-rw-r--r-- 1 root root 4428 2010-11-13 16:12 crypto.mod
-rw-r--r-- 1 root root 4052 2010-11-13 16:12 cs5536.mod
-rw-r--r-- 1 root root 1824 2010-11-13 16:12 datehook.mod
-rw-r--r-- 1 root root 2316 2010-11-13 16:12 date.mod
-rw-r--r-- 1 root root 1241 2010-11-13 16:12 datetime.mod
-rw-r--r-- 1 root root 512 2010-11-13 16:12 diskboot.img
-rw-r--r-- 1 root root 1896 2010-11-13 16:12 dm_nv.mod
-rw-r--r-- 1 root root 5488 2010-11-13 16:12 drivemap.mod
-rw-r--r-- 1 root root 1920 2010-11-13 16:12 echo.mod
-rw-r--r-- 1 root root 6452 2010-11-13 16:12 efiemu32.o
-rw-r--r-- 1 root root 11018 2010-11-13 16:12 efiemu64.o
-rw-r--r-- 1 root root 24168 2010-11-13 16:12 efiemu.mod
-rw-r--r-- 1 root root 4404 2010-11-13 16:12 elf.mod
-rw-r--r-- 1 root root 1636 2010-11-13 16:12 example_functional_test.mod
-rw-r--r-- 1 root root 5500 2010-11-13 16:12 ext2.mod
-rw-r--r-- 1 root root 3976 2010-11-13 16:12 extcmd.mod
-rw-r--r-- 1 root root 5932 2010-11-13 16:12 fat.mod
-rw-r--r-- 1 root root 11992 2010-11-13 16:12 font.mod
-rw-r--r-- 1 root root 2800 2010-11-13 16:12 fshelp.mod
-rw-r--r-- 1 root root 128 2010-11-13 16:12 fs.lst
-rw-r--r-- 1 root root 2508 2010-11-13 16:12 functional_test.mod
-rw-r--r-- 1 root root 1768 2010-11-13 16:12 gcry_arcfour.mod
-rw-r--r-- 1 root root 8144 2010-11-13 16:12 gcry_blowfish.mod
-rw-r--r-- 1 root root 35040 2010-11-13 16:12 gcry_camellia.mod
-rw-r--r-- 1 root root 17568 2010-11-13 16:12 gcry_cast5.mod
-rw-r--r-- 1 root root 2996 2010-11-13 16:12 gcry_crc.mod
-rw-r--r-- 1 root root 19280 2010-11-13 16:12 gcry_des.mod
-rw-r--r-- 1 root root 3268 2010-11-13 16:12 gcry_md4.mod
-rw-r--r-- 1 root root 4008 2010-11-13 16:12 gcry_md5.mod
-rw-r--r-- 1 root root 2636 2010-11-13 16:12 gcry_rfc2268.mod
-rw-r--r-- 1 root root 19204 2010-11-13 16:12 gcry_rijndael.mod
-rw-r--r-- 1 root root 9116 2010-11-13 16:12 gcry_rmd160.mod
-rw-r--r-- 1 root root 16652 2010-11-13 16:12 gcry_seed.mod
-rw-r--r-- 1 root root 18016 2010-11-13 16:12 gcry_serpent.mod
-rw-r--r-- 1 root root 8848 2010-11-13 16:12 gcry_sha1.mod
-rw-r--r-- 1 root root 3484 2010-11-13 16:12 gcry_sha256.mod
-rw-r--r-- 1 root root 5620 2010-11-13 16:12 gcry_sha512.mod
-rw-r--r-- 1 root root 11980 2010-11-13 16:12 gcry_tiger.mod
-rw-r--r-- 1 root root 39736 2010-11-13 16:12 gcry_twofish.mod
-rw-r--r-- 1 root root 24792 2010-11-13 16:12 gcry_whirlpool.mod
-rw-r--r-- 1 root root 3984 2010-11-13 16:12 gettext.mod
-rw-r--r-- 1 root root 38628 2010-11-13 16:12 gfxmenu.mod
-rw-r--r-- 1 root root 11280 2010-11-13 16:12 gfxterm.mod
-rw-r--r-- 1 root root 3720 2010-11-13 16:12 gptsync.mod
-rw-r--r-- 1 root root 10240 2010-11-13 16:12 grldr.img
-r--r--r-- 1 root root 2684 2010-11-09 23:03 grub.cfg
-rw-r--r-- 1 root root 1024 2010-11-13 11:20 grubenv
-rw-r--r-- 1 root root 7828 2010-11-13 16:12 gzio.mod
-rw-r--r-- 1 root root 1460 2010-11-13 16:12 halt.mod
-rw-r--r-- 1 root root 0 2010-11-13 16:12 handler.lst
-rw-r--r-- 1 root root 4632 2010-11-13 16:12 hashsum.mod
-rw-r--r-- 1 root root 7440 2010-11-13 16:12 hdparm.mod
-rw-r--r-- 1 root root 1216 2010-11-13 16:12 hello.mod
-rw-r--r-- 1 root root 2488 2010-11-13 16:12 help.mod
-rw-r--r-- 1 root root 3244 2010-11-13 16:12 hexdump.mod
-rw-r--r-- 1 root root 6028 2010-11-13 16:12 hfs.mod
-rw-r--r-- 1 root root 5896 2010-11-13 16:12 hfsplus.mod
-rw-r--r-- 1 root root 2856 2010-11-13 16:12 iorw.mod
-rw-r--r-- 1 root root 6248 2010-11-13 16:12 iso9660.mod
-rw-r--r-- 1 root root 5844 2010-11-13 16:12 jfs.mod
-rw-r--r-- 1 root root 5944 2010-11-13 16:12 jpeg.mod
-rw-r--r-- 1 root root 29028 2010-11-13 16:12 kernel.img
-rw-r--r-- 1 root root 1980 2010-11-13 16:12 keystatus.mod
-rw-r--r-- 1 root root 5012 2010-11-13 16:12 linux16.mod
-rw-r--r-- 1 root root 8732 2010-11-13 16:12 linux.mod
-rw-r--r-- 1 root root 1024 2010-11-13 16:12 lnxboot.img
-rw-r--r-- 1 root root 5560 2010-11-13 16:12 loadenv.mod
drwxr-xr-x 2 root root 4096 2010-11-13 11:35 locale
-rw-r--r-- 1 root root 3032 2010-11-13 16:12 loopback.mod
-rw-r--r-- 1 root root 1300 2010-11-13 16:12 lsmmap.mod
-rw-r--r-- 1 root root 4168 2010-11-13 16:12 ls.mod
-rw-r--r-- 1 root root 4932 2010-11-13 16:12 lspci.mod
-rw-r--r-- 1 root root 6060 2010-11-13 16:12 lvm.mod
-rw-r--r-- 1 root root 2652 2010-11-13 16:12 mdraid.mod
-rw-r--r-- 1 root root 2080 2010-11-13 16:12 memdisk.mod
-rw-r--r-- 1 root root 2876 2010-11-13 16:12 memrw.mod
-rw-r--r-- 1 root root 4132 2010-11-13 16:12 minicmd.mod
-rw-r--r-- 1 root root 4336 2010-11-13 16:12 minix.mod
-rw-r--r-- 1 root root 8508 2010-11-13 16:12 mmap.mod
-rw-r--r-- 1 root root 2773 2010-11-13 16:12 moddep.lst
-rw-r--r-- 1 root root 2372 2010-11-13 16:12 msdospart.mod
-rw-r--r-- 1 root root 11436 2010-11-13 16:12 multiboot2.mod
-rw-r--r-- 1 root root 10488 2010-11-13 16:12 multiboot.mod
-rw-r--r-- 1 root root 6648 2010-11-13 16:12 nilfs2.mod
-rw-r--r-- 1 root root 98312 2010-11-13 16:12 normal.mod
-rw-r--r-- 1 root root 3536 2010-11-13 16:12 ntfscomp.mod
-rw-r--r-- 1 root root 9992 2010-11-13 16:12 ntfs.mod
-rw-r--r-- 1 root root 10556 2010-11-13 16:12 ohci.mod
-rw-r--r-- 1 root root 1688 2010-11-13 16:12 part_acorn.mod
-rw-r--r-- 1 root root 1672 2010-11-13 16:12 part_amiga.mod
-rw-r--r-- 1 root root 2112 2010-11-13 16:12 part_apple.mod
-rw-r--r-- 1 root root 2004 2010-11-13 16:12 part_bsd.mod
-rw-r--r-- 1 root root 2284 2010-11-13 16:12 part_gpt.mod
-rw-r--r-- 1 root root 82 2010-11-13 16:12 partmap.lst
-rw-r--r-- 1 root root 2096 2010-11-13 16:12 part_msdos.mod
-rw-r--r-- 1 root root 1792 2010-11-13 16:12 part_sun.mod
-rw-r--r-- 1 root root 1704 2010-11-13 16:12 part_sunpc.mod
-rw-r--r-- 1 root root 17 2010-11-13 16:12 parttool.lst
-rw-r--r-- 1 root root 4488 2010-11-13 16:12 parttool.mod
-rw-r--r-- 1 root root 1904 2010-11-13 16:12 password.mod
-rw-r--r-- 1 root root 2976 2010-11-13 16:12 password_pbkdf2.mod
-rw-r--r-- 1 root root 1328 2010-11-13 16:12 pbkdf2.mod
-rw-r--r-- 1 root root 1184 2010-11-13 16:12 pci.mod
-rw-r--r-- 1 root root 2472 2010-11-13 16:12 play.mod
-rw-r--r-- 1 root root 6620 2010-11-13 16:12 png.mod
-rw-r--r-- 1 root root 2664 2010-11-13 16:12 probe.mod
-rw-r--r-- 1 root root 1024 2010-11-13 16:12 pxeboot.img
-rw-r--r-- 1 root root 1332 2010-11-13 16:12 pxecmd.mod
-rw-r--r-- 1 root root 5588 2010-11-13 16:12 pxe.mod
-rw-r--r-- 1 root root 1400 2010-11-13 16:12 raid5rec.mod
-rw-r--r-- 1 root root 2812 2010-11-13 16:12 raid6rec.mod
-rw-r--r-- 1 root root 6216 2010-11-13 16:12 raid.mod
-rw-r--r-- 1 root root 1564 2010-11-13 16:12 read.mod
-rw-r--r-- 1 root root 1120 2010-11-13 16:12 reboot.mod
-rw-r--r-- 1 root root 38636 2010-11-13 16:12 regexp.mod
-rw-r--r-- 1 root root 9796 2010-11-13 16:12 reiserfs.mod
-rw-r--r-- 1 root root 4104 2010-11-13 16:12 relocator.mod
-rw-r--r-- 1 root root 4128 2010-11-13 16:12 scsi.mod
-rw-r--r-- 1 root root 2168 2010-11-13 16:12 search_fs_file.mod
-rw-r--r-- 1 root root 2336 2010-11-13 16:12 search_fs_uuid.mod
-rw-r--r-- 1 root root 2256 2010-11-13 16:12 search_label.mod
-rw-r--r-- 1 root root 2356 2010-11-13 16:12 search.mod
-rw-r--r-- 1 root root 4920 2010-11-13 16:12 serial.mod
-rw-r--r-- 1 root root 690 2010-11-13 16:12 setjmp.mod
-rw-r--r-- 1 root root 5524 2010-11-13 16:12 setpci.mod
-rw-r--r-- 1 root root 4104 2010-11-13 16:12 sfs.mod
-rw-r--r-- 1 root root 2220 2010-11-13 16:12 sleep.mod
-rw-r--r-- 1 root root 2888 2010-11-13 16:12 tar.mod
-rw-r--r-- 1 root root 124 2010-11-13 16:12 terminal.lst
-rw-r--r-- 1 root root 3476 2010-11-13 16:12 terminal.mod
-rw-r--r-- 1 root root 12740 2010-11-13 16:12 terminfo.mod
-rw-r--r-- 1 root root 5188 2010-11-13 16:12 test.mod
-rw-r--r-- 1 root root 2884 2010-11-13 16:12 tga.mod
-rw-r--r-- 1 root root 1675 2010-11-13 16:12 trig.mod
-rw-r--r-- 1 root root 1276 2010-11-13 16:12 true.mod
-rw-r--r-- 1 root root 5484 2010-11-13 16:12 udf.mod
-rw-r--r-- 1 root root 4672 2010-11-13 16:12 ufs1.mod
-rw-r--r-- 1 root root 4988 2010-11-13 16:12 ufs2.mod
-rw-r--r-- 1 root root 5800 2010-11-13 16:12 uhci.mod
-rw-r--r-- 1 root root 3428 2010-11-13 16:12 usb_keyboard.mod
-rw-r--r-- 1 root root 7876 2010-11-13 16:12 usb.mod
-rw-r--r-- 1 root root 5440 2010-11-13 16:12 usbms.mod
-rw-r--r-- 1 root root 3624 2010-11-13 16:12 usbtest.mod
-rw-r--r-- 1 root root 2736 2010-11-13 16:12 vbeinfo.mod
-rw-r--r-- 1 root root 6676 2010-11-13 16:12 vbe.mod
-rw-r--r-- 1 root root 3048 2010-11-13 16:12 vbetest.mod
-rw-r--r-- 1 root root 4788 2010-11-13 16:12 vga.mod
-rw-r--r-- 1 root root 2288 2010-11-13 16:12 vga_text.mod
-rw-r--r-- 1 root root 5500 2010-11-13 16:12 video_bochs.mod
-rw-r--r-- 1 root root 5744 2010-11-13 16:12 video_cirrus.mod
-rw-r--r-- 1 root root 18716 2010-11-13 16:12 video_fb.mod
-rw-r--r-- 1 root root 33 2010-11-13 16:12 video.lst
-rw-r--r-- 1 root root 5388 2010-11-13 16:12 video.mod
-rw-r--r-- 1 root root 3876 2010-11-13 16:12 videotest.mod
-rw-r--r-- 1 root root 5856 2010-11-13 16:12 xfs.mod
-rw-r--r-- 1 root root 31396 2010-11-13 16:12 xnu.mod
-rw-r--r-- 1 root root 1936 2010-11-13 16:12 xnu_uuid.mod
-rw-r--r-- 1 root root 6208 2010-11-13 16:12 zfsinfo.mod
-rw-r--r-- 1 root root 24384 2010-11-13 16:12 zfs.mod

[rtrask]

Digging a little deeper:

I added the -x option to the grub-install script to get better visibility into what is failing. Here is a snipit of the output.



+ /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=device /boot/grub
+ grub_device=/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3
+ test -f /boot/grub/grubenv
+ /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs --device /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3
/usr/sbin/grub-probe: error: no such disk.
+ fs_module=
+ test x = x -a x = x
+ echo Auto-detection of a filesystem module failed.
Auto-detection of a filesystem module failed.
+ echo Please specify the module with the option `--modules' explicitly.
Please specify the module with the option `--modules' explicitly.
+ exit 1
I'm going to look into getting the source fro grub-probe to see if I can debug it.

[psusi]

/me facepalms

Make sure you are also running the version of (lib)parted from my PPA.

[rtrask]

/me facepalms

Make sure you are also running the version of (lib)parted from my PPA.

I'm not sure what you are warning me of here. Do you know that grub-probe uses (lib)parted? I assume that with the update that down loaded your version of dmraid, that I would have gotten your version of (lib)parted.

I have been thinking that to remove some variables, that I should go back to the standard version of dmraid that comes with 10.10. Is there any reason to continue using your version of dmraid? Is there some other test that you want to run?

[psusi]

Nevermind, I got mixed up a bit. I just noticed something odd though:

util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8 (/dev/dm-1)
util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0 (/dev/dm-2)

Neither of those match the device you are trying to install to, which explains why it later fails trying to open a device with a different name. It's like it doesn't see the third raid volume ( though I'm a little confused about why you have 3 different raid volumes ). What does sudo dmsetup ls show?

[rtrask]

util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 2c8 (/dev/dm-1)
util/deviceiter.c:376: Already seen /dev/mapper/ddf1_4c5349202020202080862925000000004711471100003 cf0 (/dev/dm-2)

Neither of those match the device you are trying to install to, which explains why it later fails trying to open a device with a different name.
The device I'm trying to install to is the dm-1 device. It does see the third device dm-3




It's like it doesn't see the third raid volume ( though I'm a little confused about why you have 3 different raid volumes ).
The reason I have 3 raid volumes is that it matches the disks I have in the system. I have 5 disks & a DVD plugged into my on board SATA controller.

1 90 gig SSD -- used for software/OS (raid 0)
2 1 T drives -- to use for user data / storage (raid 1)
2 156 G drives -- to provide additional space for stuff I don't want to put on the other 2 (SWAP, other distros ...)

I want to boot from the SSD, and in order to do that and have BIOS set to RAID, I had to create a RAID array with a single device the SSD. It is probably possible to side step the bug in grub-probe if I reconfigure everything. But for now I am can live with the current behavior. I continue to pursue this to help make Ubuntu better.


What does sudo dmsetup ls show?


root@Hosea-14-4:/home/rtrask# dmsetup ls
ddf1_4c5349202020202080862925000000004711471100003 2c8 (252, 1)
ddf1_4c5349202020202080862925000000004711471100003 cf0p1 (252, 8)
ddf1_4c5349202020202080862925000000004711471100003 cf0 (252, 2)
ddf1_4c5349202020202080862925000000004711471100002 8a0 (252, 0)
ddf1_4c5349202020202080862925000000004711471100003 cf0p9 (252, 13)
ddf1_4c5349202020202080862925000000004711471100002 8a0p4 (252, 6)
ddf1_4c5349202020202080862925000000004711471100003 cf0p8 (252, 12)
ddf1_4c5349202020202080862925000000004711471100002 8a0p3 (252, 5)
ddf1_4c5349202020202080862925000000004711471100003 cf0p7 (252, 11)
ddf1_4c5349202020202080862925000000004711471100002 8a0p2 (252, 4)
ddf1_4c5349202020202080862925000000004711471100003 cf0p6 (252, 10)
ddf1_4c5349202020202080862925000000004711471100002 8a0p1 (252, 3)
ddf1_4c5349202020202080862925000000004711471100003 2c8p1 (252, 7)
ddf1_4c5349202020202080862925000000004711471100003 cf0p5 (252, 9)

[rtrask]

I have created a bug report on this issue.

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/677857

I'm going to go back to a clean install of Ubuntu 10.10 to facilitate that effort.

[psusi]

The device I'm trying to install to is the dm-1 device. It does see the third device dm-3

It doesn't seem to be. You were trying to install to /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3, which seems to be dm-5, and is not seen at all by grub-probe.

[rtrask]

It doesn't seem to be. You were trying to install to /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3, which seems to be dm-5, and is not seen at all by grub-probe.

Well, I'm a bit confused by your terminology, but you may have a point. The output of the grub-probe command that you gave me only shows 2 devices. I'm not sure why that would be. But the install device is /dev/dm-1 or /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
The root partition is in /dev/dm-5 which is
/dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3, but that is mounted as /target.

grub-install [OPTION] install_device

[psusi]

So you are trying to install grub to one disk using the root partition on the other? The problem seems to be that for some reason, grub isn't seeing the one with /target on it.

[rtrask]

So you are trying to install grub to one disk using the root partition on the other? The problem seems to be that for some reason, grub isn't seeing the one with /target on it.

This is a standard dual boot install. the partition where Linux is installed is ...0032c8p3 the device with the MBR is ...0032c8.

I see now why you were saying device.


/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs --device /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0p3
/usr/s

When I read it previously I thought you meant the install device.

grub-install [OPTION] install_device
The terminology is a bit fuzzy.

[rtrask]

I think I have found a site which has a solution to the problems that I have been having.

http://us.generation-nt.com/answer/bug-603319-dmraid-activate-silently-fails-active-raid1-array-help-201057181.html#r

[psusi]

I saw the fix for that hit the debian git repository yesterday and thought it might have something to do with this.

[TwiceOver]

Ugh... Just building up my new home server with a bunch of raid disks and GRUB just wont install no matter what I do. Think I'll fail back to 9.10 which I know worked with raid.

[rtrask]

I saw the fix for that hit the debian git repository yesterday and thought it might have something to do with this.

Unfortunately it is not a fix, at least not if you have more than 1 RAID array. I think there are some necessary code changes, but I believe that it points to the same problem.

[rtrask]

Ugh... Just building up my new home server with a bunch of raid disks and GRUB just wont install no matter what I do. Think I'll fail back to 9.10 which I know worked with raid.

Well, I think that the problem exists in 9.10 as well. There was a change between dmraid 1.0.0.rc14 & libdmraid1.0.0.rc16 that caused this. The issue has to do with DDF1 format raid arrays, which is related to at least the LSI bios.

See: bug-603319-dmraid-activate-silently-fails-active-raid1-array-help-201057181 (http://us.generation-nt.com/answer/bug-603319-dmraid-activate-silently-fails-active-raid1-array-help-201057181.html#r)

There may be more than one issue, grub-probe is failing as well. Let me know if 9.10 installs for you.

[Johnrl]

Does any one know if the fix ever made it in to 10.10 for the grub install as discussed in this link? http://ubuntuforums.org/showthread.php?t=1573192&page=7

If so, I think that there are still issues. Perhaps it is my configuration, but it seems like it should work.

Here is my set up:
Intel S5500HCV dual CPU 5520
latest BIOS
software raid 3 Arrays
RAID 0 - configured as boot 1 SSD 90G 3 partitions Windows 7 installed first 2, 10.10 installed on 3rd
RAID 0 - 2 158 gig disks 2 partitions swap first partition, and remainder /opt
RAID 1 - 2 1T drives 1 partition /home



(an aside: My thinking is to use SSD for the software, and mirrored disks for user data, and the raid 0 with swap so I don't waste the limited SSD for swap that will probably never be used. The of the raid 0 /opt for transient data like video that I am working on)

This is the process that I followed to install


Loaded Windows 7 - create 50 G partition for windows leave remainder for linux -- no issues
load live CD to try, then in console do a "sudo dmraid -ay" (the install see the raid arrays asks to install raid software, but does not activate the raid arrays. what's up with that)
click install and go through normal steps until partition
I do manual partition, create 3rd partition on SSD format EXT4 set as root
create partitions on other 2 disks as described above
set boot device to /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0 which is the device for the first array containing the SSD
let it rip

The rest of the install is uneventful until the grub install fails. I've tried mounting the intall on /target/ and chroot to it. and then
root@ubuntu:/# grub-install --root-directory=/ /dev/mapper/ddf1_4c5349202020202080862925000000004711471100002 8a0
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
My problem seems very similar to the one described in the link above. The fact hat it is closed would lead me to believe that the patch was incorporated in 10.10 when it went GA, but maybe not. Any ideas?

I have attached the RESULTS.txt file from running boot_info_script055.sh
installed Ububtu 10.10 on a raid 0 hard disk.
I first tried the ordinary ubuntu 10.10 it will not work in you case useless.
my first step was shrink the raid 0 volume in windows 7
I did no do anything to the free space.

I downloaded the alternate ubuntu 10.10
which gives support for raid disks.

when you get to the part which deals with hard disks
pick raid disk
use free space on disk
the installation will take place
and you should get a grub boot
with ubuntu and linux at the end.

p.s. you can install any programs normally on the dvd
from the
applications
ubuntu software centre

good luck installing ubuntu 10.10
(an aside: My thinking is to use SSD for the software, and mirrored disks for user data, and the raid 0 with swap so I don't waste the limited SSD for swap that will probably never be used. The of the raid 0 /opt for transient data like video that I am working on)

[rtrask]

Looks like 11.04 solved all of my issues, (well not all of my issues :) ) but life is much better since I rebuilt my system to 11.04 as far as the issues with RAID

[Quackers]

That's odd, because 10-10 installed fine on my Intel RAID0 system, but 11-04 needed the kpartx package installing to the live desktop first.