NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
sudo: unable to write to /var/lib/sudo/ts/admin: No space left on device
I've SSHed into my NAS and got this message: sudo: unable to write to /var/lib/sudo/ts/admin: No space left on device This has all seemed to start after doing some tinkering with the Logitech Media Server which I now suspect, could have been installed incorrectly in the wrong location. If I run df -h the result is: Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 3.7G 4.0K 100% / tmpfs 491M 4.0K 491M 1% /dev/shm tmpfs 491M 3.7M 487M 1% /run tmpfs 246M 1.4M 244M 1% /run/lock tmpfs 491M 0 491M 0% /sys/fs/cgroup /dev/md127 2.8T 1.9T 855G 70% /data /dev/md127 2.8T 1.9T 855G 70% /home /dev/md127 2.8T 1.9T 855G 70% /apps If I attempt to logon via the ReadyNAS GUI I continually get asked for the user and password, entering admin and then password just loops back around to another dialogue box with the same request. Please reassure me that I haven't completely borked the ReadyNAS OS! 😳
Is 6.10.10 the end of the line?
I am a passive user and have 3 NAS units at home - RN102/RN104/RN316.All 3 have been updated to 6.10.10. I only use it as local storage so 6.10.10 works fine for me. Been solid and easy to use. Wondering if 6.10.10 is the final or will there me more releases in the future?Raid5 is broken and separate raid0 and raid1?
I made the raid5 with 6 disks and used for a year. Now I my RN316 is broken then I try to connect these disks to another linux. However I checked every disks, somehow there is raid0x5disks and raid1 x 1disk It looks like raid5 fall aparts into raid0 and raid1. Is it possible to use these as raid5 forcebly?? such as 5 drives, /dev/sdd3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 5cda431d:eb21dd6d:849d9d92:636a0c72 Name : 0a438048:FILES-1 Creation Time : Wed Jun 11 08:24:46 2025 Raid Level : raid0 Raid Devices : 5 Avail Dev Size : 15618351694 (7447.41 GiB 7996.60 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=264112 sectors, after=0 sectors State : clean Device UUID : 6ac2adc5:992e062a:7e8aa6d7:5885b27a Update Time : Wed Jun 11 08:24:46 2025 Bad Block Log : 512 entries available at offset 8 sectors Checksum : d77027db - correct Events : 0 Chunk Size : 64K Device Role : Active device 1 Array State : AAAAA ('A' == active, '.' == missing, 'R' == replacing) one drive is like this, sudo mdadm --examine /dev/sdf3 /dev/sdf3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 38792c55:ec30a05d:ef132979:1abc74c9 Name : 0a438048:FILES-0 Creation Time : Wed Jun 11 07:15:43 2025 Raid Level : raid1 Raid Devices : 1 Avail Dev Size : 15618351680 (7447.41 GiB 7996.60 GB) Array Size : 7809175808 (7447.41 GiB 7996.60 GB) Used Dev Size : 15618351616 (7447.41 GiB 7996.60 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=263912 sectors, after=64 sectors State : clean Device UUID : df652525:c37b0a23:214456ea:deba215a Update Time : Thu Jun 12 02:46:05 2025 Bad Block Log : 512 entries available at offset 264 sectors Checksum : 295491c1 - correct Events : 2 Device Role : Active device 0 Array State : A ('A' == active, '.' == missing, 'R' == replacing) Swap area(/dev/sd*2) somehow keep raid10 sudo mdadm --examine /dev/sdf2 /dev/sdf2: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 860482db:bc8f628a:3b14dc96:8fc010a0 Name : 0a438048:1 Creation Time : Wed Jun 11 07:15:43 2025 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1044480 (510.00 MiB 534.77 MB) Array Size : 1566720 (1530.00 MiB 1604.32 MB) Data Offset : 4096 sectors Super Offset : 8 sectors Unused Space : before=4016 sectors, after=0 sectors State : clean Device UUID : 7300c357:529e4410:a14c33fc:e11bb3c2 Update Time : Wed Jun 11 17:09:12 2025 Bad Block Log : 512 entries available at offset 16 sectors Checksum : a8d95fb5 - correct Events : 19 Layout : near=2 Chunk Size : 512K Device Role : Active device 0 Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)ReadyNAS104 assistance needed
Hi, I have an old ReadyNAS 104 that apparently just crashed. I can get it to reboot and I can access it from a browser but it shows the volume as new? I have 4 - Toshipba 3 TB drives in a RAID 4 configuration. I have attempted to access the BOOT menu by rebooting the NAS with my finger on the power button but that does not appear to work. When I look at the drives they are all showing green but "new" and the volume I had for many years is now gone. Please help
ReadyNAS Pro 6 - Stuck on booting while checking fs
I have searched for similar errrors on here, but none seem to either work or be related as to my situation. My Pro 6 just started to freeze a couple days ago while it was running. I had updated it to OS6 a long while ago. Thinking it might just be a random error, I restarted the device and now it gets to the checking root fs and stops around half way (sometimes more or less). I have tried the following: OS Reinstall - Completes and boots to same percentage. Disk Tests ran fine and rebooted itself (though now this is no longer an option in the boot menu) USB Recovery ran and shutdown. Boots back to same percentage. Tech Support mode works Tried start_raids and it seemed to see every drive. Ran some mdadm commands to examine the drives and array as found in other posts on here with no glaring errors found. Running a 'smartctl -t long /dev/sda' now. Not sure what else to do to get it to boot so I can get my files (prefer it to continue being useful but can get soem other NAS and move my data as long as I can get to it). Thoughts/ideas/help? Thank you.No Volumes Exist Suddenly - ReadyNas 10400 - HELP!
I was in the middle of running a full backup of my readynas 10400 system yesterday and something has gone wrong. Now I cannot access the shares, and the system is showing the message that 'No Volumes Exist' and telling me to remove inactive volumes in order to use the disks. It was set up as a Raid 5 array using 4 discs, and one of them failed the other day, hence my decision to run a backup. I do not have a full backup of all the data so I need to get access back into those shares. I am at a loss as to what to do. I've replaced the failed drive with a new one but still no joy. From what I have read this probably means that the array is out of sync but I don't know how to get it to resyncronise. I have downloaded the logs so can supply them if required. I was in the process of setting up a robust backup system when this happened, so I hadn't managed to back it all up yet. Help, basically.Credentials for terminal login on ReadyNAS 212 after Management Service is offline
Been trying to restore access to the admin page of my ReadyNAS 212. Not sure what caused the web interface to quit working. I can see the internal drives but not the external drives in Windows file explorer. I tried an OS reinstall. Now I'm trying to login using terminal after setting the device into tech support mode. Password has been reset after OS install to admin\password but the credentials don't work for terminal. Credentials work for Raidar. I've also tried root for the ID and different old netgear passwords seen on this forum. I don't want to reset the firmware unless I absolutely have to as the config files I have backed up are several years old. Any suggestions out there? JimRemove Inactive Volumes to sue the disk - RN316
Reading this forum, it sounds like this is not an uncommon situation... I recently had a hard drive fail on my RN316 - replaced it, knowing another was expected to fail soon, and about 2 hours after the resync of the first drive completed, the second drive failed. When I replaced that drive, it did not automatically resync. When I finally managed to get the resync to happen, I was presented with the attached image in the Volumes page - warnings about removing inactive volumes to use disks, and the red drives... I have managed to assemble the arrays /dev/md127 and /dev/md126 - however btrfs is giving me the following when I attempt to mount /dev/md127 mount: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Does this sound like it's salvageable by a rebuild of the NAS, or should I be handing the whole thing over to a data recovery expert? (unfortunately, I have no backup - I was naive and trusted RAID5 with the bulk of the data on this NAS - I won't be doing that again)