Help on : Abnormality detected on dsm. All volumes have been unmounted.

[dandumit]

Hello,

I have this nasty situation "Abnormality detected on dsm. All volumes have been unmounted."

 

Where 2 power outages yesterday and after this I have this message. 

Was that synology proprietary raid. from 3 disks I see now only 2 and there is no volume on it .

 

How could I fix this  ? Should I newer DSM boot loader ? Would it help  ?

Those disks can be read on other system  ? will I be able to recover data from disks ?

 

Thank you,

Daniel

Edited January 23, 2021 by dandumit

[IG-88]

3 hours ago, dandumit said:

How could I fix this  ? Should I newer DSM boot loader ? Would it help  ?

no, dont  cchange anything until you know about the reason

dont do any repairs, 1st step is to collect information and get a picture of the problem

and you should be tripple carefull if you dont have a backup and need that data

 

3 hours ago, dandumit said:

Those disks can be read on other system  ?

 

yes, synology usese mdadm and lvm2 for its software raid, both standard linux software

 

3 hours ago, dandumit said:

will I be able to recover data from disks ?

depends on the problem, 1st step is still gather some information about the state

how did you confugure your disk array, any non redundant volumes like raid0, basic or jbod?

 

 

Edited January 23, 2021 by IG-88

[dandumit]

Thank you @IG-88 for your answer ! 

Another fact it's that I had 3 disks on that proprietary Synology raid that allows to mix different kind of HDD sizes.

 

One disk had some bad sectors and was present with yellow on disk manager.

Now in disk manager I see only 2 HDD with green. 

 

Probably this is the reason. How I could overpass this ? 

I saw a tutorial here :

 

http://www.vsam.pro/crashed-synology-volume-and-how-to-restore-ds415-play/

 

Should I try this procedure ?

Thank you,

DAniel

[IG-88]

1 hour ago, dandumit said:

Now in disk manager I see only 2 HDD with green.

there mus be more to it as if you had a shr1 it would mean you have one disk redundancy and if one disks fails the volume should still be available to access the data - but its not in your case, so there seems to be more damage then just a failed disk and as long as its not analyzed you would not take any action

@flyride is the expert here, only if he's not available i might help out, i'm not as good and experienced in this

[dandumit]

Thank you @IG-88 !

I have followed above mentioned article and I have ended like this :

 

root@dsm01:/# cat /etc/fstab
none /proc proc defaults 0 0
/dev/root / ext4 defaults 1 1
root@dsm01:/# fsck.ext4 /dev/vg1/volume_1
e2fsck 1.42.6 (21-Sep-2012)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/vg1/volume_1
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

 

 but it looks a bit wrong to me because I have asked ext4 and it describes that it's not ext2

 

Daniel

[dandumit]

updates : I have tried :

 

root@dsm01:/# btrfs check /dev/vg1/volume_1
Syno caseless feature on.
Checking filesystem on /dev/vg1/volume_1
UUID: 8c4b4944-3bed-406d-bb02-3d9d5b88890e
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 293876084736 bytes used err is 0
total csum bytes: 75083076
total tree bytes: 2428157952
total fs tree bytes: 2239168512
total extent tree bytes: 99090432
btree space waste bytes: 385104498
file data blocks allocated: 513211695104
 referenced 295111467008

and then :....
 
mount /dev/vg1/volume_1 /volume1

 

after this I was able to see at command prompt folder structures .

I was hoping that everything will be normal and I have tried one reboot.

 

Unfortunately after reboot same situation : 

 

Abnormality detected on dsm01. All volumes have been unmounted.

 

what should I do more ?

[flyride]

3 hours ago, dandumit said:

 

Abnormality detected on dsm01. All volumes have been unmounted.

 

I was under the impression that this message was part of Synology's hardware validation feature and if it failed (meaning that the loader hack did not work), this message was the result.  I don't believe that it means there is a data integrity problem.  However, I would start with looking at your arrays and see if they are damaged, then start documenting the system.  OP seems to be wandering around with online tutorials (already tried a filesystem check for ext4 and btrfs, there is only one or the other) and that will only result in damage.

 

