Writing problem while updating 16 from 15.3

[josejad]

Hi:

I've updated from 15.3 but I get an error (sorry, I didn't copy it), something like: "problem with dd command copying the files"

Now, when I log my drive in, I get no translated menus and nothing inside.
I attach a capture.

https://drive.google.com/file/d/0BwUsn6 ... sp=sharing

Thanks in advance.

[Jocko]

Do you have a shell access?
If yes, in /lacie-boot delete the file sdaxboot and create another sda1boot if the original was sda2boot and in the other case create a new file sda1boot

If you dont have a shell access, use the fdvwsl console to get a telnet access.
The folder lacie-boot is on the partition sda7.
After mounting it you can do the swap sdaxboot

[josejad]

Hi:

Thanks for the quick reply. I have ssh access. I have a sda1boot file, I can delete but, how shoud I create the new one? A void txt file?

I have tried deleting sda1boot, create a new one (touch sda1boot) and rebooting, but nothing have changed.

Thanks again

[fvdw]

do not recreated it. Replace it by sda2boot. That should load the second partition with the firmnware which can be used to install once again 16-0

[Jocko]

Hi josejad,

Before upgrading again your nas, could you post your partition table.

In putty do

Code: Select all

fdisk -l /dev/sda

[josejad]

Here is my partition table

Device Boot Start End Blocks Id System
/dev/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 243201 1951905532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 243201 1950234772+ 83 Linux

[josejad]

There is no sda2boot file in the lacie-boot directory, but there is a sda7-tmp dir in / , I don't know if it is normal

root@fvdwsl-base:/ # ls -a
. bin boot.log direct-usb lib mail nowhere root sda7-tmp sys var
.. bin_cab clunc etc linuxrc .mldonkey opt rw_fs share tmp
.ash_history boot dev lacie-boot lost+found mnt proc sbin .ssh usr

[Jocko]

Your partition table seems ok.

sda7-tmp is a folder for another purpose.

if there is no sdaxboot file in /lacie-boot that means that the main partition is corrupted (sda7) :scratch

if you had used the fvdw-sl console to install the firmware, you should be able to use sda1 or sda2 to load the firmware.

Then check if these partitions are clean, in Putty do

Code: Select all

cd /tmp
mkdir mpt
mount /dev/sda1 /tmp/mpt
ls -l /tmp/mpt

if the output is

Code: Select all

drwxr-xr-x   2 root root  4096 Apr  3  2014 bin
drwxr-xr-x   2 root root  4096 Apr  3  2014 bin_cab
drwxr-xr-x   2 root root  4096 Sep 25  2013 boot
drwxrwxrwx   2 root root  4096 Apr  3  2014 clunc
drwxr-xr-x   3 root root 12288 Apr  3  2014 dev
drwxrwxrwx  15 root root  4096 Mar 13  2014 etc
drwxr-xr-x   4 root root  4096 Mar 13  2014 lib
lrwxrwxrwx   1 root root    11 Apr  3  2014 linuxrc -> bin/busybox
drwx------   2 root root 16384 Jan  3  2008 lost+found
drwxr-xr-x   3 root root  4096 Apr  3  2014 mail
drwxr-xr-x   2 root root  4096 Aug 27  2008 nowhere
drwxr-xr-x   7 root root  4096 Apr  3  2014 opt
drwxrwxrwx   2 root root  4096 Mar  5  2011 proc
drwxr-xr-x   2 root root  4096 Jan  3  2008 root
drwxr-xr-x   2 root root  4096 Apr  3  2014 sbin
drwxrwxrwx   2 root root  4096 Mar  5  2011 share
drwxrwxrwx   2 root root  4096 Mar  5  2011 sys
drwxrwxrwx  22 root root  4096 Apr  3  2014 usr
drwxr-xr-x   2 root root  4096 Mar  9  2012 var

then sda1 is clean and can be used.

Note: If not repeat the same sequence but with /dev/sda2

if sda1 is clean, create a new file in /lacie-boot

Code: Select all

touch /lacie-boot/sda1boot

[josejad]

Hi again:

I think everything seems to be fine:

Code: Select all

root@fvdwsl-base:/ # cd tmp
root@fvdwsl-base:/tmp # ls
btsync_dumps  etc  mnt  usr  var
root@fvdwsl-base:/tmp # mkdir mpt
root@fvdwsl-base:/tmp # mount /dev/sda1 /tmp/mpt
root@fvdwsl-base:/tmp # ls -l /tmp/mpt
total 108
drwxr-xr-x   2 root root  4096 2014-12-30 18:56 bin
drwxr-xr-x   2 root root  4096 2014-12-30 18:56 bin_cab
drwxr-xr-x   2 root root  4096 2013-09-25 22:49 boot
-rw-r--r--   1 root root  2732 2015-01-03 15:52 boot.log
drwxrwxrwx   2 root root  4096 2014-12-30 18:56 clunc
drwxr-xr-x   6 root root 12288 2014-12-31 19:09 dev
lrwxrwxrwx   1 root root    11 2015-01-03 15:52 direct-usb -> /share/1000
drwxrwxrwx  18 root root  4096 2015-01-03 15:52 etc
drwxrwxrwx   2 root root  4096 2015-01-03 15:51 lacie-boot
drwxr-xr-x   4 root root  4096 2014-11-22 13:13 lib
lrwxrwxrwx   1 root root    11 2014-12-30 18:56 linuxrc -> bin/busybox
drwx------   2 root root 16384 2008-01-03 22:21 lost+found
drwxr-xr-x   3 root root  4096 2014-12-30 18:56 mail
lrwxrwxrwx   1 root root    14 2015-01-03 15:51 mnt -> /rw_fs/tmp/mnt
drwxr-xr-x   2 root root  4096 2008-08-27 23:46 nowhere
drwxr-xr-x   7 root root  4096 2014-12-30 18:56 opt
drwxrwxrwx   2 root root  4096 2011-03-05 11:08 proc
drwxr-xr-x   2 root root  4096 2008-01-03 21:06 root
drwxr-xr-x   2 root root  4096 2014-12-31 19:09 rw_fs
drwxr-xr-x   2 root root  4096 2015-01-03 15:51 sbin
drwxr-xr-x   2 root root  4096 2014-12-31 19:09 sda7-tmp
drwxrwxrwx   3 root root  4096 2014-12-31 19:09 share
drwxrwxrwx   2 root root  4096 2014-12-30 10:47 sys
lrwxrwxrwx   1 root root    10 2015-01-03 15:51 tmp -> /rw_fs/tmp
drwxr-xr-x  22 root root  4096 2015-01-03 15:51 usr
drwxr-xr-x   4 root root  4096 2015-01-03 15:52 var

I've created the sdaxboot file:

Code: Select all

touch /lacie-boot/sda1boot

and then reboot, but nothing change, boot the 16 firmware.
I've tried with sda1 and sda2 partitions.

[fvdw]

please post the output of the command (log in via ssh and give this command)

Code: Select all

mount

and please describe once more what the problem is you experience