Raid1 is missing

manne_sahne · Jan 11th 2023

That's disappointing...

Code

root@openmediavault:~# e2fsck -b 32768 /dev/sda                                                                                                                                                                    
e2fsck 1.44.5 (15-Dec-2018)                                                                                                                                                                                        
/dev/sda is in use.                                                                                                                                                                                                
e2fsck: Cannot continue, aborting.

and ....

Code

root@openmediavault:~# sudo umount --force /dev/sda                                                                                                                                                                
umount: /dev/sda: not mounted

Any clue, how this can be?

geaves · Jan 11th 2023

Ok, you've run fsck on the array /dev/md0 and it's come back with a possible solution from your post 19, run the solution on /dev/md0 not on individual drives

I also think the problem is me understanding what you are asking as this line -> Should I do the e2fsck -b 32768 with the drives you're asking should this be run on the drives, I should have answered no, it needs to be run on the array (/dev/md0)

manne_sahne · Jan 11th 2023

That's a kind of a hen/egg problem.

Code

root@openmediavault:~# e2fsck -b 32768 /dev/md0                                                                                                                                                                    
e2fsck 1.44.5 (15-Dec-2018)                                                                                                                                                                                        
e2fsck: Invalid argument while trying to open /dev/md0                                                                                                                                                             
                                                                                                                                                                                                                   
The superblock could not be read or does not describe a valid ext2/ext3/ext4                                                                                                                                       
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4                                                                                                                                       
filesystem (and not swap or ufs or something else), then the superblock                                                                                                                                            
is corrupt, and you might try running e2fsck with an alternate superblock:                                                                                                                                         
    e2fsck -b 8193 <device>                                                                                                                                                                                        
 or                                                                                                                                                                                                                
    e2fsck -b 32768 <device>

Display More

By searching around, I also noticed is that the folder by-label doesn't exist.

Code

root@openmediavault:~# dir /dev/disk                                                                                                                                                                               
by-id  by-partuuid  by-path  by-uuid

geaves · Jan 11th 2023

Ok you've tried 32768, have you tried the other one?

Quote from manne_sahne

By searching around, I also noticed is that the folder by-label doesn't exist

?? what folder, if you are referring to the mountpoint that's under /srv

manne_sahne · Jan 11th 2023

Yes, I've tried the other one as well. The result is the same.

The mountpoint is okay then.

Code

root@openmediavault:~# dir /srv                                                                                                                                                                                    
dev-disk-by-label-Raid1  ftp

But that's also useless..

Code

root@openmediavault:~# e2fsck -b 32768 /srv/dev-disk-by-label-Raid1                                                                                                                                                
e2fsck 1.44.5 (15-Dec-2018)                                                                                                                                                                                        
e2fsck: Is a directory while trying to open /srv/dev-disk-by-label-Raid1                                                                                                                                           
                                                                                                                                                                                                                   
The superblock could not be read or does not describe a valid ext2/ext3/ext4                                                                                                                                       
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4                                                                                                                                       
filesystem (and not swap or ufs or something else), then the superblock                                                                                                                                            
is corrupt, and you might try running e2fsck with an alternate superblock:                                                                                                                                         
    e2fsck -b 8193 <device>                                                                                                                                                                                        
 or                                                                                                                                                                                                                
    e2fsck -b 32768 <device>

Display More

geaves · Jan 11th 2023

Quote from manne_sahne

Yes, I've tried the other one as well. The result is the same

Then you're confirming what is already known

Quote from manne_sahne

The mountpoint is okay then

No, didn't say, I just pointed out to you that is where the mount point is after you did dir /dev/disk for whatever reason

Why run e2fsck on the mount point, that can only be run on a device.

There is nothing else to do, other than to try testdisk on each drive and see if there is any data that is recoverable, but I doubt it!!

Raid1 is missing

Participate now!

Similar Threads

RAID missing

Missing Raid

[SOLVED] RAID5 is not recognised anymore after reboot

Raid 5 lässt sich nicht wieder herstellen nach Reboot

btrfs scrub status /dev/md0 csum=2942 uncorrectable errors: 2942

Tags