I LOST MY NAS!!! and all of it's data... Oh well

[raidsm]

Hi there,

Yesterday I got a brand new SSD. So I installed it inside my NS2 just to do some testing and I was thinking that after my test , I just had to reinstall my old hard drive that was previously installed in it. All of my stuff are in this drive after all...

When I started my NS2 , it took far longer to boot , it finally came alive BUT it don't show any of the shares/partition that where on this drive. Did I just lost all of my data? That is not that bad as I have a backup but I have 2 questions

1- Did I make a mistake to install for testing purposes another drive with the idea of put back the old drive after my tests?
2-Is there an relatively easy way to recover my drive?

I don't know if it's there something written inside the PCB part of the NAS as it seems it don't recognize my old hard drive previously install prior testing a SSD...

well lesson learned I guess!

[Jocko]

don't know if it's there something written inside the PCB part of the NAS as it seems it don't recognize my old hard drive previously install prior testing a SSD...

No
NAS database is stored on the disk.

So I assume sda8 is not mounted.

Can you post these outputs

Code: Select all

cat /proc/partitions
fdisk -l /dev/sda
mount

[fvdw]

Strange, swapping disk should not be a problem as long as you do it when it is powered off ;)
But there is a risk that you have damaged the main board if you were not careful enough see here http://plugout.net/viewtopic.php?f=11&t=1082
Good to check if you miss some SMD parts in those spots

[uelpenich]

which firmware do you use? Lacie or fvdw-sl?

[raidsm]

I use FVDW with the kernel 4.6.6.

I did not broke a thing , I must have remove this drive about 100 times as I tried all king of hd inside this unit (noise test).

The NAS did load some things , but now I'm unable to access either in SSH or with the web admin page... Somehow it got stuck while loading. Is there a way to access with SSH temporarily via the fvdw installation console?

BTW I don't have a USB adapter so I'm stuck with trying to repair it inside the case....

[Jocko]

Somehow it got stuck while loading. Is there a way to access with SSH temporarily via the fvdw installation console?

Yes you can but think the firmware is not loaded in this case.

So get a telnet access by loading the kirkwood standalone kernel and post these outputs

Code: Select all

cat /proc/partitions
fdisk -l /dev/sda

mount sda7

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
ls -l /sda7/boot.log
cat /sda7/boot.log

search what fs partition is currently used

Code: Select all

ls /sda7/lacie-boot

you should see a file sdaxboot (x=1 or x=2)
mount the related partition

Code: Select all

mkdir /sdax
mount /dev/sdax /sdax
ls -l /sdax/boot.log
cat /sdax/boot.log


(x=1 or x=2)

[raidsm]

ok somehow this time I got ssh access...

here are my results

Code: Select all

root@NS2:/ # cat /proc/partitions
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8  973860551 sda8
root@NS2:/ #


Code: Select all

root@NS2:/ # fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      121127   976762583+ ee EFI GPT
root@NS2:/ #

Code: Select all

root@NS2:/ # fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      121127   976762583+ ee EFI GPT
root@NS2:/ # mkdir /sda7
root@NS2:/ # mount /dev/sda7 /sda7
root@NS2:/ # ls -l /sda7/boot.log
-rw-r--r--  1 root root 2590 2016-12-18 09:09 /sda7/boot.log
root@NS2:/ # cat /sda7/boot.log
start boot log
detect and set platform
nwsp2
UIMAGE-3142-NWSP2CL-14
Current kernel: 4.6.6 #4 PREEMPT Sun Dec 11 17:46:35 CET 2016
nwsp2
 mount dev/pts
update dev nodes
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sun Dec 18 09:08:29 EST 2016
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
create temporary group file
configure loopback network interface
setting reboot and standby
nwsp2
rebootd-nwsp2
nwsp2
standbyd-nwsp2
starting php based setup routines step 1

 * Starting udevd...                 [ OK ]
 * Found XML database configuration file...    [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Updating Disks database...           [ OK ]
 * Starting mount of volumes...
   - Mounting volume Default:  [ Fail ]
 * Finishing mount of volumes...        [ Fail ]
 * Generating Hosts File...           [ OK ]
 * Configuring System Hostname...        [ OK ] 
 * Configuring LAN interface...        [ OK ]
 * Initializing Timezone...           [ OK ]
 * Starting web server...
   Configure WebDav service :           [ OK ]
   Web server :                     [ OK ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...     [ OK ]
 * Configuring Disks...              [ OK ]
 * Configuring Samba...                [ OK ]
 * Configuring System Users...
   Root password: use custom password
   Set users, linux and samba accounts    [ OK ]
 * Starting Fvdw-sl Discovery Daemon...    [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...              [ OK ]
 * Kill temporary dropbear...          [ OK ]
starting php based setup routines step 3
 * Starting Explorer Service...  * Starting daemon update Hosts File...  [ OK ]
 * Starting USB Spin-down Guard...        [ OK ]
 * Starting Disk Temperature Guard...     [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...           [ OK ]
 * Starting AFP Service...              [ FAIL ]
 * Starting NTP client...              [ OK ]
 * Starting CRON Service...           [ FAIL ]
 * Starting Transmission Client...        [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 16.1
    built on: Oct 01 2015

    LAN IP address: 10.0.1.10 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
LED settings
else loop1 finished
rcS finished
root@NS2:/ #


Code: Select all

root@NS2:/ # ls /sda7/lacie-boot
root@NS2:/ # cd sda7
root@NS2:/sda7 # ls
bin      boot.log  direct-usb  lib         mail     opt              proc   sbin   sys  var
bin_cab  clunc     etc         linuxrc     mnt      php.ini          root   sda7   tmp  wol-enable
boot     dev       lacie-boot  lost+found  nowhere  postupgrade.log  rw_fs  share  usr
root@NS2:/sda7 # cd lacie-boot
root@NS2:/sda7/lacie-boot # ls
root@NS2:/sda7/lacie-boot # ls -a
.  ..
root@NS2:/sda7/lacie-boot # ls -l
total 0
root@NS2:/sda7/lacie-boot #


There is nothing in the Lacie-boot....?

there is something funny tho I got an unmounted usb drive in the /share/1000 directory... I did some test with fvdw to mount a hfs usb drive but this partition was a NTFS one... it's not the HFS I did try to mount but is on the same drive.

Code: Select all

root@NS2:/share/1000 # ls
fvdw  USB250GB_3


[raidsm]

Ok When I try to load the "old" 3.XX kernel , then the Nas just doesn't boot at all no activity on the drive...

[Jocko]

Hi raidsm,

There is nothing in the Lacie-boot....?

This is ok Just means you do not have yet upgrade the firmware since the first install.

root@NS2:/share/1000 # ls
fvdw USB250GB_3

* Starting mount of volumes...
- Mounting volume Default: [ Fail ]
* Finishing mount of volumes... [ Fail ]
* Starting Explorer Service...
* Starting AFP Service... [ FAIL ]
* Starting CRON Service... [ FAIL ]

This means the firmware failed to mount sda8 and the listed features need to have sda8 mounted to start.

ok somehow this time I got ssh access...

So post these outputs

Code: Select all

dmesg
mount
ps aux

and try to mount manually sda8 (not on /share/1000 !)

Code: Select all

mkdir /tmp/sda8
mount /dev/sda8 /tmp/sda8

[raidsm]

Ok I don't know why but my NAS just came back alive.... I think my hard drive is going bad , is there some sort of utility I can use to sync and repair? I won't turn it off until I got news from you guys ;)