Jump to content
XPEnology Community

Raid0 volume crashed


ultimateon

Recommended Posts

So my raid 0 volume just crashed

isrejf.png

And every damm time I look this up it says contact synology support.

The disks seem fine, I only booted down and downgraded my install because some asshole tried to login to my acount several times and locked me out of the system.

Question is how do I acess the data in the raid array

Using an HP Proliant Microserve NL54.

 

All drives seem fine smart tests bring up nothing

Link to comment
Share on other sites

Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't.

 

edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.

Link to comment
Share on other sites

Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't.

 

edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.

 

Ill try it it tomorow.

Also I'm terrible at terminal where is the array usually mounted to so I can check?

Link to comment
Share on other sites

Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't.

 

edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.

 

Ill try it it tomorow.

Also I'm terrible at terminal where is the array usually mounted to so I can check?

DiskStation> cd /
DiskStation> pwd
/
DiskStation> ls -l
drwxr-xr-x    2 root     root          4096 Mar  1 18:55 bin
drwxr-xr-x   10 root     root         53248 Dec 30 17:36 dev
drwxr-xr-x   35 root     root          4096 May 25 04:05 etc
drwxr-xr-x   32 root     root          4096 Dec 30 17:36 etc.defaults
drwxr-xr-x    2 root     root          4096 May 30  2014 initrd
drwxr-xr-x   23 root     root         20480 May 22 14:51 lib
drwxr-xr-x    2 root     root          4096 Jun 11  2014 lib64
drwx------    2 root     root          4096 May 30  2014 lost+found
drwxr-xr-x    2 root     root          4096 May 30  2014 mnt
dr-xr-xr-x  153 root     root             0 Dec 30 17:36 proc
drwxr-xr-x    7 root     root          4096 Mar 28 09:16 root
drwxr-xr-x    7 root     root           180 May  5 07:29 run
drwxr-xr-x    2 root     root          4096 Sep  9  2014 sbin
drwxr-xr-x   12 root     root             0 Dec 30 17:36 sys
drwxrwxrwt   16 root     root          2020 May 25 20:11 tmp
drwxr-xr-x    8 root     root          4096 Jun 11  2014 usr
drwxr-xr-x   16 root     root          4096 Mar  1 18:55 var
drwxr-xr-x   11 root     root          4096 Jun 11  2014 var.defaults
drwxr-xr-x   20 root     root          4096 May  5 07:26 volume1
drwxr-xr-x    5 root     root          4096 Feb 26 12:32 volumeSATA1
DiskStation> cd /volume1/
DiskStation> ls -l
drwxrwxrwx   15 root     root          4096 May 22 14:51 @appstore
drwx------    2 root     root          4096 May  5 07:29 @autoupdate
drwxr-xr-x    5 admin    users         4096 Mar  1 18:42 @database
drwxr-xr-x    9 admin    users         4096 Mar 27 07:34 @download
drwx------    2 root     root          4096 Jun  5  2014 @iSCSITrg
drwxr-xr-x    2 root     root          4096 Sep 30  2014 @smallupd@te_deb
drwxrwxrwx    4 root     root          4096 May  5 07:29 @spool
drwxrwxrwt   39 root     root          4096 May 25 04:00 @tmp
drwx------    5 admin    users         4096 Jun  5  2014 Plex
...
DiskStation>

/volume1/ is where your array data should be.

Link to comment
Share on other sites

Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't.

 

edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.

 

Ill try it it tomorow.

Also I'm terrible at terminal where is the array usually mounted to so I can check?

