Thwarted in attempt to install fvdw-sl-console

[Fuddyduddy]

Hi

I saw very little in the tftp server window. I did see (very fleetingly) some digits (denoting the image?) followed by "enter 100%". That's about it.

Following the "successful" notification I simulated a reboot by physically pulling-out then (after a brief pause) replacing the power-lead. Then I shut down the fvdw windows and tried to connect to the NS2 via the web interface. Without success.

So I then started-up the fvdw-sl console again and repeated the previous procedure, following the failure of which I carried-out the final step in your last post. Here's the complete telnet client output

Code: Select all

(none) login: root
Password:
root@(none):/ # mount /dev/sda7 sda7
mount: mounting /dev/sda7 on sda7 failed: No such file or directory
root@(none):/ # mkdir /sda1
root@(none):/ # mkdir /sda2
root@(none):/ # mkdir /sda5
root@(none):/ # mkdir /sda7
root@(none):/ # mkdir /sda8
root@(none):/ # mount /dev/sda1 /sda1
mount: mounting /dev/sda1 on /sda1 failed: Invalid argument
root@(none):/ # mount /dev/sda2 /sda2
mount: mounting /dev/sda2 on /sda2 failed: Invalid argument
root@(none):/ # mount /dev/sda5 /sda5
root@(none):/ # mount /dev/sda7 /sda7
mount: mounting /dev/sda7 on /sda7 failed: Invalid argument
root@(none):/ # mount /dev/sda8 /sda8
root@(none):/ # ls -al /sda1
total 0
drwxr-xr-x    2 root     root             0 Jul 18 09:49 .
drwxr-xr-x   17 root     root             0 Jul 18 09:49 ..
root@(none):/ # ls -al /sda2
total 0
drwxr-xr-x    2 root     root             0 Jul 18 09:49 .
drwxr-xr-x   17 root     root             0 Jul 18 09:49 ..
root@(none):/ # ls -al /sda5
total 36
drwxr-xr-x    7 root     root          4096 Jul 18 09:38 .
drwxr-xr-x   17 root     root             0 Jul 18 09:49 ..
drwxr-xr-x    2 root     root          4096 Jul 13 10:10 etc
drwx------    2 root     root         16384 Jan  1  2000 lost+found
drwxr-xr-x    2 root     root          4096 Aug 12  2011 tmp
drwxr-xr-x    3 root     root          4096 Jul 13 10:10 usr
drwxr-xr-x    3 root     root          4096 Jul 13 10:10 var
root@(none):/ # ls -al /sda7
total 0
drwxr-xr-x    2 root     root             0 Jul 18 09:49 .
drwxr-xr-x   17 root     root             0 Jul 18 09:49 ..
root@(none):/ # ls -al /sda8
total 24
drwxr-xr-x    4 root     root          4096 Jul 13 10:18 .
drwxr-xr-x   17 root     root             0 Jul 18 09:49 ..
drwx------    2 root     root         16384 Jul 13 10:17 lost+found
drwxrwxrwx    2 root     root          4096 Jul 13 10:18 public
root@(none):/ # tftp -r mke2fs-ext3 -l /sbin/mke2fs-ext3 -g ip-pc
tftp: bad address 'ip-pc'
root@(none):/ # tftp -r mke2fs-ext3 -l /sbin/mke2fs-ext3 -g 192.168.11.3
mke2fs-ext3          100% |********************************|   261k  0:00:00 ETA
root@(none):/ # chmod 755 /sbin/mke2fs-ext3
root@(none):/ # mke2fs-ext3 -j -m l /dev/sda1
mke2fs-ext3: invalid reserved blocks percent - l
root@(none):/ # mke2fs-ext3 -j -m l /dev/sda2
mke2fs-ext3: invalid reserved blocks percent - l
root@(none):/ # mke2fs-ext3 -j -m l /dev/sda7
mke2fs-ext3: invalid reserved blocks percent - l
root@(none):/ #


edit

PS I saw nothing worth noting in the telnet client window while the image was being written. I just responded to the questions and it went ahead and did its stuff. Was there anything else I should have seen?

[fvdw]

hi Fuddyduddy

