This morning I couldn't mount drives from my NV (either SMB or AFP). I couldn't access the NV via web browser either and pressing the power button failed to restart. When I checked the NV all (4) drive lights were steady green. I removed the power plug and rebooted the device.
Since then the NV has never successfully booted. I have tried an "OS Reinstall" and a "USB boot". I removed the (4) RAID drives and installed a single spare 750gig Seagate. I was able to successfully boot the NAS in this configuration. Upon replacing (4) RAID drives the NV would again not boot. The lights seem to settle into (2) sequences: drive lights on; power light on doing (3) slow blinks then (4) slow blinks drive lights off; power light on doing (3) slow blinks then (4) slow blinks
I have not tried a TFTP boot yet.
I have no recent backup of the NV. If I can't recover the drives in the NV I would appreciate some advice on what type of SATA controller I might use to mount the (4) drives on a Linux box using LVM.
As for data recovery using a Linux machine, that can be done (the ReadyNAS uses software RAID that is hardware accelerated), but best to try to diagnose what's going on with the NV first, I think.
I wouldn't try a TFTP boot recovery (I'd use USB boot recovery on the NV).
Thanks for the quick reply. I did a bit more reading this morning and found the Unofficial ReadyNAS USB Recovery Guide. This made me realize that my USB recovery was not seeing the correct sequence of light activity. I recreated the USB boot stick and attempted this again. This time the recovery did display the correct light sequences and the NV powered off at the end. The NV still did not boot however. I then did a OS recovery.
The NV is still not booting but now RAIDar is seeing the device and reporting the there are "Bad disks detected" and under the disks icon it reports "Not present". All the drive lights are out. And the power light is doing a steady slow blink.
I do have a brand new spare 750gig drive on hand. What is the best way to determine which drive (hopefully a single drive) is bad?
Best way is to power down, remove the drives (label order e.g. by noting down serial numbers) and hook the drives up to a SATA port on your PC. Then run SeaTools, doing both short and long tests. If a disk fails either test then it is bad and needs to be replaced.
mdgm, thanks again for the quick reply. I have performed a couple of more reboots - choosing to either skip the disk check or not. The NV has settled into a state where the power light is on but looks dim; drive lights 1-3 are on steady; drive light 4 is blinking. RAIDar shows all green, info in RAIDar reports "File system check 100%".
I have noticed that for a couple of minutes after the NV is booted it is responsive. It has sent me emails stating that there was a RAID event and a sync has started on volume C. After a bit it becomes unresponsive and settles into the light display described above.
I will pursue running the SeaTools on each each disk. A question, given that drive 4 is blinking can I safely attempt to replace that drive with a new one? Is there no going back after I attempt that?
I don't think you can assume drive 4 is bad from what you've seen. Best to check all disks and then suggestions on how to proceed can be made from there.
mdgm, A quick update: I installed SeaTools on a Windows 7 VM. I have connected each of the (4) drives to the VM using a SATA/USB adapter and run the ShortDST. All drives passed this test.
I'm am now running the Long Generic test. No problems so far.
mdgm, an update. The Long Generic test has completed successfully on drives 2-4.
The long test reported errors on drive 1. Additional short tests are also reporting errors on this drive. It had initially passed the ShortDST test last night.
Should I attempt to boot the NV with just drives 2-4 in place and no drive in slot 1? I do have a spare new drive. Would it be better to boot the NV with drives 2-4 in place and a new drive in slot 1?
Some success. NV came up I can now access it via Frontview and it sent me some email alerts: 1) The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. recovery media apps data backup Music 2) The X-RAID engine has failed to start.
Gonna 'fess up a bit. During my Monday morning pre-coffee attempt to get the NV online I did some too-quick reading on the forum. Somewhere I read that popping a drive and and then replacing it may force the NV to re-sync and become responsive. At that point all drive lights were steady green so I didn't suspect that that I had a bad drive. Also, never saw any email alerts from the NV about any problems.
How can I make the NV recognize that drives 2-4 are good? I have not yet replaced drive 1. Should I do that ? I do have SSH enabled on the NV and it is working. I made no changes to the NV via SSH. Just looking.
I copied the partition table from one of the other disks to hdi. Now it sees it but still marks it as faulty. I think I'm toast - unless you have any other ideas. I believe that hdi (disk 4) could be used to create the array if the NV could be convinced to try. FYI - interesting bits from dmesg:
ID disks check: ALL = 33/34/56/0/0/0/0/0, 3 IDE = 33/34/56/0/0/0/0/0, 3 MD = 0/0/0/0/0/0/0/0, 0 RAID rule check result: 0 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 Disk protected mark = 1 x_raid_start: 1,current:0 BDL_count= 0, fw=SN04, model= BDL_count= 1, fw=SN04, model= GOT MEMORY FOR DJ: 128*4k Drive hde SB at 1465135632(-sbs) CURRENT Drive hdg SB at 1465135632(-sbs) CURRENT Drive hdi SB at 1465135632(-sbs) CURRENT x_raid_start: 1,result:0 Find PHY: 0 Lookup PHY ID: 0x000f, 0x01 P0 GPIO initialization... BOARDID=1 Boot type/reason: normal/2/0 Found LM75 at 0x48 NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit) Samsung NAND flash rev C size of table 4096 table is there 0x8 bad block 2028 replacing by 4095 total bad block 1 bad 2028 = 4095 bad 4095 = -1 Total bad block number 1 retlen = 0x0200 VPD checksum = 0xfc25 ECC is ON Creating 2 MTD partitions on "NAND 64MiB 3,3V 8-bit": 0x00000000-0x00100000 : "P0 flash partition 1" 0x00100000-0x03ffc000 : "P0 flash partition 2" NEON flash: probing 8-bit flash bus CFI: Found no NEON flash device at location zero NEON flash: unknown flash device, mfr id 0x1, dev id 0x0 NEON flash: Found no Atmel device at location zero This board is not supported. You can use parm_extport=X module parm. I2C device 1f doesn't exist I2C device 1b doesn't exist LCD device not found X_RAID_START startstop XRAID command = start, flash_cache=0 X_RAID clean shutdown indicator: 0xe. 0 0 2 2 1 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 Update time for sb 1 = 0. Update time for sb 2 = 4e3fe8d2. Update time for sb 3 = 4e3fe8d2. Update time for sb 4 = 4c9e61d4. recent_ID = 2, select_ID=2, most_ID=2 right_mac=4 Selected sb 2, ctime=4e3fe8d2, id=a2010e6a. Use this image: 2
VERSION/ID : SB=(V:0.1.0) ID=<a2010e6a.00000000.00000000.00000000> CT:4e3fe8d2 RAID_INFO : DISKS(TOTAL:4 RAID:4 PARITY:3 ONL:3 WRK:3 FAILED:1 SPARE:0 BASE:0) SZ:1465128688 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1465128686 LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:0:000000000 DM:7 LOGICAL_DRIVE : 1: B:0004096002 E:1461032686 R:4 O:1 I:0:000000000 DM:7 PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1465128688,ST: B:online> PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1465128688,ST: :online> PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1465128688,ST: :online> PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1465128688,ST:P :faulty> CURRENT_DRIVE : DISK<N:1/2,XXX(33,0),ID:1,PT:1,SZ:1465128688,ST: :online> Not enough disks, would not start XRAID. X_RAID_COD_BACK READ 255 Access backup XRAID COD. Drive hde SB at 1465135632(-sbs) BACKUP Drive hdg SB at 1465135632(-sbs) BACKUP Drive hdi SB at 1465135632(-sbs) BACKUP X_RAID_START_BACK startstop XRAID command = start, flash_cache=0 Evaluating last known good configuration. X_RAID clean shutdown indicator: 0xe. 0 0 2 2 1 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 Update time for sb 1 = 0. Update time for sb 2 = 4e3fe8d2. Update time for sb 3 = 4e3fe8d2. Update time for sb 4 = 4c9e61d4. recent_ID = 2, select_ID=2, most_ID=2 right_mac=4 Selected sb 2, ctime=4e3fe8d2, id=a2010e6a. Use this image: 2