If arrays look intact, I'd consider regenerating a loader and doing a migration install and see if that fixes the issue.

[IG-88]

its not a mismatch of usb vid/pid, that just throws a mount failed on the serial console and dsm does not start at all

i guess taking a new usb and redoing the loader from scratch cant do anything wrong

if dsm does not start it can be checked in network (ip address), as the loader comes with 6.2.0 and there is a newer kernel (dsm system) on the disk it should offer recovery/repair and doing so will copy the newer kernel back to the loader (only takes less then a minute) and it should do a reboot, after that dsm should start again

(if a extended extra.lzma was used it should also be copied to the new usb - and no files should be used from the old loader)

 

Edited January 23, 2021 by IG-88

[dandumit]

Hello,

 

For someone that ever hit this situation :

I have been able to read disks using this article :

https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC

 

I have rewrote the usb stick with same image as initial ! because board it's old, cpu it's amd athlon and nic chip it's realtek, I needed to use a special lzma...

 

After doing this, tries to recover and blocks. Dead end...

 

I think that those disks are irecoverable. USed to be a SHR composed of 3 HDD's. IT seems that only one it's valid now. One has a lot of alarms on SMART and the third cannot be seen even at boot time.

 

Thank you for helping me !

Daniel 

[IG-88]

On 1/23/2021 at 1:34 PM, dandumit said:

updates : I have tried :

 

root@dsm01:/# btrfs check /dev/vg1/volume_1
Syno caseless feature on.
Checking filesystem on /dev/vg1/volume_1
UUID: 8c4b4944-3bed-406d-bb02-3d9d5b88890e
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 293876084736 bytes used err is 0
total csum bytes: 75083076
total tree bytes: 2428157952
total fs tree bytes: 2239168512
total extent tree bytes: 99090432
btree space waste bytes: 385104498
file data blocks allocated: 513211695104
 referenced 295111467008

and then :....
 
mount /dev/vg1/volume_1 /volume1

 

after this I was able to see at command prompt folder structures .

 

i'm  puzzled how you came from a clean btrfs file system you could mount (and presumably read) to

 

2 hours ago, dandumit said:

I think that those disks are irecoverable.

 

you would have been able to copy your data to a backup location after mounting volume1, you still had two valid disks and thats all you need if you have a one disk redundancy like shr1

 

 

[dandumit]

thank you @IG-88 for support. 

same thing it's not understandable to me too.  On that Ubuntu I have been able to read content from disks.

 

But when trying to start again with reinstall - > recover all system blocks and I am not able to go further. 

I am so desperate and clueless that I am considering to buy an original synology HW.

 

thank you

Daniel

[IG-88]

On 1/27/2021 at 6:23 AM, dandumit said:

On that Ubuntu I have been able to read content from disks.

ahh, ok thats good to hear

 

On 1/27/2021 at 6:23 AM, dandumit said:

But when trying to start again with reinstall - > recover all system blocks and I am not able to go further. 

i'd suggest checking the disks with a tool from the manufacturer and removing every partition so you will have a complete fresh install and volumes

if you use loader 1.02b and dsm 6.1 you dont have to bother about uefi/csm

if the hardware is at least 4th gen intel (haswell) you could use 1.04b 918+ with 6.2.3

(there are no information about the hardware you use)

 

On 1/27/2021 at 6:23 AM, dandumit said:

that I am considering to buy an original synology HW.

the normal affordable home units are a little under powered and can't be much extended beside too expansive external synology disk enclusures (no pcie slots)

but the hardware is reliable, if you have a more basic nas in mind without VM's or docker its not a bad choice

Qnap does more or less have the same but some better extendability like pcie slots (for 10g nic and nvme) in smaller units, nvme as data volume (synology only supports that as cache)

Edited January 28, 2021 by IG-88