plugout.net

Hi!

I've been happily using fvdw-sl for the last few weeks. It feels good to be in control of my own hardware :) Thanks for your effort.

This said, yesterday i had a local power failure and when everything was back online, my nwsp2cl was invisible. When i went to check it upstairs, i found it rebooting every couple of minutes and my router didn't lease an IP anymore.

After some efforts to reboot / reset it, I opened it and made a backup of the data. I figured something happened to my partition table and the easiest sollution seemed to start fresh again. So i used fdisk to put a fresh empty MBR table on the disk.

After this, the drive obviously reacted differently, it's no longer rebooting, so i don't think that was a power issue. When using the console software, i tried all options. U-boot recognizes the drive and uploads the standalone kernel (yes, i made shure i selected the standalone nwsp2cl one). But when telnet client opens i get a time out. I understand that if the kernel is loaded correctly it should also get a DHCP lease, and that doesn't happen. My router sees a static 192.168.1.252 though.

This is within my subnet mask (all computers have a 192.168.1.x address)

In my last hopeless attempt to fix this, i tried to flash the kernel. This was successfull, but no change so far.

What can i try next? Thank you for you effort!

(btw, after telnet fails, i retried several times. and when i use uboot after that, i don't have to reboot the nas, i just finds it automatically)

kuzanagi88 wrote: I figured something happened to my partition table and the easiest sollution seemed to start fresh again. So i used fdisk to put a fresh empty MBR table on the disk.

:disapprove Before doing this drastic command, you might post here. There are other tools to check your partition table!
But at least you backup your data

kuzanagi88 wrote:This said, yesterday i had a local power failure and when everything was back online, my nwsp2cl was invisible. When i went to check it upstairs, i found it rebooting every couple of minutes and my router didn't lease an IP anymore.

I remember that this was already happened to a member and the issue was the feature "Temperature Guard Hard Disk" with the threshold 50°C that was too low.

Anyhow you need now to do again a first install with the fvdw-sl console.

kuzanagi88 wrote:But when telnet client opens i get a time out.

Up to now, the members that had this timeout issue, is a problem on the laptop side.

So:
- Don't use wireless connexion,
- Disable all firewall (custom firewall and Defender if this one is available after disabling your firewall) or add some rules for nc and fvdw-sl console (see also if your anti-virus doesn't have a firewall feature)
- Keep enable one network interface card (NIC)

Hi Jocko, thanks for your reply.

All very usefull information. And your right, it was a bit drastic. But I still have my data, so nothing lost, lots to learn, which will be fun.

I'm going to try with another computer. I was using a windows 7 desktop with disabled firewall. I will try booting windows 7 on a laptop and connect that with a cable. I will post the results back here in a moment.

Still no luck. I disabled the wifi, and the kernel seems to be loading in uboot.

If i ping 192.168.1.252, i get destination host unreachable, so no time out there.

The telnet client still times out.

Btw the led on the nas is flashing red / blue very fast after telnet time out.

Did you start the nas only when in the window pops up there is a prompt that it waits for u-boot?

yes, but i also tried without rebooting the nas, the uboot still loads then btw.

Here are my steps:

choose install fvdw-sl firmware
wait for uboot message
plug in nas power adapter
uboot gets recognized and I see the tftp upload
the last message in uboot is:
starting kernel.
i hear some hard drive movement form this moment.
when telnet opens, it just sits there connecting.
when it times out, the led starts flashing red/blue

Any other ideas?

I assume you loaded the "standalone" kernel.
If the disk has a problem it might take longer to load and telnet client times out to early, so before the kernel is fully loaded.

When it mentions time out, keep it open and try to connect again after a minute or so by using the connect button in the telnet client (use the 192.68.1.252 ip)

ps the red/bleu flashing indicates that it cannot recognize your disk probably by a failure in the partition table, or not finding a valid partition table at all

hi fvdw, thanks for your response. I've tried waiting up to 15 minutes and no result.

The not recognizing my disk must be because it has no partitions? Should i add one or more partitions? And i flashed the GPT kernel, should i partition the drive to GPT? Or is it also compatible with MBR?

thank you for your time

kuzanagi88 wrote:And i flashed the GPT kernel, should i partition the drive to GPT? Or is it also compatible with MBR?

When you flash uboot, this one is able to use both partition table types.

But did you check if you have really a classic nwsp2 or a Lite nwsp2 ?

See viewtopic.php?f=11&t=213

ok, that's clear.

i double checked, and i indeed the the classic, not the lite.

i'm going to try without my router now, just laptop - nas with a lan cable and static ip's.