Reboot = no files on hdd

[sakal]

Hello, can anyone help me fix issue?

Whats happend: Electricity go down for 1sec and everything reboot, my PC, my NAS and so on.

After reboot of NAS when i login on LACIE i see =
https://i.ibb.co/0D1MSY6/QrcenMY.png

in ssh console i see:
https://imgur.com/eEBr2ny

BUT when i plug this HDD to my PC where is ubuntu desktop i can see all files. :laughat

QUESTION IS: How to make this disk with files working as it was before and see all files on harddrive? :please

Thanks for all your ideas and help :applause

[Jocko]

Hi

Your files are missing because sda8 (data partition) is not mounted. I assume the filesystem is corrupted on it and the firmware failed to mount (I assume on UBUNTU the partition was then read-only mounted and you had to read some errors in the dmesg output)

It is quiet easy to fix that : load the disk setup menu and click on your volume name (default name is Vol-A) to open its setup menu. Then click on the button "Check and repair the filesystem"

[sakal]

Hi,

thx for nice answer but after i did turn off with power button and i try it 3 times still have error :(

https://pasteboard.co/fLEWRzCUttBe.jpg

Maybe also help boot log:

Code: Select all

start boot log
is a physical machine
detect and set platform
cloudbox
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
device cloudbox
family kirkwood
mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = cloudbox
source = buttons-cloudbox
buttons-nwsp2 daemon started
Keep old Min free memory=2000
Wed Mar 16 21:00:20 UTC 2022
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 4.x
/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
configure loopback network interface
setting reboot and standby
cloudbox
rebootd-cloudbox
cloudbox
standbyd-cloudbox
starting php based setup routines step 1
* Found database configuration file...   [ OK ]
* Generating Hosts File...                       [ OK ]
* Configuring System Hostname...                 [ OK ]
* Configuring LAN interface...           [ OK ]
* Starting web server...                                 [ OK ]
* Starting Fvdw-sl Discovery Daemon...   [ OK ]
* Configuring Samba...                                   [ OK ]
* Configuring System Users...
Root password: use custom password
Set users, linux and samba accounts      [ OK ]
start rpcbind service
starting php based setup routines step 2

Warning: filesize(): stat failed for /rw_fs/tmp/etc/nas_conf_vltl.xml in /etc/finc/configfunc_read.finc on line 33
* Starting dropbear...                           [ OK ]
* Kill temporary dropbear...                     [ OK ]
starting php based setup routines step 3
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.2 patched
built on: October 18 2019

LAN IP address: 192.168.8.54 (DHCP)

Port configuration:

LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings

[Jocko]

Hi

So it seems you have a corrupted firmware image ! Maybe you have installed some external packages ?
mount and e2fsck binaries require now libraries not provided by our firmware :tapfoot (and in this case it is only this issue and not a corrupted fs on sda8)

So can you post these outputs

Code: Select all

ls -l /bin/mount
ldd /usr/bin/mount
ldd /usr/sbin/e2fsck
ls /usr/lib/libmount.so.1
ldd /usr/lib/libmount.so.1

We can try to reset the library cache. So do

Code: Select all

mv /etc/ld.so.cache /etc/ld.so.cache.bak
ldconfig
ls -l ld.so.cache

then repeat

Code: Select all

ldd /usr/bin/mount
ldd /usr/sbin/e2fsck
ldd /usr/lib/libmount.so.1

Caution: do not try to upgrade the firmware (to get again a fresh version 18.2) because the feature uses mount command to proceed this

[sakal]

Thank for your great support , here is output from console :


1st part:

Code: Select all

bash-4.3# ls -l /bin/mount
lrwxrwxrwx  1 root root 16 May 27  2017 /bin/mount -> ../usr/bin/mount
bash-4.3# ldd /usr/bin/mount
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
        libmount.so.1 => /usr/lib/libmount.so.1 (0xb6e93000)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6e83000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6e78000)
        librt.so.1 => /lib/librt.so.1 (0xb6e69000)
        libc.so.6 => /lib/libc.so.6 (0xb6d2d000)
        /lib/ld-linux.so.3 (0xb6ee8000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6d06000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6ce6000)
bash-4.3# ldd /usr/sbin/e2fsck
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libuuid.so.1: no version information available (required by /usr/sbin/e2fsck)
        libext2fs.so.2 => /opt/lib/libext2fs.so.2 (0xb6f89000)
        libcom_err.so.2 => /opt/lib/libcom_err.so.2 (0xb6f7f000)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6f6f000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6f64000)
        libe2p.so.2 => /opt/lib/libe2p.so.2 (0xb6f57000)
        libdl.so.2 => /lib/libdl.so.2 (0xb6f4c000)
        libc.so.6 => /lib/libc.so.6 (0xb6e10000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6de9000)
        /lib/ld-linux.so.3 (0xb6fbd000)
bash-4.3# ls /usr/lib/libmount.so.1
/usr/lib/libmount.so.1
bash-4.3# ldd /usr/lib/libmount.so.1
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6e81000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6e76000)
        librt.so.1 => /lib/librt.so.1 (0xb6e67000)
        libc.so.6 => /lib/libc.so.6 (0xb6d2b000)
        /lib/ld-linux.so.3 (0xb6ee6000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6d04000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6ce4000)

2nd part:

Code: Select all

bash-4.3# mv /etc/ld.so.cache /etc/ld.so.cache.bak
bash-4.3# ldconfig
bash-4.3# ls -l ld.so.cache
ls: ld.so.cache: No such file or directory
bash-4.3# locate ld.so.cache
bash: locate: command not found
bash-4.3# find -name "ld.so.cache"
./etc/ld.so.cache
bash-4.3# ls -l ./etc/ld.so.cache
-rw-r--r--  1 root root 26453 Mar 17 11:40 ./etc/ld.so.cache

3td part:

Code: Select all

bash-4.3# ldd /usr/bin/mount
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/bin/mount: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
        libmount.so.1 => /usr/lib/libmount.so.1 (0xb6f19000)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6f09000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6efe000)
        librt.so.1 => /lib/librt.so.1 (0xb6eef000)
        libc.so.6 => /lib/libc.so.6 (0xb6db3000)
        /lib/ld-linux.so.3 (0xb6f67000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6d8c000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6d6b000)
bash-4.3# ldd /usr/sbin/e2fsck
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libblkid.so.1: no version information available (required by /usr/sbin/e2fsck)
/usr/sbin/e2fsck: /opt/lib/libuuid.so.1: no version information available (required by /usr/sbin/e2fsck)
        libext2fs.so.2 => /opt/lib/libext2fs.so.2 (0xb6fa6000)
        libcom_err.so.2 => /opt/lib/libcom_err.so.2 (0xb6f9c000)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6f8c000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6f81000)
        libe2p.so.2 => /opt/lib/libe2p.so.2 (0xb6f74000)
        libdl.so.2 => /lib/libdl.so.2 (0xb6f69000)
        libc.so.6 => /lib/libc.so.6 (0xb6e2c000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6e05000)
        /lib/ld-linux.so.3 (0xb6fd3000)
bash-4.3# ldd /usr/lib/libmount.so.1
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
/usr/lib/libmount.so.1: /opt/lib/libblkid.so.1: no version information available (required by /usr/lib/libmount.so.1)
        libblkid.so.1 => /opt/lib/libblkid.so.1 (0xb6f53000)
        libuuid.so.1 => /opt/lib/libuuid.so.1 (0xb6f48000)
        librt.so.1 => /lib/librt.so.1 (0xb6f39000)
        libc.so.6 => /lib/libc.so.6 (0xb6dfd000)
        /lib/ld-linux.so.3 (0xb6fb1000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6dd6000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6db6000)


[Jocko]

Hi

Yes you have a corrupted fw image and some additional packages have to be installed. For example, I checked there is no library (or symlink) "libblkid.so.1" in the folder "/opt/lib/" its right location is /usr/lib.

Code: Select all

root@Acrab:/ # ldd /usr/lib/libmount.so.1
        libblkid.so.1 => /usr/lib/libblkid.so.1 (0xb6f08000)
        libuuid.so.1 => /usr/lib/libuuid.so.1 (0xb6efd000)
        librt.so.1 => /lib/librt.so.1 (0xb6ee6000)
        libc.so.6 => /lib/libc.so.6 (0xb6d99000)
        /lib/ld-linux.so.3 (0xb6f9b000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6d6e000)


So you have to use fvdw-sl console to write again the fw image on sda1 partition (I am not sure you can upgrade successfully the firmware from the web-interface)

Then start fvdw-sl console and select the action "Write fvdw-sl firmware image to disk". At the related step, ask to write the image on sda1. After rebooting, you should get now a fresh version 18.1. Check if you get again access on your data. if yes you can upgrade to version 18.2, but you have to install first a patch for version 18.1 (https://plugout.net/viewtopic.php?f=7&t=3532) and after upgrading to version 18.2, install its roll-up patch (https://plugout.net/viewtopic.php?f=7&t=3532)

[sakal]

If is possible i want try first: (web-interface)

1)
Can i simple update firmware: fvdw-sl firmware version 18-2
over: fvdw-sl firmware version 18-2 ?

2)
Or first fvdw-sl firmware version 18-1 and after i should go on fvdw-sl firmware version 18-2 ?

[Jocko]

1)
Can i simple update firmware: fvdw-sl firmware version 18-2
over: fvdw-sl firmware version 18-2 ?

There is no guarantee because the upgrade script need to mount a system partition to write the new files. So I assume it will fail at this step

[sakal]

I

1) Are we 100% sure with installation sda8 will be safe and all files will be not erased? Yes if you select the action "Write fvdw-sl firmware image to disk"" and not the action "Install fvdw-sl firmware" which rebuilds a new partition table

2) After installation from step 1 = Will be configuration still there? All files all transmission config, samba config and so on?what step1 do you talk ? if it is step1 of the upgrade script from the web-interface, yes because step1 retrieves only the required archives (and if it is successful that does not mean step 2 will be ok)

3) It is not more easy to move data to other HDD , delete HDD (all partitions) where is courted FS, install clean NAS SW and than copy files back ? No what I suggest it is easy and safe

[Jocko]

I posted my answers in your post