in the mke2fs-ext3 command you should use behind -m not the letter "l" but the number 1 (one)

[fvdw]

Hi fuddyduddy any progress ?

ps by the way don't worry, there is nothing that you can break with what we are doing. So relax and enjoy the free teching lessons in linux. You will get it done.

If the mke2fs-ext3 command worked and gave a mountable partition then we can proceed with the next step
which is manually installing the firmware, basically this is doing step by step what the imagewriter script was doing automatic.

First we are going to upload the firmware image manually and write it manually to the disk

To do that start the fvdw-sl console choose action to load and start the standalone kernel and log in with the telnet client.
(at same time the tftp server should start automatically, if doesn't do that start it the fvdw-sl console)

I assume you have installed the fvdw-sl console version 5-3-15-1 from 18 feb 2014 and that you pc has IP 192.168.11.3

first mount partition sda5

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

first remove any old firmware image file

Code: Select all

rm /sda5/firmware.img

This command can give as answer that the file doesn't exist, if this is the case just proceed.
We need to be sure an older version is not present otherwise we will run out of space to store the new one

Now upload the firmware image

Code: Select all

tftp -r nwsp2/xfvdw-sl-15-1-nwsp2-18feb2014.img -l /sda5/firmware.img -g 192.168.11.3

This should take a while because a file of 256 MB must be uploaded.
After uploading you can check if it there by performing the command

Code: Select all

ls -al /sda5/firmware.img

if is there write it to sda1

Code: Select all

dd if=/sda5/firmware.img of=/dev/sda1

write it to sda2

Code: Select all

dd if=/sda5/firmware.img of=/dev/sda2

write it to sda7

Code: Select all

dd if=/sda5/firmware.img of=/dev/sda7

all three commands will take a while to complete when they finish they will give info on how much records have been written, post this output, it should be same for all three commands.
Assuming everything is ok remove the firmware.img from sda5

Code: Select all

rm /sda5/firmware.img

and umount sda5

Code: Select all

umount /sda5

almost done to be sure that also the kernel has been written succefully to sda6 we will repeat that step also.
Upload the kernel

Code: Select all

tftp -r nwsp2/UIMAGE-395-NWSP2CL-199 -l /uimage -g 192.168.11.3

(be sure to use capital letters as shown as Linux file names are case sensistive)
Check that file is uploade by using command

Code: Select all

ls -al /uimage

write to sda6

Code: Select all

dd if=/uimage of=/dev/sda6

Last step we need to forma sda8 because also that was not done
Upload the the program to format partitions

Code: Select all

tftp -r mke2fs-ext3 -l /sbin/mke2fs-ext3 -g 192.168.11.3

-edit: make it executable

Code: Select all

chmod 755 /sbin/mke2fs-ext3

Now format partition 8

Code: Select all

mke2fs-ext3 -j -m 1 /dev/sda8

This will take some time to complete as it needs to format 1 TB
When it is finished we create on folder on it
First mount it

Code: Select all

mkdir /sda8
mount /dev/sda8 /sda8

create the folder

Code: Select all

mkdir /sda8/public

Umount sda8

Code: Select all

umount /sda8

done reboot the nwsp by using

Code: Select all

reboot -f

now the magic should take place and you should be able to connect to the web interface

success ;)

[Fuddyduddy]

Hi fuddyduddy any progress ?

ps by the way don't worry, there is nothing that you can break with what we are doing. So relax and enjoy the free teching lessons in linux. You will get it done.

If the mke2fs-ext3 command worked and gave a mountable partition...

Hi

It did, I think. Here's the output

Code: Select all

(none) login: root
Password:
Login incorrect
(none) login: root
Password:
root@(none):/ # tftp -r mke2fs-ext3 -l /sbin/mke2fs-ext3 -g 192.168.11.3
mke2fs-ext3          100% |**************************************|   261k  0:00:00 ETA
root@(none):/ # chmod 755 /sbin/mke2fs-ext3
root@(none):/ # mke2fs-ext3 -j -m 1 /dev/sda1
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
128520 inodes, 514080 blocks
5140 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: done                           
Creating journal (8192 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.
root@(none):/ # mke2fs-ext3 -j -m 1 /dev/sda2
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
128520 inodes, 514080 blocks
5140 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

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

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
root@(none):/ # mke2fs-ext3 -j -m 1 /dev/sda7
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
128520 inodes, 514080 blocks
5140 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

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

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
root@(none):/ #


...then we can proceed with the next step
which is manually installing the firmware, basically this is doing step by step what the imagewriter script was doing automatic.
....
now the magic should take place and you should be able to connect to the web interface

success ;)

