NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Ultra 6
7 Topics4.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.1KViews0likes5Commentsready nas ultra 6 Drive expansion with 6tb drives
Hi, Can someone tell me if I can install 4 x 6tb drives to my Readynas ultra 6 (Clean install) Would I get the full 18tb(3 x 6tb) with 6tb(1 x 6tb drive) acting as raidx redundancy shoudl i stick to 4tb drives? also at moment i have 3 x tb drives with 3 spare bays As an alternative to above Is it possible to add a second raid volume using 3 x 6tb to get 12tb with 1 drive being redundant and can i co-exist with the original volume In other words I have 4 x 6tb drives- how best to use them with my 6 bay - 3 drives poulatred with 2tb HDs in place Thanks AlanSolvedShell In a Box failed to start / cannot be removed
Hi, I have the Poussin app Shell in a box installed. Recently it misses its logo on the installed app page. When I switch the app on a pop-up occurs: The app failed to start. Please update or contact developer. Code: 22002010000 When I try to remove the application, the nas sends a email that it cannot be uninstalled. A couple of months ago I started using certificates from Lets Encrypt. Before that I used the self signed certficates. Could that be the cause? Best regards, JanSolvedOS 6.6.1 on Ultra 6 - Temperature readings incorrect
This looks to be a bug in 6.6.1 using my Ultra 6 (legacy) NAS. And I can't make sense of what is wrong: We have a ducted air conditioned house at around 25 degrees ambient My "CPU temperature" seems to have a "floor" of at or around 35 degrees and doesn't deviate too much from it, no matter the load... My "System temperature" fluctuates more erratically and is a higher temperature I decided to run a stress test (using "stress" via SSH). I ran a 5 minute test, with results below: The graph says the light blue CPU temp fluctuates from 47 to 57 degrees - which does not align to the text temp under the graph. Same is true for dark-blue system, which temperate increase lags the light-blue CPU, but the text under the graph says it's the lower temperature. So I guess I am trying to say: The thermometer temp guages at the top should be switched around so the system temp is ~35 degrees and is relatively stable (given the Hard disks are between 33-37 degrees, and air conditioning at 25 degrees) and the CPU temperature should be at 47 degrees and fluctuate more widely with load... The text under the graph should also be swapped. Funny thing is, sensors via SSH shows: coretemp-isa-0000 Adapter: ISA adapter CPU: +35.0°C (crit = +100.0°C) it8721-isa-0a10 Adapter: ISA adapter V5_0: +4.96 V (min = +4.76 V, max = +5.14 V) V3_3: +3.28 V (min = +3.13 V, max = +3.46 V) V1_8: +1.81 V (min = +1.50 V, max = +2.10 V) V-12: -12.10 V (min = -13.24 V, max = -10.73 V) 3VSB: +3.24 V (min = +3.14 V, max = +3.46 V) Vbat: +3.34 V System: 1205 RPM (min = 399 RPM) System: +52.0°C (low = +1.0°C, high = +80.0°C) sensor = thermal diode So OS6 web dashboard is showing what SENSORS is showing - but SENSORS has to be wrong... doesn't it?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.3KViews0likes14CommentsPower Timer not turning on OS6 FW 6.4.1 - Legacy Ultra 6
I recently acquired an Ultra 6 Plus, which I upgraded to OS 6, FW 6.4.1, for use in backups. The Power Timer function (which I liked better in the old NV+ models, since I could specify minutes) turns the U6+ off, but does not turn it on. I'm currently using a cron entry on my DD-WRT router to do a WOL job to turn the U6+ on at the specified time (3:50am). Needless to say, it's a fix smacking of Rube Goldberg, though not as good as the one in this simple alarm clock (No, this is NOT my proposed fix, perfume is expensive, and so are cannonballs). Hardware: ReadyNAS Ultra 6 Plus Firmware: 6.4.1 Time: correct Power Timer: currently 2am to 11am (so I can verify it turned on for to do backups, will shorten to 6 or 7am when assured of regular backups) Backup jobs: currently 4am to 6am (rsync pulls) WOL: enabled DD-WRT router cron WOL job: 3:50AM Ay suggestions on how I can fix this? I'm willing to SSH in if need be, but not completely comfortable in linux. -kevinb1 (formerly imsai on infrant/netgear, how do I change my handle back?) P.S. I'm also getting fan underspeed warnings, but one thing at a time....SolvedReady 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