ReasyNAS looses connectivity ....

[hegnerd]

I have a ReadyNas NV+. I performed a factory reset using the pin hole slot on the back of the device. Now when the device boots i can ping it momentarily then the message "Requesting IP ...." appears in the LCD display and connectivity is lost. I understood from the documentation that the factory default for the device is 192.168.168.168/24 and that DHCP is not active.

Why is the device assuming DHCP is active during a factory reset ?

[mdgm]

By default it will attempt to receive an IP address via DHCP. If it can't receive an IP address then it will use the I.P. address you mentioned.

Does it still show "Requesting IP ...." on the LCD?

[hegnerd]

Yes it still says "Requesting IP ..."

I booted it with no cable plugged into the NIC and it still says it.

Any ideas ??

[mdgm]

Do you remember what version of RAIDiator the unit was running?

What brand and model disks do you have installed?

Was it working fine before doing the factory reset?

[hegnerd]

Radiator v 4.1.6

WD20EARS

Yes

[mdgm]

You shouldn't be using anything older than 4.1.7 with the WD20EARS. A factory default should be done after updating to 4.1.7+.

Using 4.1.6 would explain getting ATA errors (which you mentioned getting in another thread). There's a compatibility issue with 4.1.6 and prior that leads to getting 6 ATA errors on each reboot. Without a compatibility issue like this normally ATA errors would be a sign of impending disk failure.

Do you have any other disks you could try to boot the NAS with and update the firmware?

If not, could you try doing a factory default with just one disk installed, updating to 4.1.7 or later then powering down, putting all disks in and doing another factory default.

[hegnerd]

How is using just one disk going to change the fact that the device thinks it setup to use DHCP?

Is there no other way to get into the device?

[mdgm]

It won't change that but as the disks have compatibility issues it's possible that using a single disk will allow it to pickup an IP address (or realise it hasn't found one and go to the I.P. address you mentioned).

If that doesn't work I do have other suggestions at least one of which should resolve the problem but best to try this first.

[hegnerd]

OK, it's late enough at night that I hooked the NAS to my production network and allowed it to obtain an IP address.

Updated RAIDiator to 4.1.9.

I'll see if I can change the IP address.

[mdgm]

After your successful update from 4.1.6 to newer firmware please do a factory default (wipes all data, settings, everything). Without 4k sector partition alignment you will likely have poor write performance with your disks. Do note there is an ownership issue on 4.1.9 so you may prefer to run 4.1.8 or 4.1.10 beta.

[hegnerd]

Great ..... what is an "ownership issue"?

[hegnerd]

I'll try to downgrade to 4.1.8.

Is there a way to 4k sector partition alignment with 4.1.8? If not will we be stuck with poor write performance?

[mdgm]

An issue where ownership of files is transferred to the wrong user which would prevent access to read files or make changes. Data would still be left intact.

You just need to do a factory default after updating successfully to RAIDiator 4.1.7 or newer. Can do it on any of 4.1.7, 4.1.8, 4.1.9 etc (personally I wouldn't do it on 4.1.9 due to the ownership issue mentioned above).