Although it's not late (2115 here) I'm getting chivied by the wife, plus I've had more than enough for today of staring at my monitor and bashing my keyboard, so I think I'll defer the pleasure of administering the coup de grace (hopefully) 'til tomorrow if you don't mind.

(I was at a birthday-party too, one day before you. It was my own, my 79th).

[fvdw]

congratulation with you birthday ...79 years is a respectable age. :applause

No problem to do the rest tomorrow i can wait.

[Fuddyduddy]

Good morning

first remove any old firmware image file
Code:
rm /sda5/firmware.img

Problem :(

Code: Select all

(none) login: root
Password:
root@(none):/ # mkdir /sda5
root@(none):/ # mount /dev/sda5 /sda5
root@(none):/ # rm /sda5/firmware.img
rm: can't remove '/sda5/firmware.img': No such file or directory
root@(none):/ #

EDIT
Sorry, please ignore! (I should have read on :oops:

[Fuddyduddy]

all three commands will take a while to complete when they finish they will give info on how much records have been written, post this output, it should be same for all three commands.

Here's the output

Code: Select all

root@(none):/ # tftp -r nwsp2/xfvdw-sl-15-1-nwsp2-18feb2014.img -l /sda5/firmware.img -g
192.168.11.3
root@(none):/ # ls -al /sda5/firmware.img
-rw-r--r--    1 root     root             0 Jul 19 08:17 /sda5/firmware.img
root@(none):/ # dd if=/sda5/firmware.img of=/dev/sda1
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000356 seconds, 0B/s
root@(none):/ # dd if=/sda5/firmware.img of=/dev/sda2
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000268 seconds, 0B/s
root@(none):/ # dd if=/sda5/firmware.img of=/dev/sda7
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000268 seconds, 0B/s
root@(none):/ #


EDIT
Does this only mean I didn't wait long enough (or is the problem a deeper one)?

[fvdw]

Hi Fuddyduddy,

problem is clear there is no firmware image transfered from your pc to the nas. (0 bytes transferred)
That means the file that we tried to upload (xfvdw-sl-15-1-nwsp2-18feb2014.img) is not present in the directory were we tried to upload it from (nwsp2)

So we need to check your setup of the fvdw-sl-console

So how did you install the fvdw-sl-console ?
In the folder on your pc were you unpacked the fvdw-sl console zip file there must be a folder with name "tftp" (without the quotes)
In that folder there should be another folder with name "nwsp2" (without the quotes) in there should the file with name we used( xfvdw-sl-15-1-nwsp2-18feb2014.img). Please specify the content of this folder on your pc.

ps did you change the default folder to be used by the tftp server ? (In the main window of the fvdw-sl console)

[Fuddyduddy]

In the folder on your pc were you unpacked the fvdw-sl console zip file there must be a folder with name "tftp"...

Yes

...In that folder there should be another folder with name "nwsp2"

Yes

...in there should the file with name we used( xfvdw-sl-15-1-nwsp2-18feb2014.img)

Yes.

ps did you change the default folder to be used by the tftp server ? (In the main window of the fvdw-sl console)

Not knowingly, no. The file-path for the folder being used is shown in the console window as <F:\Apps\LaCie\fvdw-sl\installer\tftp> (without the '< >').

I recall that that was the folder to which I pointed the installer during the "question and answer" part of the installation. Was it wrong?
EDIT
HANG ON! The file-path is incomplete, isn't it! Shouldn't it be <F:\Apps\LaCie\fvdw-sl\installer\tftp\nwsp2>?

[fvdw]

in which folder of your pc is this file present fvdw-sl-console.exe ?

is it in F:\Apps\LaCie\fvdw-sl\installer ?