NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Number6
Jan 19, 2021Aspirant
readynas pro 6 stuck in boot/check root FS/check FS loop
Help: readynas pro 6 stuck in boot/check root FS/check FS loop I had a power failure. Rebooting this ReadyNAS it's stuck in a loop of booting... checking root fs... checking fs rinse-and-repeat. ...
Number6
Feb 08, 2021Aspirant
booted six times -- moving that spare drive from slot to slot. all booted aok.
Went back into "debug mode" (that's what was displayed on the LEDs this time); logged in; and did
mdadm -A -f -vv --scan --homehost=001F33EADAB1 --auto-update-homehost --auto=md
Results were (and then terminal was still active for a while... then it rebooted):
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/sda
mdadm: no recogniseable superblock on /dev/sdb
mdadm: no recogniseable superblock on /dev/sdc
mdadm: no recogniseable superblock on /dev/sdd
mdadm: no recogniseable superblock on /dev/sde
mdadm: no recogniseable superblock on /dev/sdf
mdadm: no recogniseable superblock on /dev/sdg
mdadm: no RAID superblock on /dev/sdg1
mdadm: /dev/sda1 is identified as a member of /dev/md/0, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md/0, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md/0, slot 2.
mdadm: /dev/sdd1 is identified as a member of /dev/md/0, slot 3.
mdadm: /dev/sde1 is identified as a member of /dev/md/0, slot 4.
mdadm: /dev/sdf1 is identified as a member of /dev/md/0, slot 5.
mdadm: added /dev/sdb1 to /dev/md/0 as 1
mdadm: added /dev/sdc1 to /dev/md/0 as 2
mdadm: added /dev/sdd1 to /dev/md/0 as 3
mdadm: added /dev/sde1 to /dev/md/0 as 4
mdadm: added /dev/sdf1 to /dev/md/0 as 5
mdadm: added /dev/sda1 to /dev/md/0 as 0
mdadm: /dev/md/0 has been started with 6 drives.
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/sdg1
mdadm: /dev/sda2 is identified as a member of /dev/md/1, slot 0.
mdadm: /dev/sdb2 is identified as a member of /dev/md/1, slot 1.
mdadm: /dev/sdc2 is identified as a member of /dev/md/1, slot 2.
mdadm: /dev/sdd2 is identified as a member of /dev/md/1, slot 3.
mdadm: /dev/sde2 is identified as a member of /dev/md/1, slot 4.
mdadm: /dev/sdf2 is identified as a member of /dev/md/1, slot 5.
mdadm: added /dev/sdb2 to /dev/md/1 as 1
mdadm: added /dev/sdc2 to /dev/md/1 as 2
mdadm: added /dev/sdd2 to /dev/md/1 as 3
mdadm: added /dev/sde2 to /dev/md/1 as 4
mdadm: added /dev/sdf2 to /dev/md/1 as 5
mdadm: added /dev/sda2 to /dev/md/1 as 0
mdadm: /dev/md/1 has been started with 6 drives.
mdadm: looking for devices for further assembly
mdadm: /dev/sda3 is identified as a member of /dev/md/2, slot 0.
mdadm: /dev/sdb3 is identified as a member of /dev/md/2, slot 1.
mdadm: /dev/sdc3 is identified as a member of /dev/md/2, slot 2.
mdadm: /dev/sdd3 is identified as a member of /dev/md/2, slot 3.
mdadm: /dev/sde3 is identified as a member of /dev/md/2, slot 4.
mdadm: /dev/sdf3 is identified as a member of /dev/md/2, slot 5.
mdadm: added /dev/sdb3 to /dev/md/2 as 1
mdadm: added /dev/sdc3 to /dev/md/2 as 2
mdadm: added /dev/sdd3 to /dev/md/2 as 3
mdadm: added /dev/sde3 to /dev/md/2 as 4
mdadm: added /dev/sdf3 to /dev/md/2 as 5
mdadm: added /dev/sda3 to /dev/md/2 as 0
mdadm: /dev/md/2 has been started with 6 drives.
mdadm: looking for devices for further assembly
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/md/2
mdadm: no recogniseable superblock on /dev/md/1
mdadm: no recogniseable superblock on /dev/md/0
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: no recogniseable superblock on /dev/sdg
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: no recogniseable superblock on /dev/sdg1
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: cannot open device /dev/sdb2: Device or resource busy
mdadm: cannot open device /dev/sdc2: Device or resource busy
mdadm: cannot open device /dev/sdd2: Device or resource busy
mdadm: cannot open device /dev/sde2: Device or resource busy
mdadm: cannot open device /dev/sdf2: Device or resource busy
mdadm: cannot open device /dev/sda3: Device or resource busy
mdadm: cannot open device /dev/sdb3: Device or resource busy
mdadm: cannot open device /dev/sdc3: Device or resource busy
mdadm: cannot open device /dev/sdd3: Device or resource busy
mdadm: cannot open device /dev/sde3: Device or resource busy
mdadm: cannot open device /dev/sdf3: Device or resource busy
Any more ideas?
mdgm
Feb 08, 2021Virtuoso
That would seem to suggest that the SATA backplane is probably fine.
If the disks are fine, then I guess it would point to a problem on the disks, or looking at doing a memory test of the RAM (if not done already) or perhaps a problem with the PSU.
Try starting just the 4GB root volume. I think from memory it's something like this:
# mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
If that works you could mount the sysroot and have a look around in that.
- Number6Feb 08, 2021Aspirant
I did that and then telnet "hung", then it started rebooting.
HERE:
# mdadm -vv --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 5.
mdadm: added /dev/sdb1 to /dev/md0 as 1
mdadm: added /dev/sdc1 to /dev/md0 as 2
mdadm: added /dev/sdd1 to /dev/md0 as 3
mdadm: added /dev/sde1 to /dev/md0 as 4
mdadm: added /dev/sdf1 to /dev/md0 as 5
mdadm: added /dev/sda1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 6 drives.
If no other ideas (more ideas would be MOST appreciated!), then should I:
(A) Pay $400 for service
or
(B) Pay $250-400 for a replacement unit on ebay -- hoping that my drives will just work in that unit.
- mdgmFeb 08, 2021Virtuoso
If the system crashes doing a simple thing like starting the RAID then paying for software service is going to be a waste of time unless it's just that one of the disks is bad and needs to be removed or cloned or something like that.
The problem is either:- failing PSU
- bad disk
- some other hardware issue e.g. RAM etc.
Have you run the memory test boot menu option for at least a few passes?
Have you tried the disk test boot menu option and/or done e.g.
# smartctl -t long /dev/sda
Seeing your system is crashing I would wait for each disk's test to finish before trying the next one if you do this.
If you are confident the disks are fine and don't want to go down the route of trying replacing the PSU and/or RAM, then getting a new NAS e.g. RN426, RN526X etc. and moving the disks across is probably what should be tried next.
- Number6Feb 09, 2021Aspirant
Hadn't run the boot mode tests yet. Ran smartctl smarttest on all six seemingly ok. starting a long test on sda now.
If it's a bad disk, then shouldn't I be able to try booting with one disk removed at a time? Thinking it might be disk 0, I did try that but it didn't work. If that's a good test for a bad drive, then I'll do it and if it works with just one removed, then I can replace that drive.
I've hunted on the bay for RN426 OR RN526X and didn't find any. Are those the only 6 bay units that are upward compatible with my Pro 6? -- i.e. that I can just plug my six drives in and they should just work? Going that way sounds attractive since I could upgrade to 4-8GB drives (the Pro is stuck at 3GB drives max).
- mdgmFeb 09, 2021Virtuoso
The latest models are RN426, RN428, RN526X, RN528X, RN626X, RN628X
Older OS6 models are RN316, RN516 and RN716XIf the disks, array and OS are fine it will boot with the volume read-only so you can copy your data off, then do a factory reset (wipes all data, settings, everything) and restore data from backup.
I don't recommend getting RAIDiator-x86 units (e.g. Ultra, Ultra Plus, Pro) unless you really love buying old hardware. They would all have been manufactured over 8 years ago and thus even if in working condition now, are more likely to fail sooner.
Your Pro is not limited to 3TB disks, however upgrading to higher capacity disks whilst staying on RAIDiator-x86 would run into expansion limitations.
- mdgmFeb 09, 2021Virtuoso
Number6 wrote:If it's a bad disk, then shouldn't I be able to try booting with one disk removed at a time? Thinking it might be disk 0, I did try that but it didn't work. If that's a good test for a bad drive, then I'll do it and if it works with just one removed, then I can replace that drive.
You could, however I don't like to do it that way. If the disks become out of sync it could force a resync leading to further problems.
It sounds to me like most likely it's a PSU issue with spinning up all the disks drawing too much power from a failing PSU. One way to test this theory would be to put 6 scratch disks in and see if it enters the reboot loop. If it doesn't enter the reboot loop then it would suggest a bad disk.
If you remove the PSU you can inspect it to see if it's damaged. PSUs are one of the most likely components to fail in a PC and they have failed in a number of Pro units. It's hardly surprising that PSUs are failing well after the warranty has expired.
- SandsharkFeb 09, 2021Sensei
Number6 wrote:I've hunted on the bay for RN426 OR RN526X and didn't find any. Are those the only 6 bay units that are upward compatible with my Pro 6? -- i.e. that I can just plug my six drives in and they should just work?
No OS6 unit will have that level of compatibility unless the Pro6 was converted to OS6 (and I can see yours wasn't). You can put the drives from your unit in one in order to recover data in a read-only mode, but it won't "just work" as a production NAS.
If you have an ATX power supply lying around, you could connect it externally in place of the internal one and see if that resolves the problem, or even run it that way long enough to recover the data. If you do plan to do that and run it a long time, use masking tape to block the gap the cable goes through and the internal power supply fan outlet so the chassis fan properly draws air around the drives and motherboard. If that works, then you can get more life from your NAS by replacing the internal supply with an SFX format one.
- Number6Feb 09, 2021Aspirant
I'm running the long tests on each disk now (on second right now). each takes 4 hours. After I run all six, THEN I'll try six spare drives to see what happens.
I don't think I have a spare PS (the only spare I had was already put into use).
- SandsharkFeb 10, 2021Sensei
If you can temporarily "borrow" an ATX supply from a working machine long enough to determine if the supply is the issue, that would help. If that is it, we can guide you in replacing the internal one with a standard SFX one. One issue may be the number of Molex 4-pin connections, as you need three. But SATA to 4-pin adapters and 4-pin splitters can be employed. Otherwise, it just needs the standard ATXv12 24-pin main and 4-pin CPU connections. It should also be at least 450W to insure it has sufficient 12V power.
For data recovery only, if you have a way to mount the drives in a PC internnaly and/or externally using SATA to USB or eSATA connections, you can use R-Linux for Windows or a native Linux system to recover the data. I'm not expert on that, but others can guide you.
- StephenBFeb 10, 2021Guru - Experienced User
Sandshark wrote:
you can use R-Linux for Windows or a native Linux system to recover the data. I'm not expert on that, but others can guide you.
R-Linux for Windows is freeware, and won't work for this - it doesn't support RAID (so you can only use it for JBOD or RAID-1).
You could use their paid software (R-Studio) instead. https://www.r-studio.com/data-recovery-software/
- Number6Feb 28, 2021Aspirant
Thanks very much to Sandshark I was able to replace the entire box and ... it all worked just fine!!! Woo Hoo !!!!!!!
So, it *might* have been the PSU (or something else?).
Now that I have a ReadyNas Pro 6 that *might* just need a working PSU, I'd like to consider finding and trying to replace the PSU to see if I can get it working. It seems that I can find a power supply that will probably fit (kinda) or it might need a 24pin cable extender on ebay for about $30 --- or I see one there that's supposed to all fit right for $65. My experience over the years is that if something's not going to fit, I'll be the one that experiences it and ends up having trouble finding the right extra pieces.
Any specific suggestions (the cheaper the better) for a PSU that will "just fit" gladly accepted and appreciated.
- SandsharkFeb 28, 2021Sensei
Even when the "original" Seasonic was available, it didn't have the extended 24-pin cable needed for a ReadyNAS. I don't know if the eBay seller listing the ones that "just fit" had them custom made or just includes the required extender pre-installed. A 6-inch extender on eBay is about $7, so you do end up with a lower total cost that way, assuming a 6" extension is long enough (it typically is, but one can never be sure unless you've used that brand before).
While the Seasonic power supply is rated at 300W, it's distribution of the various voltages is atypical, and you generally have to get a 350W or even 400W or more supply to insure it has sufficient 12V power. A lot of them don't have the three 4-pin Molex connectors, either. But I usually replace them with the 90-degree ones from the old supply to shorten those cables and make the overall installation a little cleaner.
Do come back and let us know what you decide. I used up my last stored away Seasonic, so will have to buy something if I need to fix another. But every time I see something that looks promising, it seems it goes off the market.
- Number6Mar 01, 2021Aspirant
Sandshark -- I wasn't going to post the link since I'm not pushing this Psu, but since it might or might not work & you know the hardware details that I don't know... here's the possibly compatible Psu: https://www.ebay.com/itm/NEW-350W-Netgear-ReadyNAS-Pro-Business-Edition-POWER-SUPPLY-Replace-N2-/401764577845
Sure, I'd MUCH rather spend $30-40 instead of $65, but if this one will work "for sure", it's likely worth it (is it?).
- SandsharkMar 01, 2021Sensei
Your link is broken, but I know the one you are referring to. The specs look good. The +5V and +3.3V are individually rated lower than the original, but the 20A rating for each on the original is a bit misleading since their combined capability is less than the total of the two separate specs. And the NAS really doesn't draw that much from those, anyway. The two +12V busses are rated higher, and so is the +5VSB.
So, based on the ad, I'd say it should work just fine. Better, in fact, since it has a thermally controlled fan and the higher +5VSB (which is what's often the first to go).
The seller is KDMPower, and it appears to be a modified KDM SFX power supply. If that means they are the manufacturer, then they may have custom built them with the longer cable, whihc is easier to install than a normal one with extender.
It does not show if it's 110/220V auto-switching or has a manual switch (which would be impossible to get to once installed in the NAS). But that's not something you'll normally need to worry about.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!