new install fvdv trouble

[araldo60]

Code: Select all

root@fvdwsl-base:/ # `cat /direct-usb/fvdw/config-err.txt
>
> cat /direct-usb/fvdw/config-err.txt
> cp /usr/share/nzbget/webui/config.js /direct-usb/fvdw/config-err.txt
> chmod 666 /direct-usb/fvdw/config-err.txt
>
>
>
>
>

You have this behaviour because you enter a " ` " just before the first cat command. So enter another one or close the terminal and reopen a new one

And the right order is

Code: Select all

cp /usr/share/nzbget/webui/config.js /direct-usb/fvdw/config-err.txt
chmod 666 /direct-usb/fvdw/config-err.txt
cat /direct-usb/fvdw/config-err.txt


(you can submit one by one or at the same time: the breakline at each end line will perform a submit)

i had the file pdf

[Jocko]

Hi

Nope the file config.js doesn't seem to be corrupted So why gnutar thinks that ? :scratch

Anyhow we go to run e2fsck command on the partition sda1 and see what it returns.
So

Code: Select all

umount /rw_fs/tmp/upgrade/img
e2fsck -cpvf /dev/sda1

Please to run e2fsck command only if the partition is unmounted and do not close your terminal session as long as it is running (it may take 1 or 2 hours)

[araldo60]

Hi

Nope the file config.js doesn't seem to be corrupted So why gnutar thinks that ? :scratch

Anyhow we go to run e2fsck command on the partition sda1 and see what it returns.
So

Code: Select all

umount /rw_fs/tmp/upgrade/img
e2fsck -cpvf /dev/sda1

Please to run e2fsck command only if the partition is unmounted and do not close your terminal session as long as it is running (it may take 1 or 2 hours)

how can i verify if the partition is unmounted ?

[Jocko]

if umount failed to do it it should return an error message.

Anyhow if you run the command mount (which will list all mounted partitions). You have not to find a line beginning by "/dev/sda1"

[araldo60]

if umount failed to do it it should return an error message.

Anyhow if you run the command mount (which will list all mounted partitions). You have not to find a line beginning by "/dev/sda1"

root@fvdwsl-base:/ # umount /rw_fs/tmp/upgrade/img
umount: /rw_fs/tmp/upgrade/img: not mounted.
root@fvdwsl-base:/ # e2fsck -cpvf /dev/sda1
/dev/sda1: Updating bad block inode.

5098 inodes used (15.56%, out of 32768)
361 non-contiguous files (7.1%)
5 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 359/2/0
41563 blocks used (31.71%, out of 131072)
0 bad blocks
1 large file

3874 regular files
263 directories
121 character device files
171 block device files
0 fifos
6 links
660 symbolic links (660 fast symbolic links)
0 sockets
------------
5095 files

time execution 10 sec

[Jocko]

:scratch
So no bad block but only an inode issue...

Now remount /dev/sda1

Code: Select all

mount /dev/sda1  /rw_fs/tmp/upgrade/img
ls /rw_fs/tmp/upgrade/img

[araldo60]

:scratch
So no bad block but only an inode issue...

Now remount /dev/sda1

Code: Select all

mount /dev/sda1  /rw_fs/tmp/upgrade/img
ls /rw_fs/tmp/upgrade/img

Code: Select all

root@fvdwsl-base:/ # mount /dev/sda1  /rw_fs/tmp/upgrade/img
root@fvdwsl-base:/ # ls /rw_fs/tmp/upgrade/img
bin      boot   dev         etc  linuxrc     mail     opt   root  share  usr
bin_cab  clunc  direct-usb  lib  lost+found  nowhere  proc  sbin  sys    var
root@fvdwsl-base:/ #

[Jocko]

So run

Code: Select all

rm -rf /rw_fs/tmp/upgrade/img/usr
tar -xf /rw_fs/tmp/upgrade/fvdw-sl-18-2-base-18oct19.files.tar.gz -C /rw_fs/tmp/upgrade/img
gnutar --compare --file=/rw_fs/tmp/upgrade/fvdw-sl-18-2-base-18oct19.files.tar.gz -C /rw_fs/tmp/upgrade/img

Note: be careful with the first command (syntax)

[araldo60]

So run

Code: Select all

rm -rf /rw_fs/tmp/upgrade/img/usr
tar -xf /rw_fs/tmp/upgrade/fvdw-sl-18-2-base-18oct19.files.tar.gz -C /rw_fs/tmp/upgrade/img
gnutar --compare --file=/rw_fs/tmp/upgrade/fvdw-sl-18-2-base-18oct19.files.tar.gz -C /rw_fs/tmp/upgrade/img

Note: be careful with the first command (syntax)

root@fvdwsl-base:/ # rm -rf /rw_fs/tmp/upgrade/img/usr
root@fvdwsl-base:/ # tar -xf /rw_fs/tmp/upgrade/fvdw-sl-18-2-base-18oct19.files.
tar.gz -C /rw_fs/tmp/upgrade/img
root@fvdwsl-base:/ # gnutar --compare --file=/rw_fs/tmp/upgrade/fvdw-sl-18-2-bas
e-18oct19.files.tar.gz -C /rw_fs/tmp/upgrade/img

[Jocko]

So this time no warning from gnutar command ? in this case it was really this inode block issue.

So now you can make a new fw upgrade attempt