Network Space Max OpenShare Volumes lost

[pasqualeCatucci]

Hi,
first of all sorry for my english, i am using a translator. I need your help because few days ago, after a simple reboot of the NAS (Network Space Max 6TB), I no longer see the shared volumes OpneShare and the personal volume of Admin user MyShare. From dashboard I can see RAID 0 and also the space occupied. do you think of anything? Can I try to recover the files somehow? thank you very much for your help.

pasqualeC

[Jocko]

Hi

So you use your nwsp max with a raid0 (I assume 2x disk3TB) As raid0 does not have redundancy, if the nas fails to assemble the raid, then you lose your data without recovery solution.
I am afraid it is your case if it is a disk failure but it may be also a corrupted fs issue on your raid0. In the first case, AFAIK there is no way to restore a raid0 and on the 2d case, doubtless you will be able to repair the fs

With the fvdw-sl console you may deepen your issue.
So the first step is to install fvdw-sl console on your laptop, and try to get a telnet access by selecting the action "load a standalone kernel" (need to select the standalone kernel for kirkwood platform). As the OS is loaded only on the RAM, there is no risk to corrupt your disks

later I will give the commands to investigate the issue

Note: with a raid0, you always need to have a backup solution for your valuable data

See :
You have to run the action "Load standalone kernel" to get a telnet access on the nas. (https://plugout.net/viewtopic.php?f=7&t=3086)
Please to read this topic if you have some connect issues: https://plugout.net/viewtopic.php?f=7&t=2645

You need to read carefully these topics (all information is important and must be understood)

[pasqualeCatucci]

thanks Jocko for your help.
I'm waiting for command to investigate and to repair (I hope) the fs.

bye

[Jocko]

Ok Did you succeed to get the telnet access?

The first outpout is

Code: Select all

gdisk -l /dev/sda
gdisk -l /dev/sdb

[pasqualeCatucci]

yes, I did.
This is the output:

Code: Select all

root@fvdw-sta-kirkwood:/proc # [b]gdisk -l /dev/sda[/b]
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7178A1DC-2935-4E2E-9DBC-AF23FC425705
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 31410 sectors (15.3 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1         4036608         4038655   1024.0 KiB  0700  primary
   2         4048896      5860530447   2.7 TiB     0700  primary
   3         4040704         4042571   934.0 KiB   0700  primary
   4         4044800         4046848   1.0 MiB     0700  primary
   5            2048          514047   250.0 MiB   0700  primary
   6          530432          546497   7.8 MiB     0700  primary
   7          546816          578945   15.7 MiB    0700  primary
   8          579584         2266409   823.6 MiB   0700  primary
   9         2267136         4018221   855.0 MiB   0700  primary
  10         4020224         4036289   7.8 MiB     0700  primary


root@fvdw-sta-kirkwood:/proc # [b]gdisk -l /dev/sdb[/b]
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8DC5F2B0-B724-4479-9251-B759DB03E13F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 31410 sectors (15.3 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1         4036608         4038655   1024.0 KiB  0700  primary
   2         4048896      5860530447   2.7 TiB     0700  primary
   3         4040704         4042571   934.0 KiB   0700  primary
   4         4044800         4046848   1.0 MiB     0700  primary
   5            2048          514047   250.0 MiB   0700  primary
   6          530432          546497   7.8 MiB     0700  primary
   7          546816          578945   15.7 MiB    0700  primary
   8          579584         2266409   823.6 MiB   0700  primary
   9         2267136         4018221   855.0 MiB   0700  primary
  10         4020224         4036289   7.8 MiB     0700  primary

[Jocko]

As it is a raid0 we go to progress step by step carefully.

Now you need to upload the raid tools, so on the telnet run

Code: Select all

fvdw-sl-programs

and select the 4th item "Upload and extract glibc mini and tools"

if all is ok, please to post these output

Code: Select all

mdadm --examine /dev/sda2
mdadm --examine /dev/sdb2

Note: as it is a verbose output, please to use the bbcode 'code' to post them (much more readable!)

[pasqualeCatucci]

root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 53380253:93cda1b9:a5c89cea:2f9ecd2b
Name : NSMAXbyPorky:4
Creation Time : Sat Oct 18 08:00:32 2014
Raid Level : raid0
Raid Devices : 2

Avail Dev Size : 5856481536 (2792.59 GiB 2998.52 GB)
Super Offset : 5856481536 sectors
State : clean
Device UUID : a2ef1607:719b252c:a70daf94:a73e67fc

Update Time : Sat Oct 18 08:00:32 2014
Checksum : fe69d331 - correct
Events : 0

Chunk Size : 512K

Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)


root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 53380253:93cda1b9:a5c89cea:2f9ecd2b
Name : NSMAXbyPorky:4
Creation Time : Sat Oct 18 08:00:32 2014
Raid Level : raid0
Raid Devices : 2

Avail Dev Size : 5856481536 (2792.59 GiB 2998.52 GB)
Super Offset : 5856481536 sectors
State : clean
Device UUID : 6f83620c:1b785bb5:dcb0c55d:d249e0d6

Update Time : Sat Oct 18 08:00:32 2014
Checksum : 307af20a - correct
Events : 0

Chunk Size : 512K

Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing)

[Jocko]

I repeat what I post previously...

Note: as it is a verbose output, please to use the bbcode 'code' to post them (much more readable!)

It seems both disk are ok and you should be able to assemble it
we go first to assemble it with the read-only state:

Code: Select all

mdadm --assemble --readonly /dev/md4 /dev/sda2 /dev/sdb2

and post

Code: Select all

mdadm --detail /dev/md4

[pasqualeCatucci]

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --assemble --readonly /dev/md4 /dev/sda2 /dev/sdb2
mdadm:option --readonly not valid in assemble mode

[pasqualeCatucci]

i tryed removing the --readonly option and this is the result:

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --detail /dev/md4
/dev/md4:
        Version : 1.0
  Creation Time : Sat Oct 18 08:00:32 2014
     Raid Level : raid0
     Array Size : 5856481280 (5585.18 GiB 5997.04 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Sat Oct 18 08:00:32 2014
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 512K

           Name : NSMAXbyPorky:4
           UUID : 53380253:93cda1b9:a5c89cea:2f9ecd2b
         Events : 0

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2