fake-RADI0 detected by Yast but not mounted after restart

albercik_22 · April 20, 2011, 12:15pm

Hi Community,
Im newbie, browsed through forum and found some simililar issues but not exactly what I was looking for. So here comes my problem: I have fake(bios) raid0 with Windows XP and third non-raid hd which I wanted use to install linux to (as I read about problems with installing grub into raid0).
During installation Yast had correctly detected raids and all windows partitions (basically its divided into two raids with 2 partitions of 1st and 3 on 2nd) and even proposed mounting them at /windows/c, /windows/d and so on.
Now I have OpenSuse 11.4 installed, grub at /boot on sdc but to log to system I need to use installation disc (otherwise Windows starts up). What I wanted to do is follow this tutorial to add grub to Windows bootloader: Boot Multiboot openSUSE Windows (2000, XP, Vista - any mix) with Windows bootloader.
Problem is after reboot partitions are not mounted (dirs exists but nothing there) so I cannot copy boot code to windows. I read that fake raid may need special drivers but when i start Yast->system->partitions it again shows everything correctly!

fragment from partitions section in Yast (I translated/removed non-important entries as I have non-English system so it may vary from what is actually in Eng version):


Device: /dev/md125p1
Size: 48.83 GB
Device path: 
Device 1 id: md-uuid-41ef407f:0fdf61b6:f0753e61:af96c24e-part1
File system id: 0x07 HPFS/NTFS
Mounting point: /windows/E *

when I do ls /dev/disk/by-id/


ata-SAMSUNG_HD322HJ_S17AJ90Q610255             md-uuid-070b33d4:a3d58399:b57a5dd5:786e6142    scsi-SATA_SAMSUNG_HD642JJS1AFJ1CQ600858
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part1       md-uuid-41ef407f:0fdf61b6:f0753e61:af96c24e    wwn-0x50000f0008068084
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part2       md-uuid-efa602a9:7a46e269:02bf8c05:159d051a    wwn-0x50000f0008068085
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part3       scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255        wwn-0x50000f000b162055
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part5       scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part1  wwn-0x50000f000b162055-part1
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part6       scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part2  wwn-0x50000f000b162055-part2
ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part7       scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part3  wwn-0x50000f000b162055-part3
ata-SAMSUNG_HD642JJ_S1AFJ1CQ600848             scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part5  wwn-0x50000f000b162055-part5
ata-SAMSUNG_HD642JJ_S1AFJ1CQ600858             scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part6  wwn-0x50000f000b162055-part6
ata-TSSTcorp_CDDVDW_SH-S223B_0i23454789KLMNOP  scsi-SATA_SAMSUNG_HD322HJS17AJ90Q610255-part7  wwn-0x50000f000b162055-part7
edd-int13_dev82                                scsi-SATA_SAMSUNG_HD642JJS1AFJ1CQ600848

btw, there is nothing like /dev/md125p1 just /dev/md125 which is 1st raid and not partition on raid

and cat /etc/fstab


/dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part6 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part3 /boot                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part7 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/md-uuid-070b33d4:a3d58399:b57a5dd5:786e6142-part1 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0
/dev/disk/by-id/md-uuid-070b33d4:a3d58399:b57a5dd5:786e6142-part2 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0
/dev/disk/by-id/md-uuid-41ef407f:0fdf61b6:f0753e61:af96c24e-part1 /windows/E           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0
/dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90Q610255-part1 /windows/F           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0
/dev/disk/by-id/md-uuid-41ef407f:0fdf61b6:f0753e61:af96c24e-part5 /windows/G           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

basically I see that it should be md-uuid-part1 what is mounted while its not present in /dev
should it be wwn maybe? and how is it that Yast/system/partitioning shows it correctly?

Thanks

jdmcdaniel3 · April 20, 2011, 1:00pm

One issue I see is you can’t use the /dev/disk/by-id/ since that points to a single hard drive. I am thinking this must be a logical name which is normally /dev/sda1/ or /dev/sda2 and so forth but perhaps its even /dev/md125p1 but not what you have in your fstab file at the moment. Same goes for the /boot/grub/device.map file which also tries to use /dev/disk/by-id.

Thank You,

albercik_22 · April 20, 2011, 1:44pm

Thanks for Your reply,
Actually I didn’t change anything yet. fstab in this form was created by Yast and during installation it just proposed this (by-id). As far as I remember there were also other options (like in /dev/disk/by-) but since it correctly showed all partitions (and I have no knowledge about all this stuff:) I agreed to that. Anyway I looked also into those by- and there is really nothing that could distinguish between partitions, just raids. Is it like I should have just one partition per raid?

gogalthorp · April 20, 2011, 5:12pm

I’d not allow the installer or Yast to mount those RAIDed partitions. If it can be done at all (FAKE RAID and Linux do not get along) you will need to mount by hand in the fstab.

albercik_22 · April 20, 2011, 8:08pm

That’s what I was afraid of.
I have no idea how to do this as nothing under /dev/disk looks like partitions on raid. And yet Yast detects it somehow.
But actually I can live without this All I want to do is to (dual)boot to either Windows or Linux and I needed mount just for copying boot code (as in link). Is it possible to copy boot code with replacing
dd if=/dev/sda3 of=/mnt/windows/suse.bin bs=512 count=1
to, for example (/dev/sdc3 is my /boot)
dd if=/dev/sdc3 of=/home/suse.bin bs=512 count=1
copy suse.bin to pendrive and then boot to Windows and copy to c:/? then just follow rest of tutorial (update boot.ini). Does it make sense?

gogalthorp · April 21, 2011, 1:56am

You don’t need to mount anything to use dd. It is a raw binary copy function.

albercik_22 · April 21, 2011, 1:22pm

Thanks for info,
So how to set ‘of’ parameter? There is no /dev/md125p1 in /dev and I guess /dev/md125 is not correct (and I don’t want to destroy raid array)?

gogalthorp · April 21, 2011, 5:02pm

Sorry until you set up a working connection to the array don’t fool with it in any way. If this was a RAID 1 then it might be ok but in RAID 0 only 1/2 the data is on the each drive ie ever other sector is on the other drive. Until this can be read (with FAKE I’m not sure it can) properly the bet you can do is get ever other sector on a dd operation. In no circumstance do writes. dd simply does reads from the source so you can copy sectors. But you must be very very careful not to write the command wrong. If you mess up there is no recovery in RAID 0. If you lose or mess the data on one drive all is lost.