Accessing my cloudbox-slow blinking blue light

[deepeedoubleu]

Ok, I realized I was typing something incorrect. When I try to assemble the raid array i get mdadm not found. Am I missing something?

root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l mount.tar -r mount.tar -g 10.0.1.7


root@fvdw-sta-kirkwood:/ # tftp -l mount.tar -r mount.tar -g 10.0.1.7
mount.tar 100% |****************************************************************| 199k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tar -xvf mount.tar
usr/
usr/sbin/
usr/sbin/mount
usr/lib/
usr/lib/libblkid.so.1
usr/lib/libblkid.so.1.1.0
usr/lib/libblkid.so
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md0 /dev/sda8
-sh: mdadm: not found
root@fvdw-sta-kirkwood:/ #

[fvdw]

every time you boot the nas and load the standalone kernel you need to upload mdadm again if you want to use it, I explained that already some post earlier ;)

The reason is that this kernel and file system runs from RAM meaning it is gone after reboot. The standalone kernel contains some basic binaries but not mdadm so you need to upload it again when you reboot the nas and are using the standalone kernel

[deepeedoubleu]

Hello,

Everything went great until I tried the last part with the vgscan.

Is there anything else I can try from this point? Not sure of any other options you might be able to throw my way. I hope this data can be saved. :hammerhead


fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l mount.tar -r mount.tar -g 10.0.1.7
mount.tar 100% |****************************************************************| 199k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tftp -r mdadm -l /bin/mdadm -g 10.0.1.7
mdadm 100% |****************************************************************| 1100k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /bin/mdadm
root@fvdw-sta-kirkwood:/ # tar -xvf mount.tar
usr/
usr/sbin/
usr/sbin/mount
usr/lib/
usr/lib/libblkid.so.1
usr/lib/libblkid.so.1.1.0
usr/lib/libblkid.so
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md0 /dev/sda8
mdadm: /dev/md0 has been started with 1 drive.
root@fvdw-sta-kirkwood:/ # mkdir /md0
root@fvdw-sta-kirkwood:/ # /usr/sbin/mount /dev/md0 /md0
mount: unknown filesystem type 'LVM2_member'
root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l lvm-202_02_98-vs2--20may13.tar -r lvm-202_02_98-vs2--20may13.tar -g 10.0.1.7
lvm-202_02_98-vs2--2 100% |****************************************************************| 1767k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tar -xvf lvm-202_02_98-vs2--20may13.tar
./
./usr/
./usr/sbin/
./usr/sbin/lvremove
./usr/sbin/vgchange
./usr/sbin/pvscan
./usr/sbin/vgdisplay
./usr/sbin/lvdisplay
./usr/sbin/pvcreate
./usr/sbin/vgimportclone
./usr/sbin/vgconvert
./usr/sbin/vgextend
./usr/sbin/lvmdiskscan
./usr/sbin/vgimport
./usr/sbin/lvmsadc
./usr/sbin/vgremove
./usr/sbin/lvmsar
./usr/sbin/pvck
./usr/sbin/vgmknodes
./usr/sbin/lvconvert
./usr/sbin/lvmdump
./usr/sbin/lvmchange
./usr/sbin/pvremove
./usr/sbin/pvchange
./usr/sbin/vgscan
./usr/sbin/lvextend
./usr/sbin/pvs
./usr/sbin/lvreduce
./usr/sbin/vgcfgbackup
./usr/sbin/vgcfgrestore
./usr/sbin/vgcreate
./usr/sbin/vgrename
./usr/sbin/lvs
./usr/sbin/fsadm
./usr/sbin/vgreduce
./usr/sbin/vgsplit
./usr/sbin/lvcreate
./usr/sbin/vgmerge
./usr/sbin/vgck
./usr/sbin/vgexport
./usr/sbin/lvm
./usr/sbin/blkdeactivate
./usr/sbin/lvmconf
./usr/sbin/dmsetup
./usr/sbin/lvresize
./usr/sbin/vgs
./usr/sbin/lvrename
./usr/sbin/pvresize
./usr/sbin/lvscan
./usr/sbin/pvmove
./usr/sbin/lvchange
./usr/sbin/pvdisplay
./usr/lib/
./usr/lib/libdevmapper.so.1.02
./usr/lib/libncurses.so.5.7
./usr/lib/libdevmapper.so
./usr/lib/libncurses.so.5
./opt/
./opt/lib/
./opt/lib/libreadline.so.5.2
./opt/lib/libgcc_s.so
./opt/lib/libgcc_s.so.1
./opt/lib/libreadline.so.5
root@fvdw-sta-kirkwood:/ # /usr/sbin/vgscan
/usr/sbin/vgscan: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory

[fvdw]

Mmm..seems we need some additional library files to make vgscan work, Ithought I had included them all, apperently not. I will prepare a new LVM package later this evening

No worries, we will solve this

[fvdw]

as promised the update lvm archive upload this one instead of the previous one and extract it
Now vgscan should work (tested on my 5big2)
ps don't forget to upload again mdadm and assemble the raid array if you have performed a reboot
ps 2 for your convenience I updated the instructions to install lvm tools on page 3 of this topic

Code: Select all

root@fvdw-sta-kirkwood:/ # vgscan
  Reading all physical volumes.  This may take a while...
  No volume groups found
root@fvdw-sta-kirkwood:/ #

Of course on my disk it doesn't find logical volumes

[deepeedoubleu]

Ok It seems to have went through now. I still don't see my drive on my network and is not being found by Network Assistant as of yet. The blue light is blinking fast. Should I let it sit? What would be the next step?

Thank you


fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l mount.tar -r mount.tar -g 10.0.1.7
mount.tar 100% |**************************************************************| 199k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tftp -r mdadm -l /bin/mdadm -g 10.0.1.7
mdadm 100% |**************************************************************| 1100k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /bin/mdadm
root@fvdw-sta-kirkwood:/ # tar -xvf mount.tar
usr/
usr/sbin/
usr/sbin/mount
usr/lib/
usr/lib/libblkid.so.1
usr/lib/libblkid.so.1.1.0
usr/lib/libblkid.so
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md0 /dev/sda8
mdadm: /dev/md0 has been started with 1 drive.
root@fvdw-sta-kirkwood:/ # mkdir /md0
root@fvdw-sta-kirkwood:/ # /usr/sbin/mount /dev/md0 /md0
mount: unknown filesystem type 'LVM2_member'
root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l lvm-202_02_98-vs2--20may13.tar -r lvm-202_02_98-vs2--20may13.tar -g 10.0.1.7
tftp: server error: (1) File not found
root@fvdw-sta-kirkwood:/ # tftp -l lvm-202_02-98-vs2--20may13.tar -r lvm-202_02_98-vs3-19meil16.tar -g 10.0.1.7
tftp: server error: (1) File not found
root@fvdw-sta-kirkwood:/ # tftp -l lvm-202_02_98-vs3-19mei16.tar -r lvm-202_02_98-vs3-19mei16.tar -g 10.0.1.7
lvm-202_02_98-vs3-19 100% |**************************************************************| 1779k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ #
root@fvdw-sta-kirkwood:/ # tar -xvf lvm-202_02_98-vs3-19mei16.tar
./
./usr/
./usr/sbin/
./usr/sbin/pvdisplay
./usr/sbin/vgs
./usr/sbin/vgsplit
./usr/sbin/lvconvert
./usr/sbin/vgexport
./usr/sbin/lvresize
./usr/sbin/pvck
./usr/sbin/pvs
./usr/sbin/vgcreate
./usr/sbin/pvmove
./usr/sbin/pvchange
./usr/sbin/lvdisplay
./usr/sbin/vgremove
./usr/sbin/fsadm
./usr/sbin/lvm
./usr/sbin/vgcfgrestore
./usr/sbin/vgck
./usr/sbin/lvreduce
./usr/sbin/lvchange
./usr/sbin/vgrename
./usr/sbin/lvextend
./usr/sbin/lvrename
./usr/sbin/lvremove
./usr/sbin/vgscan
./usr/sbin/blkdeactivate
./usr/sbin/pvcreate
./usr/sbin/lvscan
./usr/sbin/vgreduce
./usr/sbin/pvremove
./usr/sbin/vgmerge
./usr/sbin/vgdisplay
./usr/sbin/lvmsadc
./usr/sbin/lvmdiskscan
./usr/sbin/vgchange
./usr/sbin/lvmsar
./usr/sbin/dmsetup
./usr/sbin/vgextend
./usr/sbin/lvmconf
./usr/sbin/lvmchange
./usr/sbin/pvresize
./usr/sbin/pvscan
./usr/sbin/vgconvert
./usr/sbin/lvmdump
./usr/sbin/vgcfgbackup
./usr/sbin/vgimport
./usr/sbin/lvcreate
./usr/sbin/lvs
./usr/sbin/vgmknodes
./usr/sbin/vgimportclone
./usr/lib/
./usr/lib/libdevmapper.so.1.02
./usr/lib/libncurses.so.5
./usr/lib/libncurses.so.5.7
./usr/lib/libreadline.so.5
./usr/lib/libdevmapper.so
./opt/
./opt/lib/
./opt/lib/libgcc_s.so
./opt/lib/libgcc_s.so.1
./opt/lib/libreadline.so.5.2
./opt/lib/libreadline.so.5
./lib/
./lib/libdl-2.17.so
./lib/libdl.so.2
root@fvdw-sta-kirkwood:/ # /usr/sbin/vgscan
Reading all physical volumes. This may take a while...
Found volume group "vg" using metadata type lvm2
root@fvdw-sta-kirkwood:/ #