DiskStation> cd /
DiskStation> pwd
/
DiskStation> ls -l
drwxr-xr-x    2 root     root          4096 Mar  1 18:55 bin
drwxr-xr-x   10 root     root         53248 Dec 30 17:36 dev
drwxr-xr-x   35 root     root          4096 May 25 04:05 etc
drwxr-xr-x   32 root     root          4096 Dec 30 17:36 etc.defaults
drwxr-xr-x    2 root     root          4096 May 30  2014 initrd
drwxr-xr-x   23 root     root         20480 May 22 14:51 lib
drwxr-xr-x    2 root     root          4096 Jun 11  2014 lib64
drwx------    2 root     root          4096 May 30  2014 lost+found
drwxr-xr-x    2 root     root          4096 May 30  2014 mnt
dr-xr-xr-x  153 root     root             0 Dec 30 17:36 proc
drwxr-xr-x    7 root     root          4096 Mar 28 09:16 root
drwxr-xr-x    7 root     root           180 May  5 07:29 run
drwxr-xr-x    2 root     root          4096 Sep  9  2014 sbin
drwxr-xr-x   12 root     root             0 Dec 30 17:36 sys
drwxrwxrwt   16 root     root          2020 May 25 20:11 tmp
drwxr-xr-x    8 root     root          4096 Jun 11  2014 usr
drwxr-xr-x   16 root     root          4096 Mar  1 18:55 var
drwxr-xr-x   11 root     root          4096 Jun 11  2014 var.defaults
drwxr-xr-x   20 root     root          4096 May  5 07:26 volume1
drwxr-xr-x    5 root     root          4096 Feb 26 12:32 volumeSATA1
DiskStation> cd /volume1/
DiskStation> ls -l
drwxrwxrwx   15 root     root          4096 May 22 14:51 @appstore
drwx------    2 root     root          4096 May  5 07:29 @autoupdate
drwxr-xr-x    5 admin    users         4096 Mar  1 18:42 @database
drwxr-xr-x    9 admin    users         4096 Mar 27 07:34 @download
drwx------    2 root     root          4096 Jun  5  2014 @iSCSITrg
drwxr-xr-x    2 root     root          4096 Sep 30  2014 @smallupd@te_deb
drwxrwxrwx    4 root     root          4096 May  5 07:29 @spool
drwxrwxrwt   39 root     root          4096 May 25 04:00 @tmp
drwx------    5 admin    users         4096 Jun  5  2014 Plex
...
DiskStation>

/volume1/ is where your array data should be.

Since the GUI will be a no go and I'm currently in windows how will I remove the data.

Also if I use a bootable Linux like Ubuntu or antergos how hard would it be to mount the partitions? ( would be easier for me to move the files because GUI)

I'm only going to move 20 gigs of files give or take.

Link to comment
Share on other sites

Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't.

 

edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.

 

Ill try it it tomorow.

Also I'm terrible at terminal where is the array usually mounted to so I can check?

DiskStation> cd /
DiskStation> pwd
/
DiskStation> ls -l
drwxr-xr-x    2 root     root          4096 Mar  1 18:55 bin
drwxr-xr-x   10 root     root         53248 Dec 30 17:36 dev
drwxr-xr-x   35 root     root          4096 May 25 04:05 etc
drwxr-xr-x   32 root     root          4096 Dec 30 17:36 etc.defaults
drwxr-xr-x    2 root     root          4096 May 30  2014 initrd
drwxr-xr-x   23 root     root         20480 May 22 14:51 lib
drwxr-xr-x    2 root     root          4096 Jun 11  2014 lib64
drwx------    2 root     root          4096 May 30  2014 lost+found
drwxr-xr-x    2 root     root          4096 May 30  2014 mnt
dr-xr-xr-x  153 root     root             0 Dec 30 17:36 proc
drwxr-xr-x    7 root     root          4096 Mar 28 09:16 root
drwxr-xr-x    7 root     root           180 May  5 07:29 run
drwxr-xr-x    2 root     root          4096 Sep  9  2014 sbin
drwxr-xr-x   12 root     root             0 Dec 30 17:36 sys
drwxrwxrwt   16 root     root          2020 May 25 20:11 tmp
drwxr-xr-x    8 root     root          4096 Jun 11  2014 usr
drwxr-xr-x   16 root     root          4096 Mar  1 18:55 var
drwxr-xr-x   11 root     root          4096 Jun 11  2014 var.defaults
drwxr-xr-x   20 root     root          4096 May  5 07:26 volume1
drwxr-xr-x    5 root     root          4096 Feb 26 12:32 volumeSATA1
DiskStation> cd /volume1/
DiskStation> ls -l
drwxrwxrwx   15 root     root          4096 May 22 14:51 @appstore
drwx------    2 root     root          4096 May  5 07:29 @autoupdate
drwxr-xr-x    5 admin    users         4096 Mar  1 18:42 @database
drwxr-xr-x    9 admin    users         4096 Mar 27 07:34 @download
drwx------    2 root     root          4096 Jun  5  2014 @iSCSITrg
drwxr-xr-x    2 root     root          4096 Sep 30  2014 @smallupd@te_deb
drwxrwxrwx    4 root     root          4096 May  5 07:29 @spool
drwxrwxrwt   39 root     root          4096 May 25 04:00 @tmp
drwx------    5 admin    users         4096 Jun  5  2014 Plex
...
DiskStation>

