NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Jun 27, 2013Disk mount x86 in Linux LVM HELP
So I have a readynas ultra 2 with 2 TB drives that got that whole "Missing shares error" thing.
So I thought that I would take one of the drives, mount it in linux (ive done this b4), and reset the other drive to copy the data.
But it looks like the data partition is missing the superblock and wont mount correctly.
Any ideas? Or a way to force mount the data partition just to copy the data?
So I thought that I would take one of the drives, mount it in linux (ive done this b4), and reset the other drive to copy the data.
But it looks like the data partition is missing the superblock and wont mount correctly.
Any ideas? Or a way to force mount the data partition just to copy the data?
knoppix@Microknoppix:~$ sudo su
root@Microknoppix:/home/knoppix# apt-get install mdadm lvm2
Reading package lists... Done
Building dependency tree
Reading state information... Done
lvm2 is already the newest version.
mdadm is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 551 not upgraded.
root@Microknoppix:/home/knoppix# mdadm --assemble --scan
mdadm: /dev/md/1 has been started with 1 drive (out of 2).
mdadm: /dev/md/0 has been started with 1 drive (out of 2).
root@Microknoppix:/home/knoppix# modprobe dm-mod
root@Microknoppix:/home/knoppix# vgscan
Reading all physical volumes. This may take a while...
No volume groups found
root@Microknoppix:/home/knoppix# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc1[2]
4193268 blocks super 1.2 [2/1] [U_]
md1 : active raid1 sdc2[2]
524276 blocks super 1.2 [2/1] [U_]
unused devices: <none>
root@Microknoppix:/home/knoppix# mdadm -v --assemble --auto=yes /dev/md2 /dev/sdc3
mdadm: looking for devices for /dev/md2
mdadm: no recogniseable superblock on /dev/sdc3
mdadm: /dev/sdc3 has no superblock - assembly aborted
root@Microknoppix:/home/knoppix# dumpe2fs /dev/md0 | grep -i superblock
dumpe2fs 1.42.4 (12-Jun-2012)
Primary superblock at 0, Group descriptors at 1-1
Backup superblock at 32768, Group descriptors at 32769-32769
Backup superblock at 98304, Group descriptors at 98305-98305
Backup superblock at 163840, Group descriptors at 163841-163841
Backup superblock at 229376, Group descriptors at 229377-229377
Backup superblock at 294912, Group descriptors at 294913-294913
Backup superblock at 819200, Group descriptors at 819201-819201
Backup superblock at 884736, Group descriptors at 884737-884737
root@Microknoppix:/home/knoppix#
4 Replies
Replies have been turned off for this discussion
- Retired_MemberBump
Any recommendations for a Linux forum I could get help from? - siignaNETGEAR Employee RetiredLooks like you're indeed missing the superblock on that disk. I'll imagine it'll output about the same as your assemble command, but what do you get from 'mdadm -E /dev/sdc3' ?
You can force a recreation of the superblock, but I wouldn't do this unless you're absolutely sure of what you're doing. You'll need to get the array itself as well as the logical volume up before you can mount the filesystem.
You can mount /dev/md0 as a regular ext2/3 filesystem (because that's what it is) and you should be able to pull the RAID configuration logs out of /var/log/frontview. If you can post the latest "raid_config_*.log" that contains md2 that would be helpful. - Retired_MemberPlease ignore the mount device name. These were during different logins. sda, sdb, and sdc from the first post are all the first drive from the array.
mdadm -E output for all partitions:root@Microknoppix:/home/knoppix# mdadm -E /dev/sdb
/dev/sdb:
MBR Magic : aa55
Partition[0] : 3907029167 sectors at 1 (type ee)
root@Microknoppix:/home/knoppix# mdadm -E /dev/sdb3
mdadm: No md superblock detected on /dev/sdb3.
root@Microknoppix:/home/knoppix# mdadm -E /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 494a7e99:7972ebcc:9b4a1bd1:d55a1de3
Name : E091F58AD8E4:0
Creation Time : Thu Sep 8 16:33:41 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 8386560 (4.00 GiB 4.29 GB)
Array Size : 4193268 (4.00 GiB 4.29 GB)
Used Dev Size : 8386536 (4.00 GiB 4.29 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 57b9a1e6:9daba6b6:7246f828:f2af845a
Update Time : Tue Jul 2 01:31:50 2013
Checksum : 2bcb3495 - correct
Events : 476276
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing)
root@Microknoppix:/home/knoppix# mdadm -E /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 16b0093f:e9ce8e55:6f550c64:9f57fbf3
Name : E091F58AD8E4:1
Creation Time : Thu Sep 8 16:33:42 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1048552 (512.07 MiB 536.86 MB)
Array Size : 524276 (512.07 MiB 536.86 MB)
Data Offset : 24 sectors
Super Offset : 8 sectors
State : clean
Device UUID : cdbaf0c1:7d3f99a3:37786b19:3f1e936a
Update Time : Thu Jun 27 21:49:16 2013
Checksum : c59f7e50 - correct
Events : 255
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing)
root@Microknoppix:/home/knoppix#
Important:root@Microknoppix:/home/knoppix# mdadm -E /dev/sdb3
mdadm: No md superblock detected on /dev/sdb3.
gdisk output:root@ubuntu:/home/ubuntu# gdisk
GPT fdisk (gdisk) version 0.8.1
Type device filename, or press <Enter> to exit: /dev/sda
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): D2AD91F6-ED10-451B-8466-36F3A01BFE2D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 64-sector boundaries
Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
3 9437248 3907025072 1.8 TiB FD00
Command (? for help): i
Partition number (1-3): 1
Partition GUID code: A19D880F-05FC-4D3B-A006-743F0F84911E (Linux RAID)
Partition unique GUID: 29CFC302-D112-423D-BA26-B50B9F733F25
First sector: 64 (at 32.0 KiB)
Last sector: 8388671 (at 4.0 GiB)
Partition size: 8388608 sectors (4.0 GiB)
Attribute flags: 0000000000000000
Partition name: ''
Command (? for help): i
Partition number (1-3): 2
Partition GUID code: A19D880F-05FC-4D3B-A006-743F0F84911E (Linux RAID)
Partition unique GUID: B3B52523-2065-46AC-8D71-C802C2FBD618
First sector: 8388672 (at 4.0 GiB)
Last sector: 9437247 (at 4.5 GiB)
Partition size: 1048576 sectors (512.0 MiB)
Attribute flags: 0000000000000000
Partition name: ''
Command (? for help): i
Partition number (1-3): 3
Partition GUID code: A19D880F-05FC-4D3B-A006-743F0F84911E (Linux RAID)
Partition unique GUID: 08A311D3-C961-4449-9CB1-B0BD32D9B39D
First sector: 9437248 (at 4.5 GiB)
Last sector: 3907025072 (at 1.8 TiB)
Partition size: 3897587825 sectors (1.8 TiB)
Attribute flags: 0000000000000000
Partition name: ''
Ill get the logs when i can.
As far as I can tell, I had power loss during a resync of the drives, so now I have a bad sector and the second drive is stuck as a spare. - Retired_MemberLast good configuration:
***** RAID configuration log from 2013/05/26 *****
***** mdadm -D --scan -v *****
ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=E091F58AD8E4:0 UUID=494a7e99:7972ebcc:9b4a1bd1:d55a1de3
devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md/1 level=raid1 num-devices=2 metadata=1.2 name=E091F58AD8E4:1 UUID=16b0093f:e9ce8e55:6f550c64:9f57fbf3
devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md/2 level=raid5 num-devices=2 metadata=1.2 name=E091F58AD8E4:2 UUID=1c784278:8cb4a7bc:b66b10e9:3c012e64
devices=/dev/sda3,/dev/sdb3
***** mdadm -D --scan -vv *****
/dev/md/0:
Version : 1.2
Creation Time : Thu Sep 8 12:33:41 2011
Raid Level : raid1
Array Size : 4193268 (4.00 GiB 4.29 GB)
Used Dev Size : 4193268 (4.00 GiB 4.29 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun May 26 06:47:01 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : E091F58AD8E4:0
UUID : 494a7e99:7972ebcc:9b4a1bd1:d55a1de3
Events : 369632
Number Major Minor RaidDevice State
2 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
/dev/md/1:
Version : 1.2
Creation Time : Thu Sep 8 12:33:42 2011
Raid Level : raid1
Array Size : 524276 (512.07 MiB 536.86 MB)
Used Dev Size : 524276 (512.07 MiB 536.86 MB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun May 26 06:47:01 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : E091F58AD8E4:1
UUID : 16b0093f:e9ce8e55:6f550c64:9f57fbf3
Events : 213
Number Major Minor RaidDevice State
2 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
/dev/md/2:
Version : 1.2
Creation Time : Thu Sep 8 12:33:42 2011
Raid Level : raid5
Array Size : 1948792704 (1858.51 GiB 1995.56 GB)
Used Dev Size : 1948792704 (1858.51 GiB 1995.56 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun May 26 06:47:01 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : E091F58AD8E4:2
UUID : 1c784278:8cb4a7bc:b66b10e9:3c012e64
Events : 5399
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
***** mdconfig *****
Device : /dev/md0
Create Time : 1315499621
Update Time : 1369565221
RAID Level : 1
RAID Capacity : 4193268
Disk Size : 4193268
Chunk Size : 0
Disks : 2
RAID Disks : 2
Active Disks : 2
Working Disks : 2
Failed Disks : 0
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
1 /dev/sdb1 1 8/17 8388608 6 [ Active Sync ]
2 /dev/sda1 0 8/ 1 8388608 6 [ Active Sync ]
Device : /dev/md1
Create Time : 1315499622
Update Time : 1369565221
RAID Level : 1
RAID Capacity : 524276
Disk Size : 524276
Chunk Size : 0
Disks : 2
RAID Disks : 2
Active Disks : 2
Working Disks : 2
Failed Disks : 0
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
1 /dev/sdb2 1 8/18 1048576 6 [ Active Sync ]
2 /dev/sda2 0 8/ 2 1048576 6 [ Active Sync ]
Device : /dev/md2
Create Time : 1315499622
Update Time : 1369565221
RAID Level : 5
RAID Capacity : 1948792704
Disk Size : 1948792704
Chunk Size : 65536
Disks : 2
RAID Disks : 2
Active Disks : 2
Working Disks : 2
Failed Disks : 0
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
0 /dev/sda3 0 8/ 3 3897587825 6 [ Active Sync ]
1 /dev/sdb3 1 8/19 3897587825 6 [ Active Sync ]
After failure:***** RAID configuration log from 2013/06/02 *****
***** mdadm -D --scan -v *****
ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=E091F58AD8E4:0 UUID=494a7e99:7972ebcc:9b4a1bd1:d55a1de3
devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md/1 level=raid1 num-devices=2 metadata=1.2 name=E091F58AD8E4:1 UUID=16b0093f:e9ce8e55:6f550c64:9f57fbf3
devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md/2 level=raid5 num-devices=2 metadata=1.2 name=E091F58AD8E4:2 UUID=1c784278:8cb4a7bc:b66b10e9:3c012e64
devices=/dev/sda3,/dev/sdb3
***** mdadm -D --scan -vv *****
/dev/md/0:
Version : 1.2
Creation Time : Thu Sep 8 12:33:41 2011
Raid Level : raid1
Array Size : 4193268 (4.00 GiB 4.29 GB)
Used Dev Size : 4193268 (4.00 GiB 4.29 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Jun 2 06:47:01 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Name : E091F58AD8E4:0
UUID : 494a7e99:7972ebcc:9b4a1bd1:d55a1de3
Events : 369975
Number Major Minor RaidDevice State
2 8 1 0 active sync /dev/sda1
1 0 0 1 removed
1 8 17 - faulty spare /dev/sdb1
/dev/md/1:
Version : 1.2
Creation Time : Thu Sep 8 12:33:42 2011
Raid Level : raid1
Array Size : 524276 (512.07 MiB 536.86 MB)
Used Dev Size : 524276 (512.07 MiB 536.86 MB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Jun 2 06:47:02 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Name : E091F58AD8E4:1
UUID : 16b0093f:e9ce8e55:6f550c64:9f57fbf3
Events : 216
Number Major Minor RaidDevice State
2 8 2 0 active sync /dev/sda2
1 0 0 1 removed
1 8 18 - faulty spare /dev/sdb2
/dev/md/2:
Version : 1.2
Creation Time : Thu Sep 8 12:33:42 2011
Raid Level : raid5
Array Size : 1948792704 (1858.51 GiB 1995.56 GB)
Used Dev Size : 1948792704 (1858.51 GiB 1995.56 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Jun 2 06:47:02 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : E091F58AD8E4:2
UUID : 1c784278:8cb4a7bc:b66b10e9:3c012e64
Events : 5402
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 0 0 1 removed
1 8 19 - faulty spare /dev/sdb3
***** mdconfig *****
Device : /dev/md0
Create Time : 1315499621
Update Time : 1370170022
RAID Level : 1
RAID Capacity : 4193268
Disk Size : 4193268
Chunk Size : 0
Disks : 2
RAID Disks : 2
Active Disks : 1
Working Disks : 1
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
1 /dev/sdb1 -1 8/17 8388608 1 [ Faulty ]
2 /dev/sda1 0 8/ 1 8388608 6 [ Active Sync ]
Device : /dev/md1
Create Time : 1315499622
Update Time : 1370170022
RAID Level : 1
RAID Capacity : 524276
Disk Size : 524276
Chunk Size : 0
Disks : 2
RAID Disks : 2
Active Disks : 1
Working Disks : 1
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
1 /dev/sdb2 -1 8/18 1048576 1 [ Faulty ]
2 /dev/sda2 0 8/ 2 1048576 6 [ Active Sync ]
Device : /dev/md2
Create Time : 1315499622
Update Time : 1370170022
RAID Level : 5
RAID Capacity : 1948792704
Disk Size : 1948792704
Chunk Size : 65536
Disks : 2
RAID Disks : 2
Active Disks : 1
Working Disks : 1
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
0 /dev/sda3 0 8/ 3 3897587825 6 [ Active Sync ]
1 /dev/sdb3 -1 8/19 3897587825 1 [ Faulty ]
Im beginning to think the LVM is the problem not the superblock. How do you recover LVM partition data?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!