NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
x86 Issues
111 Topics
Easy fix fan/temp OS6 issues on x86 legacy #no support
>> EDIT - 2014-04-12 << Before to hack your system, update first to 6.1.7. Built-in fancontrol support is there! 6.1.7 has been released: http://www.readynas.com/forum/viewtopic.php?f=1&t=76000 >> EDIT << Here is how to fix fan and temperature issues on legacy x86 systems running OS 6.x, until built-in support is there. I'd previously created this post http://www.readynas.com/forum/viewtopic.php?f=51&t=70133&start=255#p393886 but it will be easier for community to have fancontrol file examples for all models in a dedicated post. It's a very easy and reliable method to monitor fan and temperature with lm-sensors and fancontrol standard packages. No change on GUI reports. NO WARRANTY / NO SUPPORT !!! with root access, execute the following commands: apt-get update && apt-get upgrade apt-get install lm-sensors fancontrol echo "#fancontrol" > /etc/fancontrol edit /etc/fancontrol file and copy the following file example corresponding to your model http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324 or create your own /etc/fancontrol file using pwmconfig command http://www.readynas.com/forum/viewtopic.php?f=51&t=71155&p=395324#p395318 fancontrol daemon start automaticaly when you install it. restart fancontrol daemon for changes in file /etc/fancontrol take effect /etc/init.d/fancontrol restart to interact with fancontrol daemon, use /etc/init.d/fancontrol stop /etc/init.d/fancontrol start /etc/init.d/fancontrol restart You can display sensors values with sensors command root@nas-xx-xx-xx:~# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +43.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +49.0°C (high = +80.0°C, crit = +100.0°C) it8721-isa-0a10 Adapter: ISA adapter in0: +12.19 V (min = +8.06 V, max = +10.66 V) ALARM in1: +4.98 V (min = +2.20 V, max = +3.51 V) ALARM in2: +3.28 V (min = +0.02 V, max = +0.18 V) ALARM in3: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM in4: +1.02 V (min = +1.42 V, max = +2.21 V) ALARM in5: +1.80 V (min = +1.66 V, max = +0.54 V) ALARM in6: -12.10 V (min = -25.78 V, max = -0.01 V) in7: +3.24 V (min = +0.00 V, max = +2.86 V) ALARM in8: +3.34 V fan1: 0 RPM (min = 10 RPM) ALARM fan2: 0 RPM (min = 44 RPM) ALARM fan3: 851 RPM (min = 11 RPM) temp1: +0.0°C (low = +57.0°C, high = -25.0°C) ALARM sensor = thermistor temp2: +0.1°C (low = -16.0°C, high = -123.0°C) ALARM sensor = thermal diode temp3: +0.1°C (low = +37.0°C, high = -44.0°C) ALARM sensor = thermal diode cpu0_vid: +2.050 V16KViews0likes173Comments
Experience with OS 6 on Legacy....
Does anyone have any thoughts, tips, caveats to running OS6 on legacy hardware? I see lots of complaints, problems, etc. I'd like to hear from anyone that's got it running and using it on a day to day basis. I just bought a 316 and have that building the array. I also have an NVX and Ultra 4 Plus. Was thinking that it would be nice to have the newer OS and features on the U4+ Current use for my NVX is media storage and streaming with backups of my personal files from the U4+. The U4+ is used for Bit Torrent, media streaming and personal files. The NVX I picked up for super cheap a little over a year ago from Green Citizen. I think the backplane has gone bad as two drives will occasionally "go dead". So I shut it off and let it sit. I turn it on after a few days and it works fine. Hence the new 316 Going to have to shuffle things around from one NAS to the other. If I think that OS 6 on the U4+ isn't viable or worth it in the long run. I'll stick to 4.xx6.9KViews0likes18Comments
*Solved* OS6 6.2.2 Frontview gone-fixed without SSH
I installed OS6 6.2.2 on a Ultra 6 Plus, been stable for several months now. I ran into a problem with the Monsta FTP app, and tried uninstalling it to reinstall. Oops. Hadn't seen the 6.2.2 bug posts. Frontview is now unavailable, and the "/shares/" web page is unresponsive. I think apache is Having A Bad Day. After reading around a bit, It looks like the ways to fix it are to: A) Reinstall the app: Tried, didn't work. B) Use OS Reinstall. OS Reinstall did not get rid of the problem. The IP is now dynamic, but still can't get any web pages. C) Use SSH to remove a bad apache line: http://www.readynas.com/forum/viewtopic.php?f=20&t=79230&p=446538&hilit=apache2#p446538. Uh, oh, I did not enable SSH. <facepalm> G-T-H) Do a Factory Reinstall then restore from backups. OK, this will work, but I'd be willing to do some work to get around this. Save the Go-To-Hell option for last. Is there a way to maybe use Tech Support mode to telnet in to fix it? Yep. *WARNING: Do this CAREFULLY. This is in a place where Users Were Not Meant To Go!* After doing some further reading, solved it this way: 1) Booted the machine into Tech Support Mode 2) used putty to telnet (port 23) into the IP shown on the front panel using root:[secret_Netgear_ReadyNAS_Support_password]. Tip: Google Search Is Your Friend. 3) since the boot partition is unavailable in Tech Support mode, I mounted it using: echo DEVICE partitions > /etc/mdadm.conf mdadm --examine --scan >> /etc/mdadm.conf mdadm --assemble --scan mount /dev/md0 /mnt 4) change to the apache2's startup directory and look at the directory: cd /mnt/etc/apache2/sites-enabled ls -1 This is what I saw: 000-fv-http <-NOTE:DON'T REMOVE THIS! 000-fv-https <-NOTE:DON'T REMOVE THIS! 001-fv-https2 <-NOTE:DON'T REMOVE THIS! 090-monsta.conf <-removed app startup link! 5) moved the bad link from the apache2 startup directory to the directory above it by using: mv 090-monsta.conf .. I could have removed it, but wanted to keep it until I knew I hadn't messed up. I then unmounted the boot partition, cleared and synced, and rebooted by: cd / sync umount /dev/md0 reboot Fixed! After FrontView came up, I enabled SSH, logged in using putty on SSH (port 22) using root:[admin_password] and then went to remove the troublesome apache link: cd /etc/apache2 rm 090-monsta.conf logged off ...and done.5.3KViews0likes9Commentssuddenly started getting fan speed errors
hi, I run 6.2.4 on RNDU4000, and suddenly started getting errors in log and email: Thu Jun 11 2015 9:24:08 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). Thu Jun 11 2015 9:22:11 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (711 rpm). Thu Jun 11 2015 9:19:54 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (711 rpm). Thu Jun 11 2015 9:16:02 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (711 rpm). Thu Jun 11 2015 9:14:36 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (710 rpm). Thu Jun 11 2015 9:08:54 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (711 rpm). Thu Jun 11 2015 9:07:23 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). Thu Jun 11 2015 9:06:16 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). Thu Jun 11 2015 9:04:15 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (708 rpm). Thu Jun 11 2015 9:03:33 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (711 rpm). Thu Jun 11 2015 9:02:27 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (707 rpm). Thu Jun 11 2015 9:00:56 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). Thu Jun 11 2015 8:58:54 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). Thu Jun 11 2015 8:58:18 System: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (709 rpm). how to fix this?6.5KViews0likes23Comments
Upgrade ReadyNAS Pro Business Edition
Hi all.. Do you anticipate any problems with upgrading the following: Modell: ReadyNAS Pro Business Edition [X-RAID2] Serie: XXXXXXXXXXXXXXXX Software: RAIDiator 4.2.27 Memory: 4096 MB [4-5-5-18 DDR2] (Upgraded cpu, cant remember wich type, need to check) Not quad. Using this: Upgrading from 4.2.x direct to 6.2.1 beta (or is there another way? ) Regards Hans7.3KViews0likes10Comments
USB backup on OS 6.2.4 Ultra6 fails
I am having difficulty with backing up my Ultra6 via USB to an external Seagate 4TB USB disk drive, namely: USB backup to a specific USB port fails with "Backup: Error backup job '<sharename>': destination cannot be accessed." USB ports listed from the dropdown in backup configuration include "USB Back Top" and "USB Back Bottom" while the Ultra6 has USB Back Left and USB Back Right ports on the back The USB device have iterrated from USB_HDD_1 through to USB_HDD_3 (negating the solution to backup to the USB share) Logs show the device is connected to: usb_devices 2-1 product=USB DISK idProduct=1000 idVendor=090c devnum=2 speed=480 2-1:1.0 2-2 product=Expansion Desk idProduct=3312 idVendor=0bc2 devnum=3 speed=480 2-2:1.0 .. 7-0:1.0 7-1 product=Back-UPS ES 550G FW:870.O3 .I USB FW:O3 idProduct=0002 idVendor=051d devnum=2 speed=1.5 7-1:1.0 usb_storage *** Connected devices *** /dev/disk/external/3:-1:ST4000DM000-1F2168:Z3017Q3G:480:7814037160 -> ../../sdh While the backup jobs configure themselves (in /etc/frontview/backup_jobs.conf) as (using USB Back Top, USB Front and USB Back Bottom): USB Back Top = dst: [usb:usb_port_3:3]/ USB Front = dst: [usb:usb_port_3:1]/ USB Back Bottom = dst: [usb:usb_port_3:4]/ Has anyone encountered this issue and solved it? I have the 4TB plugged into the Back Left port and a UPS plugged into the Back RIght port. Nothing plugged into the front port. I have not swapped or tested other ports yet but will do so this weekend. Any help would be greatly appreciated.Solved5.9KViews0likes12CommentsUPS Communication
Has anyone has recent issues with UPS communications? I have two ReadyNAS PRO 2 and they suddenly starting having UPS communication issues. One of them has the UPS master and broadcast UPS status. Two days ago they started have alerts every two minutes. I have since put the UPS on another NAS as master and have them talk to it that way. It seems to be working now, but I am still getting communication errors. The new Master is not giving me any errors with the UPS so I am assuming the UPS is ok it is the deamon for the UPS on the readynas that is causing the issues. Has anyone updated the package and has that resolved anyone issues (both PRO 2 are updated to 6.2.4) Thanks3.7KViews0likes5CommentsSMB: Browse shares from android broken
Hi, Devices: Ready NAS Ultra 2, OS 6.2.4 Under OS 4, I could access my shares using android Root Explorer or ES File Explorer on my local wifi network With OS6, using Root Explorer, I noticed I can only browse folders, but I cannot list the file they contain. Files in root of the share are listed, but not downloaded. Basically, I can browse through folder structure but I cannot list any file. ES File Explorer gives an error when accessing folders from share root: insufficient permissions Same shares with same credentials work perfectly from windows PC Any fix to this?Solved6.6KViews0likes12CommentsReadyNAS Pro 6 / OS6 6.2.4: fan warnig message
Hi, I have upgraded my Pro6 with OS 6.2.4 and all seems to be working well apart that each time I boot the NAS, after 1 or 2 minutes, I received the following warning message in the log: Fan 'Fan' in enclosure 'Internal' speed is below threshold. (0 rpm). Please can someone guide me how I might be able to resolve this issue? Thank you!3.6KViews0likes5CommentsShare locked: unable to delete it
I have a share named "torrents". Under "/data/._share" folder it was named "Torrents". I wanted to clean old leftover shares under /data/._share I deleted from windows explorer the /data/._share/Torrents folder Realizing that it affected my actual share, I wanted to save it. I went into SSH and did this: mv /data/torrents /data/torrents.bak Then deleted torrents share from the GUI and created a new share called "torrents" Now, the new created "torrents" share, still shows the old snapshots as if they existed, but I cannot delete or recover them I also cannot delete the share from GUI code error: Share 'torrents' cannot be delete. Try it again later. error code: 1004030000 Under SSH, I tried to empty it, rmdir the "torrents" folder..., no way: "Operation not permitted" Under SSH, I also see the "torrents.bak" folder, but I cannot delete it even that I deleted all its contents after I did a backup to PC: error folder not empty, despite ls -a shows no entries Now, I am screwed with a share named "torrents" and containing dummy snapshots that I cannot delete. Under SSH, there is also that "torrents.bak" folder, empty and that I cannot delete. I tried to reboot the NAS many times, no fix. I also tried chmod and chown on the folders, no way I see there is no volume scan now available by the way. Please help me fix this mess5.1KViews0likes9Comments