Unable to write firmware

[aolmaster]

So the partition table is ok
and what fvdw-sl console version do you use ? (the last version 6.0)

yes 6.0

[Jocko]

With this version you should find on sda5 a log of your previous install attempt.

Then still on the telnet window do:

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

post the output of

Code: Select all

ls /sda5
cat /sda5/installer.log

[aolmaster]

With this version you should find on sda5 a log of your previous install attempt.

Then still on the telnet window do:

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

post the output of

Code: Select all

ls /sda5
cat /sda5/installer.log

Here it is

Code: Select all

root@fvdw-sta-kirkwood:/ # mkdir /sda5
root@fvdw-sta-kirkwood:/ # mount /dev/sda5 /sda5
root@fvdw-sta-kirkwood:/ # ls /sda5
fvdw-sl-16-1-base-9feb16.img  installer.log                 lost+found
root@fvdw-sta-kirkwood:/ # cat /sda5/installer.log
fvdw-sl-installer log
tftpd ip address 192.168.0.1
getting required programs from tftp server 192.168.0.1
Dialog installed
xterm installed
mke2fs-ext3 present
gdisk present
Start fvdw-sl firmware installer version 3.0.0

selected nas type cloudbox platform kirkwood
selected disk /dev/sda
gpt support bootloader selected yes
selected partion table type gpt
Deleting old gpt partiton table
partitions found before GPTdeleting partition table = \n
del = w\nY\n\n
partitions found after delete GPT partition table = \n
deleting GPT partition succeeded, trying to delete protective ms-dos table\n

The number of cylinders for this disk is set to 242251.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Selected partition 1

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
deleting ms-dos protective partition succeeded\n
create new partiton table
create new GPT partiton table
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: present

Found valid MBR and GPT. Which do you want to use?
 1 - MBR
 2 - GPT
 3 - Create blank GPT

Your answer: Using GPT and creating fresh protective MBR.

