You should be able to mount it, the 'play' icon is for mounting an existing filesystem
OK yes, I had panicked and couldn't remember how to mount it.
Problem: The drive letter used to be sdh now it is sdj.
So the status of md0 is "read-auto".
sdj seems not to be in the raid.
Two hours after my last message, since as I said the hard drives are new, I went to the machine and unplugged/replugged the connectors from the broken hd. The RAID is working again!
Now I would like to know how it is possible to constantly have problems with the connectors, I had already once lost everything because of them! I have changed them all and now I have the same problem.
RAID md0 is 'clean'. I do not see it in the file system (Status is "Missing"). What should I do now to fix it without damaging anything else?
You're running Raid0 there is no recovery unless you use recovery software or pay for professional recovery
OK, thank you. Fortunately I have backups of most of the files. I'm just missing the last few things I created, but whatever, I can redo them.
I wonder why I always have problems with hard drives. They are also new! I would like to investigate the reason for these crashes
Looks like you used raid 0 this is striped and parts of files might have end up on different drives in your array.
if the array fails you damage those files so chances are virtually 0 to recover your array.
I hope you have a backup.
Yes, I have a backup of almost everything, I am missing a few things, if they recover well, otherwise I may lose them.
But I would like to attempt recovery first before giving up
Hello everyone.
I have version 6.0.46-1 of OMV.
I have created two RAIDs, one is working, the other is in BROKEN state (md0).
The RAID information not working is this:
Version : 1.2
Creation Time : Sat Oct 29 14:06:23 2022
Raid Level : raid0
Array Size : 2929890816 (2794.16 GiB 3000.21 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sat Oct 29 14:06:23 2022
State : broken
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : -unknown-
Chunk Size : 512K
Consistency Policy : none
Name : nas:Anna (local to host nas)
UUID : 31167f13:46400c9b:eba60ea1:875f57a0
Events : 0
Number Major Minor RaidDevice State
0 8 32 0 active sync /dev/sdc
1 8 48 1 active sync /dev/sdd
2 8 112 2 active syncIs there a chance to restore it?
Thank You
root@nas:~# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sat Oct 29 14:06:23 2022
Raid Level : raid0
Array Size : 2929890816 (2794.16 GiB 3000.21 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sat Oct 29 14:06:23 2022
State : broken
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : -unknown-
Chunk Size : 512K
Consistency Policy : none
Name : nas:Anna (local to host nas)
UUID : 31167f13:46400c9b:eba60ea1:875f57a0
Events : 0
Number Major Minor RaidDevice State
0 8 32 0 active sync /dev/sdc
1 8 48 1 active sync /dev/sdd
2 8 112 2 active sync
root@nas:~# cat /proc/mdstat
Personalities : [raid0] [linear] [multipath] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid0 sdb[0] sdg[2] sde[1]
5860147200 blocks super 1.2 512k chunks
md0 : active raid0 sdh[2] sdc[0] sdd[1]
2929890816 blocks super 1.2 512k chunks
unused devices: <none>fdisk -l | grep "Disk "
Disk /dev/sdg: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20PURZ-85G
Disk /dev/sdf: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk model: TOSHIBA MK3276GS
Disk identifier: 0xe1a99502
Disk /dev/sde: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20PURZ-85A
Disk /dev/sdd: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10PURZ-85U
Disk /dev/sdc: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00W
Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20PURZ-85A
Disk /dev/sda: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAKX-0
Disk identifier: 5C6BFB13-D813-4980-B209-D1719FAD7F71
Disk /dev/md0: 2,73 TiB, 3000208195584 bytes, 5859781632 sectors
Disk /dev/md1: 5,46 TiB, 6000790732800 bytes, 11720294400 sectorsroot@nas:~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=nas:Anna UUID=31167f13:46400c9b:eba60ea1:875f57a0
ARRAY /dev/md1 metadata=1.2 name=nas:1 UUID=a3747a6f:6aea4af3:204d8c4f:c818a923root@nas:~# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid0 num-devices=3 metadata=1.2 name=nas:Anna UUID=31167f13:46400c9b:eba60ea1:875f57a0
devices=/dev/sdc,/dev/sdd
ARRAY /dev/md1 level=raid0 num-devices=3 metadata=1.2 name=nas:1 UUID=a3747a6f:6aea4af3:204d8c4f:c818a923
devices=/dev/sdb,/dev/sde,/dev/sdgYou'd need to answer a few questions:
1. How big is the data store.
2. If it's large is it mostly video?
Right now I have more than 2 tb of recovered data, mixed between videos and photos.
I produce an average of 4 gb of data per week, always mixed video and photos.
The total hard disk available to date is 10tb.
A 4tb usb hard disk for backup (Once I reach its limit I will continue the backup on another usb hd)
OK guys.
I saved what I could.
Now I have to redo everything. I reinstall OMV and connect the drives.
Given what has happened to me I ask for your advice:
is it more convenient to create a RAID 5 or merge all the hard drives and have a larger capacity available?
Hi guys.
Here I am again.
I have saved the remaining available data.
So at the moment those few remaining files are safe.
Now I would ask for one last help in trying to merge the whole array and retrieve other files as well.
If that doesn't work, patience. But at least we tried!
Here's what I consider to be the questions you must answer:
- Do you want to try to recover the array? If you attempt this and it goes wrong, that's it. There won't be anything nothing left to recover.
(OR)- Do you want to backup the data that remains in the RAID array?
The answer to the above is your call.
Hi.
Yes, my intention is to back up first. And recover what little is left, less than 50%.
After that one could try to recover the array?
As for the rsync command, I had already tried using it but it crashes when it finds an incomplete/damaged file.
I am using "MC" so that I can step in and skip the incomplete/damaged files.
It will take some time, always hoping that some other adverse event doesn't happen!
Another thing: all disks apart from the USB one and the OS one were part of the RAID before the disaster!
Thank you for your valuable help!
If you didn't add the external drive to the RAID array, it will be outside. Mount it
I have this situation:
In the 'Discs' section, I see that there is a \sda and \sdc:
In 'File System' it can be seen that this \sda is used for 111GB.
You can also see that it has an NTFS file system! How this is possible I do not know. I had formatted everything in ext4 when building the RAID, I'm sure! I can't figure it out!
\sdc is not present
In the RAID \sda is not present and I cannot get it to fit. If I click on Recover it makes me choose \sdc, which does not appear in any of the previous sections, but not \sda.
If I try to add \sdc to the RAID instead, I get this error
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mdadm --manage '/dev/md127' --add /dev/sdc 2>&1' with exit code '1': mdadm: Failed to write metadata to /dev/sdc
Errore #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mdadm --manage '/dev/md127' --add /dev/sdc 2>&1' with exit code '1': mdadm: Failed to write metadata to /dev/sdc in /usr/share/php/openmediavault/system/process.inc:195
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(419): OMV\System\Process->execute()
#1 [internal function]: Engined\Rpc\RaidMgmt->add(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('add', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('RaidMgmt', 'add', Array, Array, 1)
#5 {main}You could try connecting the "NTFS" formatted external drive to windows. If windows can't see the data....
No, I have now formatted the external drive in EXT4.
The only hope I have is in \sdc. It shows up in the drives but remains outside the RAID.
You were already able to patch it, maybe repeating the same operations will recover the files anyway.
Does Rsync also replicate data that I no longer see in theRaid?
I formatted the USB HD. I'm starting from scratch.
Problem: Many files are not present in the RAID!!!
I see that \sdc is out of the RAID, how can I proceed to try to get it back in?
I tried to do "Restore" but it gave me this error:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mdadm --manage '/dev/md127' --add /dev/sdc 2>&1' with exit code '1': mdadm: Failed to write metadata to /dev/sdc
Errore #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mdadm --manage '/dev/md127' --add /dev/sdc 2>&1' with exit code '1': mdadm: Failed to write metadata to /dev/sdc in /usr/share/php/openmediavault/system/process.inc:195
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(419): OMV\System\Process->execute()
#1 [internal function]: Engined\Rpc\RaidMgmt->add(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('add', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('RaidMgmt', 'add', Array, Array, 1)
#5 {main}
Even if you managed a recovery, could you "trust" the result?
You are right. The problem is that some hds in the RAID are failing and I should hurry up and back them up before they stop working.
But if you can actually lose data or get damaged, it would be better to start from the beginning.
More than attempting to retrieve it....
Worst case scenario, I will start the backup from the beginning again...3 more months of waiting!
Alles anzeigenIt shows it has a partition.
Output of sudo fdisk -l /dev/sde
sudo blkid | grep sde
Also cat /etc/fstab
sudo fdisk -l /dev/sde
Ignoring extra data in partition table 5.
Ignoring extra data in partition table 5.
Ignoring extra data in partition table 5.
Invalid flag 0xd7f0 of EBR (for partition 5) will be corrected by w(rite).
Disk /dev/sde: 3,7 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: Elements 25A1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sde1 4294967295 4820883454 525916160 250,8G f W95 Ext'd (LBA)
/dev/sde5 4831721256 7829571976 2997850721 1,4T 43 unknown
Partition 1 does not start on physical sector boundary.root@NAS:~# sudo blkid | grep sde
root@NAS:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb1 during installation
UUID=da7dd745-e1c0-4f19-88ae-c9a28230b666 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=f62a962f-6e9b-4011-9118-2287143468b0 none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/3c50a097-b1fe-4c69-93ae-7ee87c64838b /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae-7ee87c64838b ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/34361084361048EE /srv/dev-disk-by-uuid-34361084361048EE ntfs defaults,nofail,big_writes 0 2
# <<< [openmediavault]Did you reboot or why did the disk name change from /dev/sdg to /dev/sde?
Yes, the guide said to reboot and so I did.
Alles anzeigenOr you can try this
https://www.cgsecurity.org/wiki/TestDisk
e.g.
https://www.simplified.guide/l…k-recover-partition-table
you can go directly to step 7 to install testdisk
I followed the guide to the end but I still don't see the hd in File System
It seems that the disk is sde
root@NAS:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,8T 0 disk
├─sda1 8:1 0 16M 0 part
└─sda2 8:2 0 1,8T 0 part /srv/dev-disk-by-uuid-34361084361048EE
sdb 8:16 0 298,1G 0 disk
├─sdb1 8:17 0 297,1G 0 part /
├─sdb2 8:18 0 1K 0 part
└─sdb5 8:21 0 976M 0 part [SWAP]
sdc 8:32 0 1,8T 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
sdd 8:48 0 931,5G 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
sde 8:64 0 3,7T 0 disk
└─sde1 8:65 0 1K 0 part
sdg 8:96 0 931,5G 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
sdh 8:112 0 465,8G 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
sdi 8:128 0 931,5G 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
sdj 8:144 0 931,5G 0 disk
└─md127 9:127 0 2,3T 0 raid5 /srv/dev-disk-by-uuid-3c50a097-b1fe-4c69-93ae
Did you by chance wipe the disk while installing or delete the partition table?
No, I did nothing. I was careful which disk I chose for the installation
I have installed it and is now searching...it will take a while I think, it is a 4 tb