/volume1/ is where your array data should be.

Since the GUI will be a no go and I'm currently in windows how will I remove the data.

Also if I use a bootable Linux like Ubuntu or antergos how hard would it be to mount the partitions? ( would be easier for me to move the files because GUI)

I'm only going to move 20 gigs of files give or take.

Link to comment
Share on other sites

go download winscp.

initiate a connection to your synology box.

You can use root as user, password is equal to your "admin" user under synology.

 

Choose SCP protocol and you should be able to read the above structure. go /volume1 or 2 or 3 depends on your synology. Get your MOST important files first then others.

 

The program works just like FTP.

Link to comment
Share on other sites

go download winscp.

initiate a connection to your synology box.

You can use root as user, password is equal to your "admin" user under synology.

 

Choose SCP protocol and you should be able to read the above structure. go /volume1 or 2 or 3 depends on your synology. Get your MOST important files first then others.

 

The program works just like FTP.

winscp diden't show the directory mounted, had to telnet or just plug a screen the nl54.

yotubq.png

 

I cd'ed into /volume 1 only to do ls and find nothing, anyone got any briliant Ideas before I tell somone i just lost half a ton of spreadsheets ( wasn't my fault i'm not particularly mad since my files weren't there at the time and somone else decided moving servers around was a "no problem" situation but yeah.)

Link to comment
Share on other sites

When you did the downgrade how did you do it?

Is it possible the volume just didn't migrate properly?

Also did you re-upgrade back to your original version after?

 

Basicly I installed the 5.2 version by acident , and downgraded to the 5.1 update 4.

But considering i-m now in linux and mounting the volume :-|

 

 

this is what i'm currently getting when mounting the volume and I am at a loss.

sxkkua.png

Link to comment
Share on other sites

anyone?

 

My suggestion to you is do lots of searching and reading about data recovery. You could try here http://forum.cgsecurity.org/phpBB3/ these guys are experts in data recovery and may be able to help you. Be prepared to spend lots of time. I lost an array once, and it took me about 6 months before I was able to recover my data... someone from the testdisk forums helped me a lot, and the rest took persistence and luck.

 

I documented my experience here http://forum.cgsecurity.org/phpBB3/foun ... t2600.html Good luck :!:

Link to comment
Share on other sites

Hi,

 

This is all the knowledge I have, try these steps. Unfortunately if this does not work, there's nothing I can help you with.

Make sure you have mdadm and lvm2 packages installed in your Ubuntu Linux.

For my test, I did an installation of Ubuntu and made sure NOT to use Logical Volume Management so that I was sure that my tests only show results of the synology volume. Don't know how bootable USBs show up, but I guess that will not be an issue.

 

