NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 1000S Disk change over, boot failure
My ReadyNAS 1000S has been working fine for over two years. We use it as a destination for backup images of our servers and other computers. After January 1, I wanted to replace the hard drives with a new set, and put the current set in off site storage. It seemed like a simple thing to do. The new hard drives are lightly used 1TB drives formatted for NTFS and I don't need the contents.
I shut the 1000S down and swapped out all of the drives. The NAS booted and was found by Raidar, but there were no volumes. I tried to do a OS reinstall, but I had instructions for a ReadyNAS 1100 rather than the 1000S and I think I got it botched up. No big deal I'll just start over from scratch.
I got the right ReadyNAS LED Language document and downloaded the TFTP tools and images. After a lot of trial and error I got TFTP working reliably if I put a Hub between the computer and the NAS. That's when I ran into the issue of kernel_init vs kernel_conf (and initrd). I found the conf versions but never the init versions. TFTP server works and downloads three files, but then I get disk lights flashing all on alternating with 1 & 3 which indicates "Boot loader fails to locate valid RAIDiator image, Raw-write CF shall solve the problem, otherwise, CF socket and DIMM are in question."
I have no reason to beleive that the CF or DIMM are broken so I would like to try the Raw Write of the CF. I have found and attempted, without success, a USB image load, but cannot find what image should be loaded onto the CF. Is it the file that gets loaded by TFTP? That one doesn't have an extension .img. Is the the file used by the USB reload? That doesn't seem likely.
I have read and followed the Unofficial USB recovery guide (Bott's Thoughts) and that results in "No disks detected, please choose disks from hardware compatible list." I get this result even with the original hard drives supplied by Infrant.
There really seems to be a lack of complete information about how this recovery or remote boot process should work and where to find all the required files. Any links or clues would be appreciated.
I shut the 1000S down and swapped out all of the drives. The NAS booted and was found by Raidar, but there were no volumes. I tried to do a OS reinstall, but I had instructions for a ReadyNAS 1100 rather than the 1000S and I think I got it botched up. No big deal I'll just start over from scratch.
I got the right ReadyNAS LED Language document and downloaded the TFTP tools and images. After a lot of trial and error I got TFTP working reliably if I put a Hub between the computer and the NAS. That's when I ran into the issue of kernel_init vs kernel_conf (and initrd). I found the conf versions but never the init versions. TFTP server works and downloads three files, but then I get disk lights flashing all on alternating with 1 & 3 which indicates "Boot loader fails to locate valid RAIDiator image, Raw-write CF shall solve the problem, otherwise, CF socket and DIMM are in question."
I have no reason to beleive that the CF or DIMM are broken so I would like to try the Raw Write of the CF. I have found and attempted, without success, a USB image load, but cannot find what image should be loaded onto the CF. Is it the file that gets loaded by TFTP? That one doesn't have an extension .img. Is the the file used by the USB reload? That doesn't seem likely.
I have read and followed the Unofficial USB recovery guide (Bott's Thoughts) and that results in "No disks detected, please choose disks from hardware compatible list." I get this result even with the original hard drives supplied by Infrant.
There really seems to be a lack of complete information about how this recovery or remote boot process should work and where to find all the required files. Any links or clues would be appreciated.
3 Replies
Replies have been turned off for this discussion
- You should've tried a factory default (wipes all data, settings, everything). The NTFS formatted disks will need to be wiped. See http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu
Does this not work?
Removing the CF card from the NAS and connect it to your PC and writing to it is the way to go. Writing this way you would use the standard firmware image not the TFTP boot recovery download or the USB Boot Recovery image.
What OS is on your client machine (e.g. PC? Mac?). - Our clients are PC's. The unit that accesses this drive 99% of the time is Windows server 2003.
The standard firmware image is the one found here http://www.readynas.com/?p=5827 ??
I will try this and post again later.
Thanks. - I am now back up and running.
The piece that I was missing was that the Image to write to the CF, is the same as the update file that would be downloaded to the NAS during an "Update". Not the TFTP image or USB image.
During all my thrashing about, I did find a new Raw Write utility that works with Windows 7.
http://www.netbsd.org/~martin/rawrite32 ... e32-en.htm
Its not real fancy but it was easy and it worked.
Thanks,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
