NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Poeweshift-ReadyNAS Tech Support Nightmare #190 448 88
Sirs, i REALLY hate to pick on tech support, but something seriously went downhill fast with Netgear's tech support. I am a Powershift partner and sell and support many Netgear products, Routers, swit...
So you did do a reboot with the quota check option checked? I'm wondering whether thre could be a problem with the quotas e.g. for the ReadyNAS (Time Machine) user
I'm concerned by the mention of 4.2.15. Were the 3TB disks installed prior to the firmware update from 4.2.15? 3TB disks should not be added till after updating to 4.2.16 or later.
By commandline access I mean e.g. SSH or tech support still having access to tech support mode.
Edit: it sounds like from what you posted above that when you moved the disks across to the new NAS, the firmware may have been somehow downgraded to 4.2.15 (presumably 4.2.15 was in the flash of the replacement unit). Not sure how this is possible. This is going to cause problems. On 4.2.15 the limit for the Time Machine quota is 2TB. This downgrade may well have caused the quotas to be messed up. Hopefully forcing a reboot with quota check would repair this. Can you download your logs (Status > Logs > Download all logs) if you haven't already. What does the initrd.log look like? This should confirm whether or not my suspicion is correct as initrd.log shows a firmware update history.
If a reboot with quota check doesn't fix it, perhaps change the quota for Time Machine (under Backup > Time Machine in Frontview) to 2TB and do another reboot with a quota check. Then change the quota back and see if the problem is fixed. If you still have issues try an OS Re-install via the boot menu to see if that helps.
The 2.17TB is odd. 2.17TB is the maximum size a MBR partition on a disk can be. With the update to 4.2.16+ the partitions on the disks are converted from MBR to GPT (this is a one way conversion and irreversible) as GPT partitioning is needed to support 3TB drives. Perhaps 2.17TB was the actual maximum quota supported by the utilities used in 4.2.15?
Downgrading from 4.2.16+ to 4.2.15 is not supported and any attempt to downgrade intentional or otherwise is going to lead to problems. The 4.2.15 OS, utilities etc. are not designed to work with internal GPT partitioned drives or a quota of the size you set. I recommend when moving disks to a new unit that you first get a spare disk (not from your array) and place that in the new unit (if the disk is used you might need to wipe it via a factory default via the boot menu) and confirm that the firmware is at least as up to date as what was on the old unit. If it's not update the firmware and verify that the firmware update was successful. Then power down, remove the spare disk and follow the migration procedure: http://www.readynas.com/kb/faq/boot/how_do_i_migrate_disks_over_from_an_existing_readynas_to_another
I'm concerned by the mention of 4.2.15. Were the 3TB disks installed prior to the firmware update from 4.2.15? 3TB disks should not be added till after updating to 4.2.16 or later.
By commandline access I mean e.g. SSH or tech support still having access to tech support mode.
Edit: it sounds like from what you posted above that when you moved the disks across to the new NAS, the firmware may have been somehow downgraded to 4.2.15 (presumably 4.2.15 was in the flash of the replacement unit). Not sure how this is possible. This is going to cause problems. On 4.2.15 the limit for the Time Machine quota is 2TB. This downgrade may well have caused the quotas to be messed up. Hopefully forcing a reboot with quota check would repair this. Can you download your logs (Status > Logs > Download all logs) if you haven't already. What does the initrd.log look like? This should confirm whether or not my suspicion is correct as initrd.log shows a firmware update history.
If a reboot with quota check doesn't fix it, perhaps change the quota for Time Machine (under Backup > Time Machine in Frontview) to 2TB and do another reboot with a quota check. Then change the quota back and see if the problem is fixed. If you still have issues try an OS Re-install via the boot menu to see if that helps.
The 2.17TB is odd. 2.17TB is the maximum size a MBR partition on a disk can be. With the update to 4.2.16+ the partitions on the disks are converted from MBR to GPT (this is a one way conversion and irreversible) as GPT partitioning is needed to support 3TB drives. Perhaps 2.17TB was the actual maximum quota supported by the utilities used in 4.2.15?
Downgrading from 4.2.16+ to 4.2.15 is not supported and any attempt to downgrade intentional or otherwise is going to lead to problems. The 4.2.15 OS, utilities etc. are not designed to work with internal GPT partitioned drives or a quota of the size you set. I recommend when moving disks to a new unit that you first get a spare disk (not from your array) and place that in the new unit (if the disk is used you might need to wipe it via a factory default via the boot menu) and confirm that the firmware is at least as up to date as what was on the old unit. If it's not update the firmware and verify that the firmware update was successful. Then power down, remove the spare disk and follow the migration procedure: http://www.readynas.com/kb/faq/boot/how_do_i_migrate_disks_over_from_an_existing_readynas_to_another
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
