Hi
I am new 2 openmediavault.
I have a setup with 6 4tb discs.
last night one disc died.unplugged it and booted up.
now i cant view my array,
seems /dev/127/ cant mount
i have replaced the bad drive with a new one , but no change .
i was hoping for a rebuild option in gui
please help
how can i get hold of bootlog
Raid 6 failure in openmediavault, panic
-
- OMV 1.0
- Thomasraid6
-
-
I got your pics. Let fix this on the forum. What is the output of: fdisk -l
-
is there a way to run that command via the webgui or something
i run the omvbox on the same monitor as this pc
that makes it abit annoying to copy paste -
-
enable ssh in the web interface and login to the box using putty.
-
root@openmediavault:~# fdisk -l
Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sda: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000Disk /dev/sda doesn't contain a valid partition table
Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x9edd8974Device Boot Start End Blocks Id System
/dev/sdc1 2048 976752639 488375296 7 HPFS/NTFS/exFATDisk /dev/sdd: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sde: 4000.8 GB, 4000785948160 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814035055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000Disk /dev/sde doesn't contain a valid partition table
Disk /dev/sdf: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000Disk /dev/sdf doesn't contain a valid partition table
Disk /dev/sdg: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0007300eDevice Boot Start End Blocks Id System
/dev/sdg1 * 2048 7409663 3703808 83 Linux
/dev/sdg2 7411710 7835647 211969 5 Extended
/dev/sdg5 7411712 7835647 211968 82 Linux swap / Solaris -
Is there a way to get my data back?
-
-
Your data should not be gone. Just need to get the array started, sync'd, and mounted. It will take a while though.
mdadm --stop /dev/md127
mdadm --assemble /dev/md127 /dev/sd[abcdef] --verbose --forceYou can view the progress with: cat /proc/mdstat
-
root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdef] --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdc has no superblock - assembly aborted
root@openmediavault:~#the first command worked like a charm
not the second one tho -
mdadm: /dev/sdc has no superblock - assembly aborted
-
-
I assume sdc is the new drive?? If yes, then
mdadm --zero-superblock /dev/sdc
dd if=/dev/zero of=/dev/sdc bs=512 count=10000then this again
mdadm --assemble /dev/md127 /dev/sd[abcdef] --verbose --force
-
is there a way to double
check what serialnumber or disc is connected to what sda sdb sdc sdd sdf sde -
Yes, in the physical disks tab in the web interface. It shows the serial numbers.
-
-
root@openmediavault:~# mdadm --zero-superblock /dev/sdc
mdadm: Unrecognised md component device - /dev/sdc
root@openmediavault:~# -
here are my discs
https://www.dropbox.com/sc/gce…AAD-2qk2dbbqiTUMuJkljUsbasdc is the one with serial s300TQXJ
-
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdc has no superblock - assembly aborted
root@openmediavault:~# mdadm --zero-superblock /dev/sdc
mdadm: Unrecognised md component device - /dev/sdc
root@openmediavault:~# dd if=/dev/zero of=/dev/sdc bs=512 count=10000
10000+0 poster in
10000+0 poster ut
5120000 byte (5,1 MB) kopierade, 0,234325 s, 21,8 MB/s
root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdef] --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdc has no superblock - assembly aborted
root@openmediavault:~#what can i do
need to solve this
please.. -
-
What is the output of: cat /proc/mdstat
-
root@openmediavault:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
unused devices: <none>
root@openmediavault:~# -
i rebooted and got
root@openmediavault:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : inactive sda[0] sdf[5] sde[4] sdd[3] sdb[1]
19534436503 blocks super 1.2unused devices: <none>
root@openmediavault:~#so where is the new 4tb sdc [2] ... ??
ts listed in he physical discs tab ,via gui -
-
Try:
mdadm --manage /dev/md127 --add /dev/sdc
cat /proc/mdstat
-
root@openmediavault:~# mdadm --manage /dev/md127 --add /dev/sdc
mdadm: add new device failed for /dev/sdc as 6: Invalid argument
root@openmediavault:~#
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!