Problems upgrading to V17 (part2)

[Jocko]

So try to run step2 and re-post

Code: Select all

df- h
ls -l /tmp
ls -l /tmp/upgrade

[fvdw]

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?

Oke so sda2 can be fully read without i/o error, meaning no had block.

Yes you could repeat it for sda5. Just to verify that it has no bad blocks.


About firware upgrade attempt.
Are you still waiting to start step 2?

Ps I see from your last post that sda5 file system is not clean. That might cause issues. However as Jocko mentioned e2fsck cannot be run to repair on a mounted file system.
So follow his advice how to proceed

[Jocko]

So attached a patch to run a fs scan on sda5 before mounting it.

Store the attached file in fvdw share and install it with the keycode : 'unzip'

Before rebooting, check if you have now two rcS scripts

Code: Select all

ls -l /etc/init.d/rcS*
-rwxr-xr-x  1 root root 20716 2020-03-21 09:59 /etc/init.d/rcS
-rwxr-xr-x  1 root root 20399 2017-05-20 12:28 /etc/init.d/rcS.org


after rebooting, the original boot script is restored and if you want to run a new fs scan you have to install again the patch

So if all is ok, reboot your nas (only one time) and post

Code: Select all

cat /boot.log
e2fsck -fn /dev/sda5

sda5 should be clean now

[peetn]

Hello,

thanks for the great help.

This is what I did:

1) run step2 (as asked by Jocko)

So try to run step2 and re-post

Code: Select all

df- h
ls -l /tmp
ls -l /tmp/upgrade

Results attached. It failed with a new code (624).
Output of the above commands attached too.


2) installed the patch
it succeeded and I indeed had 2 scripts

3) reboot

4) ran the cat command (the boot.log is attached) + ran the e2fsck command (still errors)
also a screenshot attached in the zip file

[Jocko]

So your issue is on sda5 side.

First the fs scan on nas booting aborted:

Code: Select all

/dev/sda5: recovering journal
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? yes

So sda5 fs is not restored

You got the code 624 because there is also an error with the uncompressed fs image. Its size is wrong, around 124MB instead of 250MB !

You do not post the file df.txt, I think there is some useful information here to understand what happens on step2. I think the common zip archive with fvdw-sl console is too big with your tiny sda5 partition which has also an issue with its side...


Note: now I am not here for few hours...

[peetn]

my appologies, i didn't add the df.txt since the output of df -h was in the screenshot above (Step2 output of requested command) - the first lines in there...

i ran the command again
both attached (original + new)

if the sda5 is too small, can i easily make it bigger? (i'm afraid not...)

btw: i'm now running

Code: Select all

dd if=/dev/sda5 bs=1 of=/share/1000/public/sda5.img > dd.txt &

I guess it will again take half a day

[fvdw]

btw: i'm now running
Code:
dd if=/dev/sda5 bs=1 of=/share/1000/public/sda5.img > dd.txt &

I guess it will again take half a day

did it take that long on sda2 ?
Thats not normal

Anyhow dd should copy 393.764.864 bytes

ps sda5 size should be sufficient and no you cannot make it larger.
But there are other ways to get a firmware image on sda2.
But lets first try to solve sda5 issue because if not you will be faced everytime with problems as it is used for future upgrades

[Jocko]

So after your read dd command on sda5, I think the best way is to try to format again sda5. (currently sda5 uses a bad superblock or a corrupted one, maybe it is why you have a bad read speed)

To do it, you need to backup some data from sda5,

Code: Select all

cd /rw_fs
tar -czf /my-sda5-etc.gz etc

Be careful you need to do the cd command before running the tar command and keep exactly the pathname for the tarball (/my-sda5-etc.gz). The patched script expects to find this file here.

Check if my-sda5-etc.gz is present at the root: ls /

Now install the new patch to reset sda5 (same keycontrol 'unzip') and again you should have two rcS files.

The patched boot script formats sda5 only if it finds /my-sda5-etc.gz and also rcS.org. The regular boot script is restored after rebooting and your backup archive is renamed : my-sda5-etc-old.gz

So post the outputs after rebooting one time your nas:

Code: Select all

cat /boot.log
df -h
e2fsck -n /dev/sda5
tune2fs -l /dev/sda5

Note this first boot will take more time as it formats sda5 and runs a fs scan

[peetn]

Hello,

about the sda5.img
The size was: 375 MB (393.764.864 bytes) - see screenshot 1
that seems to be what you expected
sda5 finished at 03h this night, so it took about 14h
that is in line with what i expected, about 25MB/h
the 251 sda2 took about 10h


prepare patch commands
see screenshot 2

install patch
see screenshot 3

--Reboot--
did not take much longer...

Patch results:
* zip file with output files
* also same information in screenshot 4 (is in the zip because too large)


Next steps
I assume I need to restore the backup file first and then retry the upgrade?

[Jocko]

Hi

So all was ok on nas rebooting :thumbup

I assume I need to restore the backup file first and then retry the upgrade?

No
See your boot.log

Found sda5 backup file, we go to format again sda5...
Creating filesystem with 384536 1k blocks and 96256 inodes
Filesystem UUID: 79bedc37-a865-4d02-96b0-cd2a305ad026
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: 0/47 done
Writing inode tables: 0/4728/47 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/47 done

We run now a fs scan...
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 11/96256 files (0.0% non-contiguous), 22438/384536 blocks
Regular boot script is restored...
We restore now sda5 content...
etc/
etc/nas_conf_db.xml
etc/nas_ext_hdd_db.xml
etc/ntp.conf
etc/dropbear/
etc/dropbear/dropbear_rsa_host_key
etc/dropbear/dropbear_rsa_host_key.org
etc/ssl/
etc/ssl/owncert.pem
etc/nas_conf_db.xml.bak
etc/mdadm.conf
etc/nas_conf_db.xmle
etc/install-firmware.log

So the sda5 content is already restored and

The regular boot script is restored after rebooting and your backup archive is renamed : my-sda5-etc-old.gz

you should have now the file my-sda5-etc-old.gz

The next step is to try again to upgrade the firmware. See what happens...

Other point, I sent you a pm about your email address