Wrong HD temperature read

[fvdw]

do you use a wireless connection between PC and LAN ?

--edit ,
if yes, then try a wired connection, we have seen problems with wireless connections to detect the nwsp2 booting with the fvdw-sl console

[Jocko]

I think yes and in according to this post viewtopic.php?f=26&t=1840, I think that he must have too many network Card set...

[guanabara]

do you use a wireless connection between PC and LAN ?

--edit ,
if yes, then try a wired connection, we have seen problems with wireless connections to detect the nwsp2 booting with the fvdw-sl console

Indeed, i use a wireless connection using a usb adapter.

Will try with wired connection in moments.

I think yes and in according to this post viewtopic.php?f=26&t=1840, I think that he must have too many network Card set...

What do you mean by "too many network card set" ?

Best

[Jocko]

I means that you should disable all NIC except for the wired network card

[guanabara]

I means that you should disable all NIC except for the wired network card

Have just tried with all interfaces disable, except the wired and the result was the same.

Same console message, and unable to telnet after the image upload.

Thanks

EDIT: The process succed. I was able to telnet the NAS. But i cannot have Web access using the NAS ip address.

Any sugestion ?

Thanks

[fvdw]

I means that you should disable all NIC except for the wired network card

Have just tried with all interfaces disable, except the wired and the result was the same.

Same console message, and unable to telnet after the image upload.

Thanks

EDIT: The process succed. I was able to telnet the NAS. But i cannot have Web access using the NAS ip address.

Any sugestion ?

Thanks

so it means you could upload the standalone kernel and login using the telnet client.
of course there is no web access to the nas when running the standalone kernel. for that you need to install the firmware first :whistle

Use the install firmware action in the fvdw-sl console, do not backup the old firmware of lacie, just let it delete it and create the new partition table.
ps all data on the disk will be erased inclusding the original data partition were the lacie firmware stored your files. So back thm up if you still need that data.

---edit

oops I skimmed this post to quickly you only need to write the firmware t0 partition sda1,2 and 7 using the write firmware image action of the console as Jocko suggested in an earlier post
Then your data will be kept save (in sda8)

[guanabara]

I means that you should disable all NIC except for the wired network card

Have just tried with all interfaces disable, except the wired and the result was the same.

Same console message, and unable to telnet after the image upload.

Thanks

EDIT: The process succed. I was able to telnet the NAS. But i cannot have Web access using the NAS ip address.

Any sugestion ?

Thanks

so it means you could upload the standalone kernel and login using the telnet client.
of course there is no web access to the nas when running the standalone kernel. for that you need to install the firmware first :whistle

Use the install firmware action in the fvdw-sl console, do not backup the old firmware of lacie, just let it delete it and create the new partition table.
ps all data on the disk will be erased inclusding the original data partition were the lacie firmware stored your files. So back thm up if you still need that data.

---edit

oops I skimmed this post to quickly you only need to write the firmware t0 partition sda1,2 and 7 using the write firmware image action of the console as Jocko suggested in an earlier post
Then your data will be kept save (in sda8)

In the step 8 of the instructions, th file upload to the disk is giving timeout:
tftp: timeout

Any suggestion ?

Thanks.

EDIT: Typo, installing.

[Jocko]

In the directory where you have installed the fvdw-sl console, you must find a file tftpd32.ini, open it in nodepad and change the value of Timeout

[guanabara]

I was able to upload the image.

However writing to /dev/sda1 fails. sda2 and sda7 is ok.

I tried to ignore this error, but when acessing the nas webpage, i'm not able to see any information, just a single page almost blank.

[Jocko]

So try to get again the telnet access and do this command line

Code: Select all

fdisk -l /dev/sda

---edit---
and of course post here the output !!!

Now I assume that on sda2 and sda7 the firmware image is ok, then do the sequence

Code: Select all

mkdir /tmp/sda7
mount /dev/sda7 /tmp/sda7
cd /tmp/sda7/lacie-boot
rm /tmp/sda7/lacie-boot/sda*boot
touch sda2boot


Reboot the NAS and try to open the web interface