Thwarted in attempt to install fvdw-sl-console

[Fuddyduddy]

Here it is

Code: Select all

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   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      121601   975153532+  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      121601   973482772+ 83 Linux


Comparing this with the output from the previous time I used this command, I note that this one is completely garbled :o

[fvdw]

this the correct partition table for the fvdw-sl firmware.

Now lets check the individual partitions

do this for partiton sda1, sda2, sda5, sda7 and sda8

Code: Select all

mkdir /sda1
mkdir /sda2
mkdir /sda5
mkdir /sda7
mkdir /sda8
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2
mount /dev/sda5 /sda5
mount /dev/sda7 /sda7
mount /dev/sda8 /sda8


after this perform this command to check partion content (post the output)

Code: Select all

ls -al /sda1

do this also for /sda2, /sda5, /sda7 /sda8

[Fuddyduddy]

this the correct partition table for the fvdw-sl firmware

My mistake (I was looking at the fdisk -l output from before the Lacie partitions were deleted)!

Code: Select all

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):/ # ls -al /sda1
total 0
drwxr-xr-x    2 root     root             0 Jul 17 09:58 .
drwxr-xr-x   17 root     root             0 Jul 17 09:58 ..
root@(none):/ # ls -al /sda2
total 0
drwxr-xr-x    2 root     root             0 Jul 17 09:58 .
drwxr-xr-x   17 root     root             0 Jul 17 09:58 ..
root@(none):/ # ls -al /sda5
total 36
drwxr-xr-x    7 root     root          4096 Jul 13 10:10 .
drwxr-xr-x   17 root     root             0 Jul 17 09:58 ..
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 17 09:58 .
drwxr-xr-x   17 root     root             0 Jul 17 09:58 ..
root@(none):/ # ls -al /sda8
total 0
drwxr-xr-x    2 root     root             0 Jul 17 09:58 .
drwxr-xr-x   17 root     root             0 Jul 17 09:58 ..

[fvdw]

problem is found there is no file system on sda1, sda2, sda7 and sda8

When at home this evening I will post instructions to complete the job manually

[fvdw]

ok start the fvdw-sl console and choose as action write fvdw-sl firmware image to disk
follow the instructions and connect with the telnet client

in step 8 be sure to replace ip-pc in the the propose command by the actual ip address of your pc.
(shown in top right corner of the fvdw-sl console window.)
This command must be entered in the telnet client !
look at the window of the tftp server if the file is really uploaded. Then proceed with step 9 en 10
In step 10 also replace ip-pc by actual ip address of your pc
when you have started the fvdw-sl-image writer script it will ask you to which partitions to write the image
write to sda1, sda2 and sda7

you can check if the writing was ok by repeating the mkdir commands and mounting the partitions as explained in previous posts

PS as you also did not format sda8 we will have to do that as well, but we will do this later.
if writing of the disk image to these three partitions was ok reboot you nwsp2 and see if the web interface comes up.

[Fuddyduddy]

Hi

I have some good news and some bad news.

The good news is that writing the firmware image to disk succeeded - as reported through the telnet terminal anyway. The bad news is that despite that the output from the same commands as before is just as discouraging as before

Code: Select all

root@(none):/ # mkdir /sda1
root@(none):/ # mkdir /sda2
root@(none):/ # mkdir /sda5
mkdir: can't create directory '/sda5': File exists
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):/ # reboot -f


Also, entering reboot -f produces no effect, neither does pressing the power-button (I had to pull out the power-lead again). And, finally, I still can't connect to the NS2's web interface

[fvdw]

and did you look at the tftp server if the the image was transfered ?

did you get when running the script "Uploading firmware files succeeded"

did it as you to write it sda1, sda2 and sda7 ?

In fact this cannot be true, if the writing was successful then there must be a file system on these partitions that can be mounted.
the image file is relative big and you see the progress of upload in the image writer script and the tftp server window. Did you see that ?

ps I told you that after reboot -f the telnet client will become non responsive as it initiate a reboot of the nas...

repeat the process and note carefully the output that you get when running the script

------

when it again fails the mount test then we are going to test the partitions by formatting them, do the following give this command

Code: Select all

tftp -r mke2fs-ext3 -l /sbin/mke2fs-ext3 -g ip-pc
chmod 755 /sbin/mke2fs-ext3

replace ip-pc in this line with actual ip of your pc !

now try to format sda1, sda2 and sda7 (replace sda1 in the command accordingly to sda2 and sda7)

Code: Select all

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

[fvdw]

ps I am off now for a birthday party when I return later this evening I will look at your progress
don't worry we will solve this problem one way or the other ;)

[Fuddyduddy]

Hi

There are some things I'm confused about and I shall have to ask questions about them before I try again.

But now, sorry, I'm going to bed.

Hope you had an enjoyable time at the party!

[Fuddyduddy]

hi

...look at the window of the tftp server if the file is really uploaded. Then proceed with step 9 en 10

I'm afraid that my eyes were mostly glued to the instructions in the fvdw-si console window and my attention divided between that and your previous post. By the time I caught-up with your instruction to note what was appearing in the tftp server it was too late :doh Sorry! But anyway, which window? (there are three tabs). And is there a way I could retrieve the log file instead?

did you get when running the script "Uploading firmware files succeeded"

Yes I did, showing "100%"

did it as you to write it sda1, sda2 and sda7 ?

Yes

the image file is relative big and you see the progress of upload in the image writer script and the tftp server window. Did you see that ?

I'm afraid that's part of what I missed seeing.

ps I told you that after reboot -f the telnet client will become non responsive as it initiate a reboot of the nas...

Yes, when things are working as they should, but isn't it also possible that a reboot never gets initiated by the telnet client?

repeat the process and note carefully the output that you get when running the script

Since I feel braver than I did last night - when I was getting pretty tired - I shall now go ahead and have another go, and will report the results.

Sorry to say that with my lack of experience with this I'm not yet sufficiently quick at switching my attention to the right display at the right time. I will try to do better this time!