No Frontview after 4.1.8 upgrade on 1000S

[VanTechs]

I upgraded my ReadyNAS 1000S to 4.1.8 and now I no longer have Frontview; I can still access my shared folder. Also Radar detects it as a 600. I don't care about the data on it so I tried doing a factory reset by turning the unit off; holding reset using a pin and hitting the power button with another pin but no luck. I can still access my shared folder so it doesn't seem to be performing the reset.

[mdgm]

What version of RAIDiator did you update from?

[VanTechs]

I believe it was 1.00c p18?!?

[mdgm]

That's very, very old firmware that you updated from.

I suggest the first thing you do is to backup your data, but if you really don't care about your data, don't bother.

So you followed the instructions here?: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu

Is the NAS able to boot into tech support mode (can check if it is using RAIDar: http://www.readynas.com/downloads)?

[VanTechs]

I don't care about data. I put it into tech support mode; RAIDar shows:

Model: IT71004-D02
Host name: none
IP: 192.168.168.168
TELNET - 58626

Now what do you suggest I should do?

[mdgm]

So that worked.

Perhaps you didn't do the factory default right.

Can you power off the unit and try doing a factory default again?:

1. Disconnect power from NAS to turn it off
2. Reconnect power
3. Press and hold reset button (e.g. using paperclip)
4. Press power button to turn NAS on (only need to hold this button till NAS starts to boot)
5. Continue holding reset button. The disk LEDs will blink twice, once after about 5 seconds (OS Re-install) and once after about 30 seconds (factory default). Release after the second blink (about 30 seconds).

[VanTechs]

I tried again several times but still no luck.

1. Turned the unit off by holding the power button for a few seconds. Then unplugged from power and plugged back in.
2. Pressed and held the reset button
3. Pressed and let go of the power button with another pin while kept holding the reset button.
4. Unit turned on but disk lights did not flash at all. Kept holding but no disk led flash; unit booted normally and just like before, i can still access my shared drive but Frontview doesn't work.

[mdgm]

After unit was downgraded to 4.1.4 Frontview access was able to be regained.

There is still the issue where the unit thinks it's a 600 though.

[c3po]

After unit was downgraded to 4.1.4 Frontview access was able to be regained.

There is still the issue where the unit thinks it's a 600 though.

Could you please download all logs and send to nsbu_logs@netgear.com ( attn: c3po )?
How many fans are reported on health page? Some old systems did not have correct model name programmed, software may think 1000s is 600 if only one fan is detetced.
The boot loader did not reponse to reset switch, what about power button? If you press and hold power button during very beginning of power on, do disk LEDs blink at all. This can tell me if it is broken reset switch or may be boot loader was corrupted during update.
I can get answers for above questions from your log file as well.

How did you upgrade to 4.18? Through FrontView?
How did you downgrade to 4.1.4 without FrontView, using raw-writer?
(Technically, we can upgrade from the very first release to any of later releases through FrontView. But there are restriction for raw-writer method because some pre-update and post-update scripts have not been run)

[mdgm]

4.1.4 update was done via the command line i.e. using something like this:

Code: Select all

$ cd tmp
$ wget http://www.readynas.com/download/RAIDiator/archive/4.1.4/RAIDiator-4.1.4
$ cd ..
$ echo /tmp/RAIDiator-4.1.4 > .cf_update_in_progress
$ reboot

I've read elsewhere that users of old Sparc units have had trouble trying to reset a system on 4.1.8 but worked after downgrading to 4.1.4 so thought it was worth a shot.

[VanTechs]

After unit was downgraded to 4.1.4 Frontview access was able to be regained.

There is still the issue where the unit thinks it's a 600 though.

Could you please download all logs and send to nsbu_logs@netgear.com ( attn: c3po )?
How many fans are reported on health page? Some old systems did not have correct model name programmed, software may think 1000s is 600 if only one fan is detetced.
The boot loader did not reponse to reset switch, what about power button? If you press and hold power button during very beginning of power on, do disk LEDs blink at all. This can tell me if it is broken reset switch or may be boot loader was corrupted during update.
I can get answers for above questions from your log file as well.

How did you upgrade to 4.18? Through FrontView?
How did you downgrade to 4.1.4 without FrontView, using raw-writer?
(Technically, we can upgrade from the very first release to any of later releases through FrontView. But there are restriction for raw-writer method because some pre-update and post-update scripts have not been run)

I do indeed have one fan plugged in; mostly because of the excessive noise. 1 fan spinning at 13000rpm is driving me nuts; let alone 4
Can I replace the fan with a slow one or the unit would report errors?

The power button did respond; just reset didn't. I upgraded to 4.1.8 through FrontView.

[c3po]

I am not sure if the RESET switch is on back or routed to front from my memory, but since you were able to do "echo /tmp/RAIDiator-4.1.4 > .cf_update_in_progress", you can issue this command to do factory reset "touch .os_install", basically, firmware will perform reset when a empty file .os_install is found. The file will be removed after reset. The other way to trigger factory reset is to remove all parititons on disk that firmware treats the disks as new and proceed to factory reset.

The reason why your 1000s is mistaken treated as 600 is that model name of early Infrant systems were not programmed same way as later systems.
vendor: Infrant
model: IT71004-D02
model_valid: 0
The wrong reported model should not affect the operating of the system.

So firmware tries to guess the model name and decide that yours is a 600, the reason, my guess, is that becuase you removed one pair fans. To quite down the fan, I used to go electronic store to buy fan regulator, bascially a serial resistor, then you can adjust fan speed to your desired level (Level that meets thermal requirement and satisfying acoustic level), keep in mind that the power consumption level of regulator needs to be at least half of total power ratings of fans that draw from the regulator. (i.e. The worst case for regulator is that half power consumed by regulator itslef, the other half is by fans: If two pair fans consume 5W, and you decide to put two pairs on one regulator, the regulator itslef should tolerate 2.5W on its resistor.).

[VanTechs]

I'm not sure if this issue is caused by the detection of the wrong model but for power options, I have Power Off but no Power On. This feature would be very handy for me as I could set it to Off during the day and On for backup at night time.

[mdgm]

I'm not sure about this either. Try a factory default and see if you can see power on options then.

[c3po]

Unfortunately, schedule power on was not available for 1000S board (The RTC alarm output was not connected to power on circuit ). Schedule power on was introduced for NV and later boards.