plugout.net

Today I was playing with Twonky media server, all went fine after I did a restart to see if the server was started at boot,
this was something I never should have done...

After the restart all!! of my shares are gone and in the webgui it says I have 0.00 available storage...
In the menu File Share I still can see the names from the shares, but it only says 'wait' at Total Size and Free Size (looks it 'hangs')
in /share/1000 I only have twonkymedia folder with twonky files, all of the other shares are gone.

df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 488M 167M 316M 35% /
/dev/sda5 740M 1.3M 731M 1% /rw_fs
tmpfs 4.9M 112K 4.8M 3% /rw_fs/tmp/usr/var
/dev/root 227M 163M 52M 77% /lacie-boot

The harddisk is a 3TB (red) NAS WD drive just 2years old.

In an other thread I red something it has to do with mounting sda8, this is the result.

mount /dev/sda8 /share/1000
mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
mount: relocation error: /usr/lib/libmount.so.1: symbol blkid_new_probe_from_filename, version BLKID_2.17 not defined in file libblkid.so.1 with link time reference

And another test.

e2fsck -ny /dev/sda8
e2fsck: /opt/lib/libblkid.so.1: no version information available (required by e2fsck)
e2fsck: /opt/lib/libblkid.so.1: no version information available (required by e2fsck)
e2fsck: /opt/lib/libblkid.so.1: no version information available (required by e2fsck)
e2fsck: /opt/lib/libuuid.so.1: no version information available (required by e2fsck)
e2fsck: symbol lookup error: e2fsck: undefined symbol: undo_io_manager

And now I'm stuck, is there any! solution to get at least my files back?
Any help is appreciated

Grtzz Mark

Your files are most likely still there only the data partition can not be mounted probably due to corruption of system partition

Which version of fvdw-sl are you running?

And please post output of

Code: Select all

ls /lacie-boot

If the output is

Code: Select all

sda1boot

then give this command

Code: Select all

cd /lacie-boot
mv sda1boot sda2boot

and reboot
System will now try to boot from second system partition and everything should be ok.
Only the fvdw-sl version will be a different one as sda2 will contain an older version but that can be solved by upgrading again. Before doing that running e2fsck on sda1 is recommended as this system partition seems to have gone corrupt possibly by a bad sector

If content of lacie-boot is different do not execute above commands but post the output of the ls command

Perfect! that did the trick thank you very! much, and indeed I'm back to fvdw-sl 17-0
I was on 18-2

Output from e2fsck /dev/sda1:

Code: Select all

e2fsck 1.42.11 (09-Jul-2014)
/dev/sda1: recovering journal
Setting free inodes count to 25526 (was 25525)
Setting free blocks count to 82178 (was 82179)
/dev/sda1: clean, 7242/32768 files, 48894/131072 blocks


So it looks I'm good to go to upgrade again.

df -h

Code: Select all

Filesystem                Size      Used Available Use% Mounted on
/dev/sda2               226.2M    148.4M     65.3M  69% /
/dev/sda5               739.9M      1.3M    731.0M   0% /rw_fs
tmpfs                     4.9M    120.0K      4.8M   2% /rw_fs/tmp/usr/var
/dev/sda8                 2.7T      1.5T      1.1T  57% /share/1000
/dev/root               226.2M    162.6M     51.0M  76% /lacie-boot


Indeed sda2 is now root, since sda1 looks ok, can't I move back to sda1 as root ?

And any idea what caused this problem?, all I did was playing around with some media servers
to see which one worked best for my mediaplayer.

Again thank you for the great help.

Grtzz Mark

Hi

Yagi1 wrote:Indeed sda2 is now root, since sda1 looks ok, can't I move back to sda1 as root ?

Nope, it seems there is also another issue with the lib cache on sda1 (maybe because you have installed some extra packages): never mount command should expect a lib in /opt.

So it is better to upgrade again for overwriting sda1