Upgrade failed and gone to hell

[firwareslut]

THe command isn't found and I don't find it in the bin folder.

It's probably a bad disk....I've had a lot of trouble mounting the partitions in linux when i took the disk out. Luckily i managed to backup my public folder.

I will test another disk.

[Jocko]

Hi firwareslut,

I started up the console again and tried to mount sda1 or sda2 to get a look at the log file and i get this

mount: mounting /dev/sda1 on /sda1 failed: Function not implemented

Be careful, with the last fvdw-sl console only sda7 partition is initialized. The partition sda1 and sda2 are created but not formatted (step done now when you upgrade the firmware). So any mount attempt on these partition fails. After a fresh install, the partition used is only sda7.

When I mount /sda7 there is no boot.log file in the root.

But if you do not have a boot.log here then you may have a disk issue like you suggest.

[firwareslut]

I installed a new disk and everything worked first time. I must have bad sectors on that drive. It's several years old now so it's maybe not a big surprise. Western Digital 2TB green! Luckily only the firmware partitions had problems.

Thanks for the help.

I am donating again for the support. There's been a lot of work done here since I was last active!

[firwareslut]

So, after the initial install I ran the web update to 18.2 and ran into trouble again. Once, again the disk won't book.

sda1 is empty other than lacie-boot folder

sda7 has a boot.log and it says this :


start boot log
is a physical machine
detect and set platform
nwsp2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 file system...
else loop1 finished
rcS finished


Here is a copy of the post upgrade log

First post upgrade setup routines
- iface [ OK ]
- timezone [ OK ]
- phptimezone [ OK ]
- opcache [ OK ]
- update-ldsocache [ OK ]
- init-raid [ OK ]
- user-update [ OK ]
- afp-share-update [ OK ]
- update-job-servers [ OK ]
- update-usb-disks [ OK ]
- webconsole [ OK ]
- root-inittab [ OK ]

[firwareslut]

In the meantime I have written the firmware again from the console and have gone back to 18.1

[Jocko]

Hi

:scratch

As you reinstall the fw we can not find where was the issue, but...

So, after the initial install I ran the web update to 18.2 and ran into trouble again. Once, again the disk won't book.
sda1 is empty other than lacie-boot folder

To have an empty sda1, maybe it is this bug:

known bugs fvdw-sl-18.1

web-interface
Affected device: All nas
Affected version: fvdw-sl-18.0 and 18.1

feature: firmware upgrade
Bug: firmware may be corrupted with some inappropriate actions from the web-interface (do a page rollback or reload the firmware update menu whereas the upgrade script is still running).

So after starting the step2 or when the firmware waits you for running step3, you must not, for example, reload the menu (or open a new session on the another browser window)

and what was the trouble ???

[firwareslut]

Ok, so I did the upgrade again and this time it worked. I don't recognise that step 3 appeared last time so maybe something went wrong in the browser. It's possible I opened a new tab away from the upgrade page.

[Jocko]

Hi

So the issue is fixed.

Note: I advise to install this patch for version 18.2 https://plugout.net/viewtopic.php?f=7&t=3149