Re: [SLUG] How do I mount a RAID1 disk?
Oh hi Mike, Raid 1 you should be able to mount as it's native filesystem for recovery in read-only mode. EG mount -t ext2 -o /dev/sdb3 /mnt/recovery You mentioned LVM. That's going to be your problem for now. You need to make sure you have the lvm2 tools installed. Try 'pvscan' it should list the physical volumes (aka partitions in this case). 'vgchange -ay' should 'activate' all the volume groups. Then if that's done you should now find you've got some logical volumes... 'lvscan' will tell you. Then it's going to be something like... mount -o ro -t ext2 /dev/VolumeGroup/LogicalVolume /mnt/recovery Note that I use the -o ro to mount read-only as you're less likely to fsck up the data. On Wed, 3 Dec 2008, Michael Lake wrote: Hi all I am trying to get data off someones old machine that died and place it onto a new machine for them. The old machine had two Western Digital IDE drives as RAID1. I have inserted one of the drives into a new machine in place of the CDROM drive and connected it's IDE cable up and it shows up as /dev/sdc /dev/sdc sdc1 sdc2 sdc3 sdc5 Both of the drives show the same info above. By trying mount I can see that partition 2 is the swap, 1 is probably a /boot and the data that I wish to retrieve is on either or both of 3 or 5. See Try to mount the Partitions below. I also used mdadm to get some detailed info on sdc5 (see below). My problem is that I can't work out how to mount sdc3 (have tried -t ext3, -t reiserfs, -t auto) or sdc5. The latter is probably the one I want. I gather the partition table says it 'mdraid' and I need to change that? I have two drives, and both give the same info. I just need to mount ONE of them and copy the data off it. I don't want to try and setup the original raid. (PS: the machine I have one of them installed on is using mdraid and LVM) Try to mount the Partitions --- # mount -r /dev/sdc1 /mnt mount: unknown filesystem type 'mdraid' # mount -r /dev/sdc2 /mnt /dev/sdc2 looks like swapspace - not mounted mount: you must specify the filesystem type # mount -r /dev/sdc3 /mnt mount: you must specify the filesystem type # mount -r /dev/sdc5 /mnt mount: unknown filesystem type 'mdraid' Use mdadm to examine these partitions - # /sbin/mdadm --examine /dev/sdc2 mdadm: No md superblock detected on /dev/sdc2 -- as it's swap OK # /sbin/mdadm --examine /dev/sdc3 mdadm: No md superblock detected on /dev/sdc3 # /sbin/mdadm --examine /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 00.90.00 UUID : b6035660:c11a8a2e:7026aea2:99d23bfc Creation Time : Wed May 14 15:10:36 2003 Raid Level : raid1 Used Dev Size : 108486848 (103.46 GiB 111.09 GB) Array Size : 108486848 (103.46 GiB 111.09 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Tue Aug 5 21:07:20 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : b9113923 - correct Events : 0.8311948 Number Major Minor RaidDevice State this 0 3350 active sync 0 0 3350 active sync 1 1 3451 active sync [EMAIL PROTECTED] dev]# -- ---GRiP--- Grant Parnell - LPIC-1 certified engineer EverythingLinux services - the consultant's backup tech support. Web: http://www.elx.com.au/support.php We're also busybits.com.au and linuxhelp.com.au and everythinglinux.com.au. Phone 02 8756 3522 to book service or discuss your needs or email us at paidsupport at elx.com.au ELX or its employees participate in the following:- OSIA (Open Source Industry Australia) - http://www.osia.net.au AUUG (Australian Unix Users Group) - http://www.auug.org.au SLUG (Sydney Linux Users Group) - http://www.slug.org.au LA (Linux Australia) - http://www.linux.org.au -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] How do I mount a RAID1 disk?
Hi all I am trying to get data off someones old machine that died and place it onto a new machine for them. The old machine had two Western Digital IDE drives as RAID1. I have inserted one of the drives into a new machine in place of the CDROM drive and connected it's IDE cable up and it shows up as /dev/sdc /dev/sdc sdc1 sdc2 sdc3 sdc5 Both of the drives show the same info above. By trying mount I can see that partition 2 is the swap, 1 is probably a /boot and the data that I wish to retrieve is on either or both of 3 or 5. See Try to mount the Partitions below. I also used mdadm to get some detailed info on sdc5 (see below). My problem is that I can't work out how to mount sdc3 (have tried -t ext3, -t reiserfs, -t auto) or sdc5. The latter is probably the one I want. I gather the partition table says it 'mdraid' and I need to change that? I have two drives, and both give the same info. I just need to mount ONE of them and copy the data off it. I don't want to try and setup the original raid. (PS: the machine I have one of them installed on is using mdraid and LVM) Try to mount the Partitions --- # mount -r /dev/sdc1 /mnt mount: unknown filesystem type 'mdraid' # mount -r /dev/sdc2 /mnt /dev/sdc2 looks like swapspace - not mounted mount: you must specify the filesystem type # mount -r /dev/sdc3 /mnt mount: you must specify the filesystem type # mount -r /dev/sdc5 /mnt mount: unknown filesystem type 'mdraid' Use mdadm to examine these partitions - # /sbin/mdadm --examine /dev/sdc2 mdadm: No md superblock detected on /dev/sdc2 -- as it's swap OK # /sbin/mdadm --examine /dev/sdc3 mdadm: No md superblock detected on /dev/sdc3 # /sbin/mdadm --examine /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 00.90.00 UUID : b6035660:c11a8a2e:7026aea2:99d23bfc Creation Time : Wed May 14 15:10:36 2003 Raid Level : raid1 Used Dev Size : 108486848 (103.46 GiB 111.09 GB) Array Size : 108486848 (103.46 GiB 111.09 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Tue Aug 5 21:07:20 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : b9113923 - correct Events : 0.8311948 Number Major Minor RaidDevice State this 0 3350 active sync 0 0 3350 active sync 1 1 3451 active sync [EMAIL PROTECTED] dev]# -- Michael Lake Computational Research Centre of Expertise Science Faculty, UTS Ph: 9514 2238 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Michael Lake [EMAIL PROTECTED]: Hi all I am trying to get data off someones old machine that died and place it onto a new machine for them. The old machine had two Western Digital IDE drives as RAID1. I have inserted one of the drives into a new machine in place of the CDROM drive and connected it's IDE cable up and it shows up as /dev/sdc /dev/sdc sdc1 sdc2 sdc3 sdc5 Both of the drives show the same info above. By trying mount I can see that partition 2 is the swap, 1 is probably a /boot and the data that I wish to retrieve is on either or both of 3 or 5. See Try to mount the Partitions below. I also used mdadm to get some detailed info on sdc5 (see below). My problem is that I can't work out how to mount sdc3 (have tried -t ext3, -t reiserfs, -t auto) or sdc5. The latter is probably the one I want. I gather the partition table says it 'mdraid' and I need to change that? [snip] Hey, Try starting the raid array with a missing member and then mounting the resulting md device. # mdadm --assemble --run --uuid b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 # mount /dev/md1 /mnt N.B. I haven't checked the syntax, you may need to add /dev/md1 to the mdadm line.. I don't have a box in front of me to check... The general idea should be right though.. cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Owen Townend [EMAIL PROTECTED]: 2008/12/3 Michael Lake [EMAIL PROTECTED]: Hi all I am trying to get data off someones old machine that died and place it onto a new machine for them. The old machine had two Western Digital IDE drives as RAID1. I have inserted one of the drives into a new machine in place of the CDROM drive and connected it's IDE cable up and it shows up as /dev/sdc /dev/sdc sdc1 sdc2 sdc3 sdc5 Both of the drives show the same info above. By trying mount I can see that partition 2 is the swap, 1 is probably a /boot and the data that I wish to retrieve is on either or both of 3 or 5. See Try to mount the Partitions below. I also used mdadm to get some detailed info on sdc5 (see below). My problem is that I can't work out how to mount sdc3 (have tried -t ext3, -t reiserfs, -t auto) or sdc5. The latter is probably the one I want. I gather the partition table says it 'mdraid' and I need to change that? [snip] Hey, Try starting the raid array with a missing member and then mounting the resulting md device. # mdadm --assemble --run --uuid b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 # mount /dev/md1 /mnt N.B. I haven't checked the syntax, you may need to add /dev/md1 to the mdadm line.. I don't have a box in front of me to check... The general idea should be right though.. cheers, Owen. You can give 'missing' as a component device name along with /dev/sdc5 if mdadm gives a 'not enough devices' type error. cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
Hi Own and all Owen Townend wrote: # mdadm --assemble --run --uuid b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 # mount /dev/md1 /mnt N.B. I haven't checked the syntax, you may need to add /dev/md1 to the mdadm line.. I don't have a box in front of me to check... The general idea should be right though.. You can give 'missing' as a component device name along with /dev/sdc5 if mdadm gives a 'not enough devices' type error. Okies I worked out to give the uuid its -u or --uuid= so I'm using -u and the magic number from the --examine output. Here is what I tried. # /sbin/mdadm --assemble --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 missing mdadm: cannot open device missing: No such file or directory mdadm: missing has wrong uuid. mdadm: no devices found for /dev/sdc5 I then tried specifying the /dev/md1 # /sbin/mdadm --assemble --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/md1 /dev/sdc5 missing mdadm: no recogniseable superblock on /dev/sdc5 mdadm: /dev/sdc5 has wrong uuid. mdadm: cannot open device missing: No such file or directory mdadm: missing has wrong uuid. mdadm: no devices found for /dev/md1 In the above I added /dev/md1 for it to be assembled onto. By the way I do have a /dev/md1 existing already. But no /dev/md0 (Also this new machine I'm trying to mount it on is a raid system using mdraid which I gather is different software for raid to mdadm. I think the older machine used mdadm and this new machine uses mdraid. It was setup by a previous sysadmin so I'm learning.) Mike -- Michael Lake Computational Research Centre of Expertise Science Faculty, UTS Ph: 9514 2238 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Michael Lake [EMAIL PROTECTED]: Hi Own and all Owen Townend wrote: # mdadm --assemble --run --uuid b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 # mount /dev/md1 /mnt N.B. I haven't checked the syntax, you may need to add /dev/md1 to the mdadm line.. I don't have a box in front of me to check... The general idea should be right though.. You can give 'missing' as a component device name along with /dev/sdc5 if mdadm gives a 'not enough devices' type error. Okies I worked out to give the uuid its -u or --uuid= so I'm using -u and the magic number from the --examine output. Here is what I tried. # /sbin/mdadm --assemble --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 missing mdadm: cannot open device missing: No such file or directory mdadm: missing has wrong uuid. mdadm: no devices found for /dev/sdc5 I then tried specifying the /dev/md1 # /sbin/mdadm --assemble --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/md1 /dev/sdc5 missing mdadm: no recogniseable superblock on /dev/sdc5 mdadm: /dev/sdc5 has wrong uuid. mdadm: cannot open device missing: No such file or directory mdadm: missing has wrong uuid. mdadm: no devices found for /dev/md1 In the above I added /dev/md1 for it to be assembled onto. By the way I do have a /dev/md1 existing already. But no /dev/md0 (Also this new machine I'm trying to mount it on is a raid system using mdraid which I gather is different software for raid to mdadm. I think the older machine used mdadm and this new machine uses mdraid. It was setup by a previous sysadmin so I'm learning.) Mike I pulled the /dev/md1 from the 'prefered minor' that was in the examine output. You can use a different one without hassle. The ordering for the command is: Usage: mdadm --assemble md-device options-and-component-devices... The '--run' is because with a missing device it would usually only assemble the array and leave it stopped which is the safest default. Try # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
Michael Lake wrote: (Also this new machine I'm trying to mount it on is a raid system using mdraid Oops. I meant dmraid not mdraid This should not affect trying to mount the old raid disk - I hope. Mike -- Michael Lake Computational Research Centre of Expertise Science Faculty, UTS Ph: 9514 2238 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Michael Lake [EMAIL PROTECTED]: Michael Lake wrote: (Also this new machine I'm trying to mount it on is a raid system using mdraid Oops. I meant dmraid not mdraid This should not affect trying to mount the old raid disk - I hope. Mike Hey, dmraid I believe is the linux implementation of 'fakeraid' - the onboard motherboard raid. In my understanding this has none of the benefits of either software _or_ hardware raid and many of the pitfalls. With the buzz-word 'fakeraid' it should be trivial to find more info if you so desire. dmraid and mdadm can co-exist quite happily, they should choose non-conflicting /dev/ nodes and/or fail gracefully. By placing /dev/md1 where you did in the mdadm command line you were effectively listing it as a component device of the array you were trying to start. Not a problem, but not the desired result. I'm not sure why 'missing' didn't work, perhaps it is a 'create' mode only option. How'd you go? cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
Owen Townend wrote: I pulled the /dev/md1 from the 'prefered minor' that was in the examine output. You can use a different one without hassle. The ordering for the command is: Usage: mdadm --assemble md-device options-and-component-devices... So it assembles physical devices onto the virtual /dev/md0 The '--run' is because with a missing device it would usually only assemble the array and leave it stopped which is the safest default. OK Try # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 No recognisable superblock on /dev/sdc5 dev/sdc5 has wrong uuid No devices found for /dev/md0 BUT! I tried it with sdc1 using it's uuid and it works! I message came up that /dev/md0 has been started with 1 drive out of 2 Then mount /dev/md0 /mnt worked and I can see the files and directories. I can now see the old /etc/fstab and it tells me that it was a reiserfs system. What I don't follow is that now If I run: /sbin/mdadm --examine /dev/sdc5 No md superblock detected on /dev/sdc5 where as before it said /dev/sdc5: Magic : a92b4efc etc I have some playing to do to work it out but am now much relived I can see data. Mike -- Michael Lake Computational Research Centre of Expertise Science Faculty, UTS Ph: 9514 2238 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Michael Lake [EMAIL PROTECTED]: Owen Townend wrote: I pulled the /dev/md1 from the 'prefered minor' that was in the examine output. You can use a different one without hassle. The ordering for the command is: Usage: mdadm --assemble md-device options-and-component-devices... So it assembles physical devices onto the virtual /dev/md0 The '--run' is because with a missing device it would usually only assemble the array and leave it stopped which is the safest default. OK Try # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 No recognisable superblock on /dev/sdc5 dev/sdc5 has wrong uuid No devices found for /dev/md0 BUT! I tried it with sdc1 using it's uuid and it works! I message came up that /dev/md0 has been started with 1 drive out of 2 Then mount /dev/md0 /mnt worked and I can see the files and directories. I can now see the old /etc/fstab and it tells me that it was a reiserfs system. What I don't follow is that now If I run: /sbin/mdadm --examine /dev/sdc5 No md superblock detected on /dev/sdc5 where as before it said /dev/sdc5: Magic : a92b4efc etc I have some playing to do to work it out but am now much relived I can see data. Mike Hey, I know I put in the disclaimer that I hadn't checked the syntax, but I still feel bad that I now realise that the initial command may have tried to use /dev/sdc5 as the node for the resultant raid array. This may be the culprit for the missing superblock. You are in a good position though having both the original --examine data (if you wish to recreate the superblock) and a second copy of the data (the other disk from the mirror). Hope it works out ok... cheers, Owen. N.B. Read the man pages, check the syntax, only then then run commands as root on data you're trying to recover... -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
Hi all Owen can go home tonight knowing that it all is working fine for me and thanks for enabling me to get access to the data I needed. Owen Townend wrote: I know I put in the disclaimer that I hadn't checked the syntax, but I still feel bad that I now realise that the initial command may have tried to use /dev/sdc5 as the node for the resultant raid array. This may be the culprit for the missing superblock. You are in a good position though having both the original --examine data (if you wish to recreate the superblock) and a second copy of the data (the other disk from the mirror). No probs. I just rebooted the host machine I'm copying this stuff onto and when it came up again I did a /sbin/mdadm --examine /dev/sdc5 and now it shows all the details for it like before. So I did your # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 and then mounted it OK. So now I'm copying stuff off this partition fine. I have copied the stuff off partition 1 OK too. Owen Townend wrote: Try # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 No recognisable superblock on /dev/sdc5 dev/sdc5 has wrong uuid No devices found for /dev/md0 BUT! I tried it with sdc1 using it's uuid and it works! I message came up that /dev/md0 has been started with 1 drive out of 2 Then mount /dev/md0 /mnt worked and I can see the files and directories. I can now see the old /etc/fstab and it tells me that it was a reiserfs system. What I don't follow is that now If I run: /sbin/mdadm --examine /dev/sdc5 No md superblock detected on /dev/sdc5 where as before it said /dev/sdc5: Magic : a92b4efc etc I have some playing to do to work it out but am now much relived I can see data. Hope it works out ok... cheers, Owen. N.B. Read the man pages, check the syntax, only then then run commands as root on data you're trying to recover... -- Michael Lake Computational Research Centre of Expertise Science Faculty, UTS Ph: 9514 2238 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] How do I mount a RAID1 disk?
2008/12/3 Michael Lake [EMAIL PROTECTED]: Hi all Owen can go home tonight knowing that it all is working fine for me and thanks for enabling me to get access to the data I needed. Owen Townend wrote: I know I put in the disclaimer that I hadn't checked the syntax, but I still feel bad that I now realise that the initial command may have tried to use /dev/sdc5 as the node for the resultant raid array. This may be the culprit for the missing superblock. You are in a good position though having both the original --examine data (if you wish to recreate the superblock) and a second copy of the data (the other disk from the mirror). No probs. I just rebooted the host machine I'm copying this stuff onto and when it came up again I did a /sbin/mdadm --examine /dev/sdc5 and now it shows all the details for it like before. So I did your # /sbin/mdadm --assemble /dev/md0 --run -u b6035660:c11a8a2e:7026aea2:99d23bfc /dev/sdc5 and then mounted it OK. So now I'm copying stuff off this partition fine. I have copied the stuff off partition 1 OK too. [snip] Great to hear it worked in the end! cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
