NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Volume expansion fails even after factory default
Hi,
I've got a problem with Readynas Pro Business Edition. I've got 3 x 4TB + 3 x 3TB. Changed 4th 3TB to 4TB and expansion failed. It's OK since I probably passed the 8TB limit. I've made a fresh backup. Installed all 6 disks (bays 1-4 - WD Red 4TB, 5-6 - WD Red 3TB). Made factory default with single redundancy X-RAID2. After booting all procedures went well (checking disks + creating C + installing system). And now about strange things that happen.
1) System recognizes 4TB disks as 3TB (all six have about 2700 MB i volume information screen)
2) Last disk, in bay 6 starts blinking and system starts resync (why?). After it finishes the job after about 6 hours (volume is of course empty), it says volume expansion possible after reboot.
3) After reboot it recognizes 4TB disks properly, volume expansion starts and finishes in 3 seconds with "volume expansions failed".
4) Another reboot and after it another resync happens (?) and another expansion failer. After that next reboots doesn't make any changes. Nothing happens: neither resync nor volume expansion. Final status: volume of just 13TB with 4x4TB + 2x3TB.
I tried another factory default, tried formating disks under windows (to make them totally empty - I know it's somthing like voodoo, but wanted to be sure...), changing bays. Nothing. I want volume of over 16TB and that's why I made that factory default. But it's a total failure. Or maybe I just do something wrong.
Regards!
I've got a problem with Readynas Pro Business Edition. I've got 3 x 4TB + 3 x 3TB. Changed 4th 3TB to 4TB and expansion failed. It's OK since I probably passed the 8TB limit. I've made a fresh backup. Installed all 6 disks (bays 1-4 - WD Red 4TB, 5-6 - WD Red 3TB). Made factory default with single redundancy X-RAID2. After booting all procedures went well (checking disks + creating C + installing system). And now about strange things that happen.
1) System recognizes 4TB disks as 3TB (all six have about 2700 MB i volume information screen)
2) Last disk, in bay 6 starts blinking and system starts resync (why?). After it finishes the job after about 6 hours (volume is of course empty), it says volume expansion possible after reboot.
3) After reboot it recognizes 4TB disks properly, volume expansion starts and finishes in 3 seconds with "volume expansions failed".
4) Another reboot and after it another resync happens (?) and another expansion failer. After that next reboots doesn't make any changes. Nothing happens: neither resync nor volume expansion. Final status: volume of just 13TB with 4x4TB + 2x3TB.
I tried another factory default, tried formating disks under windows (to make them totally empty - I know it's somthing like voodoo, but wanted to be sure...), changing bays. Nothing. I want volume of over 16TB and that's why I made that factory default. But it's a total failure. Or maybe I just do something wrong.
Regards!
15 Replies
Replies have been turned off for this discussion
- OK. I should work. You were right, there were some mess with the cache, it rememberd old setup from 4.2.x.
- Something is definetly wrong. It created two volumes. Both RAID 5. First is 13,62TB and is empty, but status is unknown (there is statement RESYNC - 0%, time: NaN:NaN:NaN). And second one is data:0, free: 0. It does resync of this volume. It is not possible to remove it. Systems keeps showing alerts every couple of minutes.
- Volume 'data' health changed from 'redundant' to 'inactive' and opposite.
- To use disk, remove inactive volumes. Disks 1,2,3,4 (translation from my native language)
Also it shows the second volume (with data: 0) as configured on disks 1,2,3,4. - Yep, I did it. I hope so. Changed to Flex-RAID, removed both volumes, created new one on six disks, then changed to X-RAID2. We'll see.
- And there is a fan problem... System temp. - 70 C, disks - 43-47 C. Too much as I think. Fan speed is just 727 rpm which is too less and there's no fan control. Is it possible to change it?
- I'm selfanswering forum member....
The problem with fan solved after little calibrating and some cleaning. Temperature generally drops. More calibrating could be done to force main fan to work with at last 800 rpm in order to keep lower temperature all the time. Now it goes a little like sinus function and also NAS keeps sending warnings about fan being "below 704 rpm". Annoying but - as I think - it's not a real problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