Command (? for help):
Expert command (? for help): Enter the sector alignment value (1-65536, default = 2048):
Expert command (? for help):
Command (? for help): Partition number (1-128, default 1): First sector (34-3907029134, default = 4096) or {+-}size{KMGTP}: Last sector (4096-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (2-128, default 2): First sector (34-3907029134, default = 1052672) or {+-}size{KMGTP}: Last sector (1052672-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (3-128, default 3): First sector (34-3907029134, default = 2101248) or {+-}size{KMGTP}: Last sector (2101248-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux swap'

Command (? for help): Partition number (4-128, default 4): First sector (34-3907029134, default = 3149824) or {+-}size{KMGTP}: Last sector (3149824-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (5-128, default 5): First sector (34-3907029134, default = 3166208) or {+-}size{KMGTP}: Last sector (3166208-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (6-128, default 6): First sector (34-3907029134, default = 4739072) or {+-}size{KMGTP}: Last sector (4739072-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (7-128, default 7): First sector (34-3907029134, default = 4755456) or {+-}size{KMGTP}: Last sector (4755456-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (8-128, default 8): First sector (34-3907029134, default = 5804032) or {+-}size{KMGTP}: Last sector (5804032-3907029134, default = 3907029134) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help):
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sda.
The operation has completed successfully.
creating GPT partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
49152 inodes, 196608 blocks
1966 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=201326592
6 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840

Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
9445+1 records in
9445+1 records out
4835944 bytes (4.6MB) copied, 12.712626 seconds, 371.5KB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
Unpacking firmware image from archive
firmware disk image extracted succesfully\n
Adapting firmware image for cloudbox\n
Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image
mounting firmware image succeeded
./
./etc/
./etc/init.d/
./etc/init.d/insert-modules
./etc/platform
./lib/
./lib/modules/
./lib/modules/3.14.2/
./lib/modules/3.14.2/videobuf-core.ko
./lib/modules/3.14.2/ehci-pci.ko
./lib/modules/3.14.2/usb_f_mass_storage.ko
./lib/modules/3.14.2/readme.txt
./lib/modules/3.14.2/usblp.ko
./lib/modules/3.14.2/g_ether.ko
./lib/modules/3.14.2/ftdi-elan.ko
./lib/modules/3.14.2/iscsi_tcp.ko
./lib/modules/3.14.2/ftdi_sio.ko
./lib/modules/3.14.2/usb-storage.ko
./lib/modules/3.14.2/sg.ko
./lib/modules/3.14.2/pl2303.ko
./lib/modules/3.14.2/iscsi_trgt.ko
./lib/modules/3.14.2/cdrom.ko
./lib/modules/3.14.2/libiscsi.ko
./lib/modules/3.14.2/libcomposite.ko
./lib/modules/3.14.2/ehci-orion.ko
./lib/modules/3.14.2/configfs.ko
./lib/modules/3.14.2/scsi_transport_iscsi.ko
./lib/modules/3.14.2/g_mass_storage.ko
./lib/modules/3.14.2/ehci-hcd.ko
./lib/modules/3.14.2/usbserial.ko
./lib/modules/3.14.2/zr364xx.ko
./lib/modules/3.14.2/bonding.ko
./lib/modules/3.14.2/videobuf-vmalloc.ko
./lib/modules/3.14.2/libiscsi_tcp.ko
./lib/modules/3.14.2/btrfs.ko
./lib/modules/3.14.2/r8712u.ko
./lib/modules/3.14.2/pktgen.ko
./lib/modules/3.14.2/udc-core.ko
./lib/modules/3.14.2/mv_udc.ko
./lib/modules/3.14.2/modules.dep.bb
./lib/modules/3.14.2/wire.ko
correcting firmware image for cloudbox succeeded\n
Writing firmware to partion 7
dd: writing '/dev/sda7': Input/output error
86737+0 records in
86736+0 records out
44408832 bytes (42.4MB) copied, 145.620504 seconds, 297.8KB/s
writing firmware file to partition 7 failed

root@fvdw-sta-kirkwood:/ #

[Jocko]

Maybe I understand what happens.

Can you post

Code: Select all

cat /proc/partitions
ls -l /dev/sda*

[aolmaster]

Maybe I understand what happens.

Can you post

Code: Select all

cat /proc/partitions
ls -l /dev/sda*

Nice to hear that...

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 1953514584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8 1950612551 sda8
root@fvdw-sta-kirkwood:/ # ls -l /dev/sda*
brw-rw-rw-    1 root     root        8,   0 Aug 20 14:38 /dev/sda
brw-rw-rw-    1 root     root        8,   1 Aug 20 14:38 /dev/sda1
brw-rw-rw-    1 root     root        8,  10 Aug 20 14:37 /dev/sda10
brw-rw-rw-    1 root     root        8,  11 Aug 20 14:37 /dev/sda11
brw-rw-rw-    1 root     root        8,  12 Aug 20 14:37 /dev/sda12
brw-rw-rw-    1 root     root        8,  13 Aug 20 14:37 /dev/sda13
brw-rw-rw-    1 root     root        8,  14 Aug 20 14:37 /dev/sda14
brw-rw-rw-    1 root     root        8,  15 Aug 20 14:37 /dev/sda15
brw-rw-rw-    1 root     root        8,   2 Aug 20 14:38 /dev/sda2
brw-rw-rw-    1 root     root        8,   3 Aug 20 14:38 /dev/sda3
brw-rw-rw-    1 root     root        8,   4 Aug 20 14:38 /dev/sda4
brw-rw-rw-    1 root     root        8,   5 Aug 20 14:38 /dev/sda5
brw-rw-rw-    1 root     root        8,   6 Aug 20 14:38 /dev/sda6
brw-rw-rw-    1 root     root        8,   7 Aug 20 14:38 /dev/sda7
brw-rw-rw-    1 root     root        8,   8 Aug 20 14:38 /dev/sda8
brw-rw-rw-    1 root     root        8,   9 Aug 20 14:37 /dev/sda9
root@fvdw-sta-kirkwood:/ #

[Jocko]

Nope, it is ok on this side. :scratch

So try to reproduce the error:

Code: Select all

ls -l /sda5/fvdw-sl-16-1-base-9feb16.img
dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda7

if it fails try on another partition (sda1 or sda2)

Code: Select all

dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda1

[aolmaster]

Nope, it is ok on this side. :scratch

So try to reproduce the error:

Code: Select all

ls -l /sda5/fvdw-sl-16-1-base-9feb16.img
dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda7

if it fails try on another partition (sda1 or sda2)

Code: Select all

dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda1

Ok it failed on sda7, but sda1 was sucessfull,

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -l /sda5/fvdw-sl-16-1-base-9feb16.img
-rw-r--r--    1 root     root     262144000 Jan  1  2000 /sda5/fvdw-sl-16-1-base-9feb16.img
root@fvdw-sta-kirkwood:/ # dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda7
dd: writing '/dev/sda7': Input/output error
86737+0 records in
86736+0 records out
44408832 bytes (42.4MB) copied, 121.190998 seconds, 357.8KB/s
root@fvdw-sta-kirkwood:/ # dd if=/sda5/fvdw-sl-16-1-base-9feb16.img of=/dev/sda1
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 568.302911 seconds, 450.5KB/s

[Jocko]

Note: please thank to use the BBcode 'code' when you copy some data on your post. it is more easy to read them!

So there is some thing wrong on sda7.

before installing fvdw-sl firmware, did you have issues with lacie firmware and/or is it a new disk ?

[aolmaster]

Note: please thank to use the BBcode 'code' when you copy some data on your post. it is more easy to read them!

So there is some thing wrong on sda7.

before installing fvdw-sl firmware, did you have issues with lacie firmware and/or is it a new disk ?

Ok will use th BBcode, yes i had problems with the lacie firm, the drive was not showing on network and the blue led was keep flashing, then i decided to format the disk and start from scratch, actually i did not format it i deleted all the partitions.

[Jocko]

So maybe you have a bad disk (at least it should have some bad blocks)

You should extract it and from a laptop you may use manufactor's tool to check its health (SMART tool)