NSA325: Internal volume degraded - repair not available/reachable (RAID1)
Paolo DeF
Posts: 11 Freshman Member
Dears, I have a NSA325v2, configured in RAID1. Lately, volume status has become "degraded".
The storage/volume management page takes a very long time lo load (dozens of minutes).
Even after I reach the page, it stays in "Please wait" (for hours...). I cannot even try to repair or resynch the RAID.
See below.
Can you please suggest how to proceed?
Thanks a lot!
Paolo
The storage/volume management page takes a very long time lo load (dozens of minutes).
Even after I reach the page, it stays in "Please wait" (for hours...). I cannot even try to repair or resynch the RAID.
See below.
Can you please suggest how to proceed?
Thanks a lot!
Paolo
0
Accepted Solution
-
That looks strange, indeed. But I think the right disk is dead. HD0 is waked up regularly, also by 'normal' daemons.################################ HD0 awaked by nfsd ! ################################while HD1 is never waked up, while the kernel regularly tries to put it asleep, resulting in an error.***************************************
* HD1 stand by now! *
***************************************
Set Power Saving Mode failIt's normal that the NAS works normally, that is the whole point of raid1. But apparently the firmware can't handle a disk which doesn't answer to higher level commands.
0
All Replies
-
I think (one of) the disks is (almost) dead, causing long delays, and maybe internal crashes of the backend. Do you have shell access?
0 -
Hi, thank you. Yes, I have access via telnet. I guess you're right. Please note that, other than Volume, S.M.A.R.T. and such, the NAS works just fine.0
-
You can run 'dmesg' to see the kernel error log. I think it will show a lot of I/O errors on either sda (the left disk, I think), or sdb (the right disk). Remove the disk that has I/O errors, and it should work.Then you can plug in an equal sized or bigger disk to regain your redundancy.0
-
That looks strange, indeed. But I think the right disk is dead. HD0 is waked up regularly, also by 'normal' daemons.################################ HD0 awaked by nfsd ! ################################while HD1 is never waked up, while the kernel regularly tries to put it asleep, resulting in an error.***************************************
* HD1 stand by now! *
***************************************
Set Power Saving Mode failIt's normal that the NAS works normally, that is the whole point of raid1. But apparently the firmware can't handle a disk which doesn't answer to higher level commands.
0 -
Thanks again. I'll try to mount the HDD on the computer and see if it's definitely dead or can somehow be revived. Cheers0
-
Hi, just run a few checks. If I leave just the "good" HD the NAS works just fine. I was able to mount it on my computer and it's ok. The "bad" HD spins but nothing more. The NAS does not even recognize it has been attached. I have not been able to mount it on the computer (linux was not even booting... strange, but then I stopped).
I'm leaving just the HD working in the NAS and I'm buying a new HD.
Again, thanks a lot.
Cheers, Paolo0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 148 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight