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

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

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

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 

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

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 ?

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

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

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

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

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

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

[How could I start on GA-890GPA-UD3H mobo ?]

Thank you ! Olegin ! It worked ! You cannot imagine how may tries I did before .

[the struggle]

HAve you sorted ? I have the same issue.  No boot loader for this Athlon II ! 

[How could I start on GA-890GPA-UD3H mobo ?]

Thank you @Olegin for hint ! But I am not reaching that far !  I don't hit the moment to load the .pat file.

 

I have installed loader 1.02b on a usb stick and it does not boot from it. IT's blocked on "booting the kernel".

How should I investigate this  ?

 

I have even disabled on board Ethernet adaptor and I have added another one (Intel) on PCI  .

 

DAniel

[How could I start on GA-890GPA-UD3H mobo ?]

Hello All,

I am trying to start xpnology on a GA-890GPA-UD3H mobo V1.

This has an AMD Athlon II procesor.

I have tried  a LOT of loaders but all of them are stopping at "Booting the kernel" . What should I do ? 

Is there any error.log file that I could read to understand what's happening ? What should I try ?

 

Thank you

Daniel

[Is there any extra.lzma for v1.02b loader?]

Hello,

I have the same issue. I have a Gigabyte mother board with RTL8111 and I cannot boot. 

@Polanskiman - could you please upload again loader from post 

(does not exist anymore)

O can you please give a hint how I could add a reference on grub.cfg to a "ramdisk.lzma" that may contain my needed driver ?

 

Thank you

Daniel