[fvdw]

Ok this looks promising it found a volume group, to be continued this evening. Now I am at work

For the moment you can try what this command gives as output.

Code: Select all

pvdisplay /dev/md0

Ps of course the drive is not accesible via lacie assistance, we are not running the firmware but a standalone kernel. Our goal is to mount the data partition and then copy your files. How to do that is another story as the cloudbox doesnot have an usb port to connect an external harddisk. But lets first find if we can access the data.

[fvdw]

to move on we need to know the names and info of the logical volumes, give this command

Code: Select all

lvmdiskscan

and

Code: Select all

lvdisplay

and to see if they are active

Code: Select all

lvscan

and post the output

[deepeedoubleu]

Alright, here we go:

root@fvdw-sta-kirkwood:/ # pvdisplay /dev/md0
--- Physical volume ---
PV Name /dev/md0
VG Name vg
PV Size 2.72 TiB / not usable 1.31 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 714260
Free PE 0
Allocated PE 714260
PV UUID MqLaZt-w8Qc-VFIs-I1ab-PkhF-LAZw-VkVDXB

root@fvdw-sta-kirkwood:/ # lvmdiskscan
/dev/ramdisk [ 4.00 MiB]
/dev/md0 [ 2.72 TiB] LVM physical volume
/dev/ram [ 4.00 MiB]
/dev/ram2 [ 4.00 MiB]
/dev/sda2 [ 192.00 MiB]
/dev/ram3 [ 4.00 MiB]
/dev/ram4 [ 4.00 MiB]
/dev/ram5 [ 4.00 MiB]
/dev/ram6 [ 4.00 MiB]
/dev/ram7 [ 4.00 MiB]
/dev/ram8 [ 4.00 MiB]
/dev/ram9 [ 4.00 MiB]
2 disks
9 partitions
0 LVM physical volume whole disks
1 LVM physical volume
root@fvdw-sta-kirkwood:/ # lvdisplay
--- Logical volume ---
LV Path /dev/vg/lv
LV Name lv
VG Name vg
LV UUID dmI1Td-FBsw-ETiw-V6m0-zi1x-HwHm-DbtTCS
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 2.72 TiB
Current LE 714260
Segments 1
Allocation inherit
Read ahead sectors auto

root@fvdw-sta-kirkwood:/ # lvscan
inactive '/dev/vg/lv' [2.72 TiB] inherit
root@fvdw-sta-kirkwood:/ #

[fvdw]

nice now we have all information to mount the data partition
The path to use is : /dev/vg/lv

Perculiar is that the logical volume is inactive

So lets try to activate it (needed to be able to mount it)

Code: Select all

lvchange -a y /dev/vg/lv

Now try to mount it

Code: Select all

mkdir /data
mount /dev/vg/lv /data

If that succeed change to the directory where we mounted the partition

Code: Select all

cd /data

and list the content

Code: Select all

ls -al

If correct you will get a list with folders and maybe file, I think folders, you can change to the se folders using the "cd" command and look to the content of each one to find were your data files are.

ps. As the logical volume was inactive maybe there is an issue with the partition. I don't know if it is the cause of why boot of the lacie hangs, but you could try after you have activated the logical volume if the cloudbox wants to complete boot. It is not likely as the firmware itself is on a different partition but it may hang becuase it is waiting for activating the logical volume.
But if I were you I would first look to the content of partition if it is ok, so lets do that first and then discuss again whats next

--edit note that the lvmdiskscan only finds /dev/sda2, it should also find /dev/sda3. That partion contains crucial files to let the lacie firmware boot. We will have a closer look to that later