Accessing my cloudbox-slow blinking blue light

[deepeedoubleu]

I apologize for my delay in getting back to you. This weekend got crazy. I followed your steps, but I don't believe the activation or mount was successful. I did not proceed after attempting to mount it since it seems like nothing was happening.

root@fvdw-sta-kirkwood:/ # lvchange -a y /dev/vg/lv
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory
root@fvdw-sta-kirkwood:/ # mkdir /data
root@fvdw-sta-kirkwood:/ # mount /dev/vg/lv /data

Thanks!

[deepeedoubleu]

i wanted to add that before finding this forum I attempted to complete a recovery and restore on my drive and was unsuccessful. While the drive wasn't being found on the network before I did this, I am not sure if this could be a contributing factor to any issues with activating the drive.

[fvdw]

When mount command gives no error message it means it succeeded.
You can check to see if mount is ok with this command

Code: Select all

mount

It will list all mounts

After having mounted the logical volume proceed with commands to list the content of the mountpoint. There is no risk of damaging anything with this command

Code: Select all

ls -al /data

[deepeedoubleu]

Ok here is what i see:


root@fvdw-sta-kirkwood:/ # lvchange -a y /dev/vg/lv
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory
root@fvdw-sta-kirkwood:/ # mkdir /data
root@fvdw-sta-kirkwood:/ # mount /dev/vg/lv /data
root@fvdw-sta-kirkwood:/ # mount
rootfs on / type rootfs (rw,size=124976k,nr_inodes=31244)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mapper/vg-lv on /data type ext4 (rw,relatime,data=ordered)
root@fvdw-sta-kirkwood:/ # ls -al /data
total 48
drwxr-xr-x 10 root root 4096 May 12 2016 .
drwxr-xr-x 15 root root 440 Jan 6 01:02 ..
drwxr-xr-x 2 root root 4096 May 12 2016 afp_db
drwxr-xr-x 3 root root 4096 May 22 2013 autoupdate
drwx------ 2 root root 16384 Jan 1 2010 lost+found
drwxr-xr-x 2 root root 4096 May 12 2016 reserved
drwxr-xr-x 3 root root 4096 May 12 2016 shares
drwxr-xr-x 2 root root 4096 May 12 2016 tmp
drwxr-xr-x 2 root root 4096 May 22 2013 torrent_dir
drwxr-xr-x 5 root root 4096 May 22 2013 var
root@fvdw-sta-kirkwood:/ #

[fvdw]

Seems we don't need to activate the volume. So no need to repeat the lvchange command.
And the good news is that we can read the content. :thumbup Look what is inside the subfolder shares, probably you will find your files there

Code: Select all

ls -al /data/shares

If you want to look in a subfolder of the this folder add the name to the command

Code: Select all

ls -al /data/shares/xxxx

(replace xxxx by the name of the subfolder

[Jocko]

@fvdw

As now md4 can be mounted (I assume there was an fs issue on the logical volume)

So maybe a reboot can restore access on the shares

[deepeedoubleu]

I have been experiencing internet issues. I have to go through everything again and will be on this tomorrow.

[deepeedoubleu]

I apologize for my delay to get back to you. When I try to access the shares this is what I see. I don't understand where the share name is to check other folders. I am back online and ready to get this matter resolved (hopefully). :hammerhead Please respond when you can.

root@fvdw-sta-kirkwood:/ # ls -al /data
total 48
drwxr-xr-x 10 root root 4096 May 12 2016 .
drwxr-xr-x 15 root root 440 Jan 1 00:07 ..
drwxr-xr-x 2 root root 4096 May 12 2016 afp_db
drwxr-xr-x 3 root root 4096 May 22 2013 autoupdate
drwx------ 2 root root 16384 Jan 1 2010 lost+found
drwxr-xr-x 2 root root 4096 May 12 2016 reserved
drwxr-xr-x 3 root root 4096 May 12 2016 shares
drwxr-xr-x 2 root root 4096 May 12 2016 tmp
drwxr-xr-x 2 root root 4096 May 22 2013 torrent_dir
drwxr-xr-x 5 root root 4096 May 22 2013 var
root@fvdw-sta-kirkwood:/ # ls -al /data/shares
total 12
drwxr-xr-x 3 root root 4096 May 12 2016 .
drwxr-xr-x 10 root root 4096 May 12 2016 ..
drwxrwxrwx 3 root root 4096 May 12 2016 1
root@fvdw-sta-kirkwood:/ # ls -al /data/shares/lost+found
ls: /data/shares/lost+found: No such file or directory
root@fvdw-sta-kirkwood:/ #

[fvdw]

Ok, and what does

Code: Select all

ls -al /data/shares/1

gives as output.
Further it is strange that the command to list content of folder /data/shares gives as output 12 entries but in your post only 4 are listed, did you copy all the output

[deepeedoubleu]

Thanks for responding. I was thinking the same why it was stating 12, but not all seem to be shown. This is exactly what I see when I try accessing shares. Nothing else appears on the screen. When I try to access the l share, it states the file directory can not be found.

root@fvdw-sta-kirkwood:/ # root@fvdw-sta-kirkwood:/ # ls -al /data/shares
total 12
drwxr-xr-x 3 root root 4096 May 12 2016 .
drwxr-xr-x 10 root root 4096 May 12 2016 ..
drwxrwxrwx 3 root root 4096 May 12 2016 1
root@fvdw-sta-kirkwood:/ # ls -al /data/shares/l
ls: /data/shares/l: No such file or directory
root@fvdw-sta-kirkwood:/ #