Problems upgrading to V17 (part2)

[peetn]

Hello,

Is see my original post is locked...
If you want me to continue there, please unlock it.

I have only today seen your last reply there and investigated.

I upgraded first successfully to 'fvdw-sl-16.1-upgrade-patch-21dec2018.zip'.
Then I ran 'e2fsck -n /dev/sda2' (output attached).
There still were issues.
I managed to fix those issues running 'e2fsck -c /dev/sda2', see attachment (Output e2fsck -c _dev_sda2).

However, (manual) update to V17 still failed (upgrade output to v17.png) with the same error.

Do you have other suggestions?
Can I provide more logs?

I also attached the "SMART" output and the output of the short test/long test/general condition test.

[fvdw]

Remark
Check using command

Code: Select all

mount

that sda2 is bot mounted before using e2fsck.
e2fsck may only be used on not mounted file systems

Option 1

You could run again

Code: Select all

e2fsck -n /dev/sda2

again to see of there are still issues with sda2
If this is the case run

Code: Select all

e2fsck -y /dev/sda2

Run again e2fsck with -n -f options to see if filesystem is clean.
Try again to upgrade

Option 2

Format sda2

Code: Select all

mke2fs.ext3-m1 -j /dev/sda2

It will mention that a file system is present
Let it overwrite the existing file system.
Check after formatting using e2fsck if file system is clean.
If all oké try to upgrade again.

If sda2 continues to gave problems.
Then you will not be able to upgrade as we need two working system partitions to be able to swap

[peetn]

Hello,

Thanks for the reply.

I was unable to unmount sda2:

Code: Select all

root@SPD8020-7EA8B0:/ # umount /dev/sda5
umount: /rw_fs: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

What could I do here?


Anway, I ran

Code: Select all

e2fsck -n /dev/sda2

and it saw 2 more inode remarks which it fixed by running

Code: Select all

e2fsck -y /dev/sda2

Then there were no remarks anymore.
Upgrade still failed.

For option 2: I didn't try that yet.
Will formatting delete data and will I lose my files on the public share?

[Jocko]

Hi

Why did you try to unmount sda5 :scratch you just need to unmount /dev/sda2 before running e2fsck

What is sda2 size?
Please to post

Code: Select all

fdisk -l /dev/sda
tune2fs -l /dev/sda2

For option 2: I didn't try that yet.
Will formatting delete data and will I lose my files on the public share?

No sda2 is only a fw partition and contains no user data. Of course you have to check if you format sda2 and not another one :whistle

[peetn]

My appologies about the mounting.
I unmounted sda2 and ran the e2fsck again, see attachment.
Do I mount sda2 again? To where?
I have not formatted it yet. Do I try (based on the output below)?


Output of "fdisk"

Code: Select all

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *           1          32      256016  83 Linux
/dev/sda2              33          64      257040  83 Linux
/dev/sda3              65          96      257040  82 Linux swap
/dev/sda4              97      243201  1952740912+  5 Extended
/dev/sda5              97         144      384536  83 Linux
/dev/sda6             145      243201  1952354328+ 83 Linux


Output of "tune2fs"

Code: Select all

tune2fs 1.42.11 (09-Jul-2014)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          a2d9e80b-003a-45b4-96c3-f46c96833d46
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:         unsigned_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              64000
Block count:              64000
Reserved block count:     3200
Free blocks:              19998
Free inodes:              58847
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      15
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         32000
Inode blocks per group:   1000
Filesystem created:       Thu Aug 30 21:49:50 2012
Last mount time:          Tue Mar 17 11:37:39 2020
Last write time:          Tue Mar 17 11:40:20 2020
Mount count:              0
Maximum mount count:      38
Last checked:             Tue Mar 17 11:40:20 2020
Check interval:           15552000 (6 months)
Next check after:         Sun Sep 13 12:40:20 2020
Lifetime writes:          144 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:             128
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      44295040-3daa-46f0-a4cb-f2cd9aaca73d
Journal backup:           inode blocks


[fvdw]

e2fsck reports file system is oke but thats no guarantee that there are no badblocks
Test the partition by using this command

Code: Select all

dd if=/dev/sda2 bs=1 of=/share/1000/public/sda2.img

In this command I assumed you have a shared folder with name "public"

it should finish without I/O error, please post output
Also give after finishing the dd command the command

Code: Select all

dmesg

This to see if it reports disk errors

[Jocko]

According with his partition table it is an old scheme with a small sda5 size.

About sda2 size it is ok : 251MB whereas the firmware size is 250MB. However if sda5 size (375MB) is too small, at the step1, the uncompressed files maybe corrupted.

So I advice to try to update the fw just after a reboot. Do not run the step2, but post only

Code: Select all

df -h
ls -al /tmp
ls -al /tmp/upgrade

[peetn]

There is an .img file generated of 251MB (263.208.960 bytes). Do you want me to post (a link to) that file?
I'll run it now for the sda5 too?

The dmesg output is attached.

I did a reboot and tried to update the fw:
- Step1:
- Step2: not started yet on your advise

Output df:

Code: Select all

Filesystem                Size      Used Available Use% Mounted on
/dev/root               242.2M    160.1M     69.6M  70% /
/dev/sda5               364.6M    100.9M    244.9M  29% /rw_fs
tmpfs                   200.0K     56.0K    144.0K  28% /rw_fs/tmp/usr/var
/dev/sda6                 1.8T      1.0T    780.3G  57% /share/1000


Output ls attached

[Jocko]

Hi

So you also have some issue with sda5: fs corrupted and it seems to be overloaded

Please to post the asked outputs of

Code: Select all

df -h
ls -l /rw_fs/etc
ls -l /rw_fs/tmp

---edit---
You have edited your post and now there are the asked output

You can not run a fs scan because you can not unmount it. So this may be done only on nas booting as you have a phn and you can not use fvdw-sl console with it.
So please to post these additional output

Code: Select all

e2fsck -n /dev/sda5
mount
cat /etc/patch_log

The last output is important I need to know the real fw environment on your nas to pacth the boot script

[peetn]

Hello,

for df -h command, see my edit of my previous post.
For ls -l commands: see attached screenshot

e2fsck -n /dev/sda5 output:

Code: Select all

Warning!  /dev/sda5 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
The filesystem size (according to the superblock) is 385528 blocks
The physical size of the device is 384536 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no

/dev/sda5 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 8080 has zero dtime.  Fix? no

Deleted inode 24144 has zero dtime.  Fix? no

Deleted inode 36189 has zero dtime.  Fix? no

Error reading block 385027 (Invalid argument) while getting next inode from scan.  Ignore error? no

Error while scanning inodes (94376): Can't read next inode

/dev/sda5: ********** WARNING: Filesystem still has errors **********


/dev/sda5: ********** WARNING: Filesystem still has errors **********



mount output:

Code: Select all

rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
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/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=0,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=200k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/proc/bus/usb on /proc/bus/usb type usbfs (rw,relatime)
/dev/sda6 on /share/1000 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)


cat /etc/patch_log output

Code: Select all

[2017-09-30 12:37:24]   unzip|unzip   fvdw-sl 16.1   phn   /fvdw-sl-16.1-upgrade-patch-30may2017.zip(fvdw-sl-16.1-upgrade-patch-30may2017.tar)   OK
[2020-03-16 08:27:03]   unzip|unzip   fvdw-sl 16.1   phn   /fvdw-sl-16.1-upgrade-patch-21dec2018.zip(fvdw-sl-16.1-upgrade-patch-21dec2018.tar)   OK