fvdw-sl-console for ms windows install without removing HDD

[fvdw]

there is one thing that I did not try myself and that is using the fvdw-sl-console with the old u-boot original version. I alwus used my newer compiled version. I do not believe this is the problem because I started several time the nwsp2 with the ld u-boot using tftpd. But I will put it back in flash memory and see what happens.
9 red flashes is for sure not what the response should be. It indicates that your u-boot version is behaving different. :scratch

[fvdw]

:punk The problem is found it is the original old boot loader that is the problem. I now get the same behavior !

Thanks for not letting this go, need now to find a way to find out why the old boot loader has this problem

I will be back with a new version soon !!

[fvdw]

check your ppm inbox I have sent you an update that should solve the problem with this version of u-boot.
It needs some extra response.

Can you test if it works ?

[NasaMan]

Hi Wow :hail it works until the program wants to make a backup. This fails. For unique id I choose sda as it suggested. but the backup process is aborted to prevent data loss.

EDIT: I think this is because I put the program in C:\fvdw and the telnet client has no permission to write there. Can I simply abort the process?

[fvdw]

glad to hear it is working now and thks again for not giving up and helping to get this bug resolved :punk

yes you can abort the process. I think the reason is not the write permission, the installer script tries to write the images temporarily to sda9 and then transfer them to the windows pc via tftp. I do not have an original disk anymore so I guessed sda9 would be big enough but i could test it.
At least it succeeds to mount sda9 so it is present. It fist tries to copy sda6, thats a small partition (only 8 MB and should fit on sda9) Is there not one file transferred. it should back up sda6, 7 and 8

To see what is going on we are going to try to backup the partition manual using the telnet client

first e need a mountpoint (probably already present as made by the script)

Code: Select all

mkdir sda9

Mount sda9

Code: Select all

mount /dev/sda9 /sda9

copy the image of sda6

Code: Select all

dd if=/dev/sda6 of=/sda9/nwsp2-partition6.img

[NasaMan]

sda9 exists but mount /dev/sda9 /sda9 brings mounting /dev/sda9 on /sda9 Failed: no such file or directory

[fvdw]

:scratch

to see if it exist you can type

Code: Select all

ls -al

and check if it is not already mount (but then the error message should be that it is busy)

Code: Select all

mount

[fvdw]

the problem could be that sda9 is not formatted
you could format it using this command

Code: Select all

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

and then try if it mounts

[NasaMan]

The installer says can not mount partition 9, ls -al shows that there is sda 9 in the root directory (where bin, dev, etc, usr, var are) mount brings

Code: Select all

 rootfs on / type rootfs (rw)
None on /proc type proc (rw, relatime)
None on /sys type stags (re,relatime)
None on /dev/pts type devpts (rw,relatime,mode=600)

could it be something with time? My system time was totally wrong on startup because the laptop bios battery its empty...

[fvdw]

no can be nothing with time
from what I find on the internet the stock disk should have a sda9 partition
You can check with

Code: Select all

fdisk -l /dev/sda

If it exist try to format it as described in previous post, there is nothing to loose as we can delete sda9 and restore it
Its only used for firmware upgrades of lacie a s far as I know