LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   mounting existing mirror in new installation (https://www.linuxquestions.org/questions/fedora-35/mounting-existing-mirror-in-new-installation-306256/)

Astro_ortsa 03-26-2005 06:49 AM

mounting existing mirror in new installation
 
Hi all,

I am new to this forum and this site.. Hope I do well.

Yesterday, I lost my boot drive on an old readhat 8 machine I have home. MY data was on a mirror on two seperate drive. Now I am trying to mount that mirror but I don't have any luck.

Here's some info about /dev/md0
mdadm --detail --scan

ARRAY /dev/md0 level=raid1 num-devices=2
UUID=45e17d10:10cb40b2:e3a34893:65826590
devices=/dev/hdc1,/dev/hdd1


cat /proc/mdstat

Personalities : [raid1]
md0 : active raid1 hdd1[1] hdc1[0]
9020352 blocks [2/2] [UU]

unused devices: <none>


When I try to mount /dev/md0 I got this:
mount /dev/md0 /mnt/data/

mount: /dev/md0: can't read superblock


And /var/log/messages show this

Mar 26 07:43:14 localhost kernel: FAT: Did not find valid FSINFO signature.
Mar 26 07:43:14 localhost kernel: Found signature1 0x00000000 signature2 0x00000000 (sector = 1)
Mar 26 07:43:14 localhost kernel: FAT: Filesystem panic (dev md0)
Mar 26 07:43:14 localhost kernel: invalid access to FAT (entry 0x0e94871b)
Mar 26 07:43:14 localhost kernel: File system has been set read-only


I have read howto's and groups and manpages for the last 6 hours and still does not have a clue what to do. I would love not to lose my data.

Since this seems to be a FAT system, maybe there a way to read it and I could rebuild the mirror after.

Any suggestions from linux gurus would be appreciated.

Regards,

Simon

Astro_ortsa 03-26-2005 07:35 AM

More info
 
Here's more info on the two drives attached on /dev/md0

mdadm --examine /dev/hdc1

/dev/hdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45e17d10:10cb40b2:e3a34893:65826590
Creation Time : Wed Apr 9 16:48:26 2003
Raid Level : raid1
Device Size : 9020352 (8.60 GiB 9.24 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Mar 25 09:32:48 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ca61086c - correct
Events : 0.62


Number Major Minor RaidDevice State
this 0 22 1 0 active sync /dev/hdc1
0 0 22 1 0 active sync /dev/hdc1
1 1 22 65 1 active sync /dev/hdd1
[root@localhost etc]# mdadm --examine /dev/hdd1
/dev/hdd1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45e17d10:10cb40b2:e3a34893:65826590
Creation Time : Wed Apr 9 16:48:26 2003
Raid Level : raid1
Device Size : 9020352 (8.60 GiB 9.24 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Mar 25 09:32:48 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ca6108ae - correct
Events : 0.62


Number Major Minor RaidDevice State
this 1 22 65 1 active sync /dev/hdd1
0 0 22 1 0 active sync /dev/hdc1
1 1 22 65 1 active sync /dev/hdd1


mdadm --examine /dev/hdd1

/dev/hdd1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45e17d10:10cb40b2:e3a34893:65826590
Creation Time : Wed Apr 9 16:48:26 2003
Raid Level : raid1
Device Size : 9020352 (8.60 GiB 9.24 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Mar 25 09:32:48 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ca6108ae - correct
Events : 0.62


Number Major Minor RaidDevice State
this 1 22 65 1 active sync /dev/hdd1
0 0 22 1 0 active sync /dev/hdc1
1 1 22 65 1 active sync /dev/hdd1
[root@localhost etc]# man mount
[root@localhost etc]# mdadm --examine /dev/hdc1
/dev/hdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45e17d10:10cb40b2:e3a34893:65826590
Creation Time : Wed Apr 9 16:48:26 2003
Raid Level : raid1
Device Size : 9020352 (8.60 GiB 9.24 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Mar 25 09:32:48 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ca61086c - correct
Events : 0.62


Number Major Minor RaidDevice State
this 0 22 1 0 active sync /dev/hdc1
0 0 22 1 0 active sync /dev/hdc1
1 1 22 65 1 active sync /dev/hdd1


I also find this in /etc/

blkid.tab

<device DEVNO="0x1601" TIME="1111807319" UUID="0c850c81-d3e3-4b1b-a049-cf576a922563" SEC_TYPE="ext3" TYPE="ext2">/dev/hdc1</device>
<device DEVNO="0x1641" TIME="1111807319" UUID="0c850c81-d3e3-4b1b-a049-cf576a922563" SEC_TYPE="ext3" TYPE="ext2">/dev/hdd1</device>


rc.sysinit

echo "raidautorun /dev/md0" | nash --quiet


If I read correctly, the two member of md0 are type=ext2 but /var/log/message complains about FAT?

Again, I am in the dark here.... Any suggestions

Thanks,

Simon

Astro_ortsa 03-26-2005 08:36 AM

Solved
 
OK, I think I was too tired to see the obvious, or was trying to find problem when there was none... I forgot to mount with"-t ext3". By not mounting with -t ext3, I was misleaded into weird problem solving, thinking that fedora C3 was different that redhat 8.

My data is back.

Simon


All times are GMT -5. The time now is 05:07 PM.