FIRST OF: become and stay(!) root by typing "sudo su -" (don't forget that last minus-sign) and create a mount point you can use by creating a directory:

mkdir /mnt/syno

 

mdadm --detail --scan

Try this, see if your RAID details are visible

 

fdisk -l

Check if you see a mdxxx device. In my test, I saw a /dev/md127. Try to mount it, create a mount point somewhere (remember that mkdir /mnt/syno???) and try to mount: "mount /dev/mdxxx /mnt/syno".

But probably you will get an error (unknown filesystem type 'LVM2_member')

 

lvmdiskscan

This will output all kinds of info. You are hoping to see something like /dev/vg1000/lv and-or /dev/mdxxx and "1 LVM physical volume"

 

lvdisplay

You should see something like "LV Path /dev/vg1000/lv".

 

vgdisplay

Should display the volume name

 

lvscan

Should return the volume of your synology. When you see "Active", you are as good as set. If you see your volume, but "INACTIVE",

try "modprobe dm-mod" followed by "vgchange -ay" and run lvscan again.

 

If it's ACTIVE (for example, you see the output "ACTIVE '/dev/vg1000/lv' [xxxx GiB] inherit" you should be able to mount it with

mount /dev/vg1000/lv /mnt/syno

 

That's all the info I can give you. I wish you all the luck!

Link to comment
Share on other sites

Hi,

 

This is all the knowledge I have, try these steps. Unfortunately if this does not work, there's nothing I can help you with.

Make sure you have mdadm and lvm2 packages installed in your Ubuntu Linux.

For my test, I did an installation of Ubuntu and made sure NOT to use Logical Volume Management so that I was sure that my tests only show results of the synology volume. Don't know how bootable USBs show up, but I guess that will not be an issue.

 

FIRST OF: become and stay(!) root by typing "sudo su -" (don't forget that last minus-sign) and create a mount point you can use by creating a directory:

mkdir /mnt/syno

 

mdadm --detail --scan

Try this, see if your RAID details are visible

 

fdisk -l

Check if you see a mdxxx device. In my test, I saw a /dev/md127. Try to mount it, create a mount point somewhere (remember that mkdir /mnt/syno???) and try to mount: "mount /dev/mdxxx /mnt/syno".

But probably you will get an error (unknown filesystem type 'LVM2_member')

 

lvmdiskscan

This will output all kinds of info. You are hoping to see something like /dev/vg1000/lv and-or /dev/mdxxx and "1 LVM physical volume"

 

lvdisplay

You should see something like "LV Path /dev/vg1000/lv".

 

vgdisplay

Should display the volume name

 

lvscan

Should return the volume of your synology. When you see "Active", you are as good as set. If you see your volume, but "INACTIVE",

try "modprobe dm-mod" followed by "vgchange -ay" and run lvscan again.

 

If it's ACTIVE (for example, you see the output "ACTIVE '/dev/vg1000/lv' [xxxx GiB] inherit" you should be able to mount it with

mount /dev/vg1000/lv /mnt/syno

 

That's all the info I can give you. I wish you all the luck!

Amazing post. So good I have saved it should I have any issues. Thanks. N

Link to comment
Share on other sites

Hi,

 

This is all the knowledge I have, try these steps. Unfortunately if this does not work, there's nothing I can help you with.

Make sure you have mdadm and lvm2 packages installed in your Ubuntu Linux.

For my test, I did an installation of Ubuntu and made sure NOT to use Logical Volume Management so that I was sure that my tests only show results of the synology volume. Don't know how bootable USBs show up, but I guess that will not be an issue.

 

FIRST OF: become and stay(!) root by typing "sudo su -" (don't forget that last minus-sign) and create a mount point you can use by creating a directory:

mkdir /mnt/syno

 

mdadm --detail --scan

Try this, see if your RAID details are visible

 

fdisk -l

Check if you see a mdxxx device. In my test, I saw a /dev/md127. Try to mount it, create a mount point somewhere (remember that mkdir /mnt/syno???) and try to mount: "mount /dev/mdxxx /mnt/syno".

But probably you will get an error (unknown filesystem type 'LVM2_member')

 

lvmdiskscan

This will output all kinds of info. You are hoping to see something like /dev/vg1000/lv and-or /dev/mdxxx and "1 LVM physical volume"

 

lvdisplay

You should see something like "LV Path /dev/vg1000/lv".

 

vgdisplay

Should display the volume name

 

lvscan

Should return the volume of your synology. When you see "Active", you are as good as set. If you see your volume, but "INACTIVE",

try "modprobe dm-mod" followed by "vgchange -ay" and run lvscan again.

 

If it's ACTIVE (for example, you see the output "ACTIVE '/dev/vg1000/lv' [xxxx GiB] inherit" you should be able to mount it with

mount /dev/vg1000/lv /mnt/syno

 

That's all the info I can give you. I wish you all the luck!

 

anyone?

 

My suggestion to you is do lots of searching and reading about data recovery. You could try here http://forum.cgsecurity.org/phpBB3/ these guys are experts in data recovery and may be able to help you. Be prepared to spend lots of time. I lost an array once, and it took me about 6 months before I was able to recover my data... someone from the testdisk forums helped me a lot, and the rest took persistence and luck.

 

I documented my experience here http://forum.cgsecurity.org/phpBB3/foun ... t2600.html Good luck :!:

 

Thanks Ill read both of these in detail and will post back with results soon.

Link to comment
Share on other sites

×
×
  • Create New...