NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Ultra 6
3 Topics
4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
So I logged into my Ultra 6 and noticed there was a firmware upgrade available from May 2017! Since I get at least two emails from my NAS every day I assume it should have emailed me about this, but anyway, that's a minor problem. I installed the upgrade and then.... time machine no longer worked. My two laptop macs no longer could log in. I rebooted the ReadyNAS (since sometimes it gets in a mode where nothing can log into it) and it didn't help. Probing a little further, I attempted to change the Time Machine access password to be sure I had it correct. The web interface hung! A hard reset and disk check later and some errors were corrected. All SMART reading good and no errors. So I tried again. Same result. Every time I tried to change the time machine access password the UI and effectively the ReadyNAS hung. The next step was re-installing the OS, using the reset hole and front panel buttons. I did this. Another disk check. Now I can attempt to change the time machine access password and it appears to work, except the "volume size" of the time machine space is set back to the default 3000 every time I apply changes. Digging deeper, it appears my partitions are mounted read-only which would explain a lot. # touch /c/doc/SymformContrib/delete_this touch: cannot touch `/c/doc/SymformContrib/delete_this': Read-only file system During boot in kern.log I have this EXT4-fs error (device dm-0): ext4_mb_generate_buddy:726: group 10 blocks in bitmap, 32768 in gd Sep 14 10:59:30 sleepy kernel: Aborting journal on device dm-0-8. Sep 14 10:59:30 sleepy kernel: EXT4-fs (dm-0): Remounting filesystem read-only Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_ext_remove_space:2437: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_orphan_del:2098: Journal has aborted Sep 14 10:59:31 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted The first line seems to be some Linux bug which may have been fixed. My data is there. The filesystem is read only. This seems to be showing up other bugs (such as the entire device hanging). Does anyone have any suggestions beyond "Backup your 12GB data, install OS6 and start again"? Many thanks in advance.1.1KViews0likes5Comments
Recovering volumes from ReadyNas Ultra 6
Is there any way to recover volumes on a readynas running RAIDiator 4.2.30? I had 6 hard disks, raid1 into 3 volumes and after doing an OS Reinstall, it can't recognise the volumes. The data is still intact as I can browse to the nas via clicking Browse on RAIDar, the original shares are there but I don't have access rights to them. Alternatively, what is the best software to use to read the data from the drives and then I can wipe them and start again?4.3KViews0likes14CommentsReady NAS Ultra 6 -- dead drive but no warnings. Says I still have redundancy. How?
I have an Ultra 6 with 6 disks. The 5th disk is dead according to the Health screen in FrontView. However when I go to Volume Settings it says: "Status: Redundant" How can I have redundancy if one of the drives is dead? The storage of the other 5 drives adds up the capacity shown so there doesn't seem to be any redundancy at all. There are no warnings telling me to replace the drive. I don't get it.2.8KViews0likes7Comments