New drive not being used in RAID, management service offline

---

tommyhackett wrote:

I have rebooted, anything specifically to check? From my point of view the behaviour is no different after reboot

---

You are looking for evidence that the new drive has started resyncing.

If you can access https://nas-ip-address/admin you should see that in the status. Is that responding yet?

If not, then use ssh, and try another cat /proc/mdstat

The admin page is still offline. I just tried cat /proc/mdstat and got the exact same response as before

---

tommyhackett wrote:

The admin page is still offline. I just tried cat /proc/mdstat and got the exact same response as before

---

Try pulling the new drive, and then reboot.  Then see if the admin page comes back.

I just tried it, but can't access the admin page still

---

tommyhackett wrote:

I just tried it, but can't access the admin page still

---

Note the OS reinstall changes the admin password back to password.

If you log into ssh, and enter 

systemctl status apache2

do you see something that looks like this?

root@NAS:~# systemctl status apache2
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2022-05-24 17:30:18 EDT; 4 weeks 0 days ago
 Main PID: 5849 (apache2)
  ...

 The key bit is Active: active (running).

I do get this Active (running) info, but I also get some errors too:

root@TXHReadyNAS:~# systemctl status apache2
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Wed 2022-06-22 07:33:50 GMT; 3h 14m
in ago
  Process: 2077 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCE
SS)
  Process: 1831 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCES
S)
   CGroup: /system.slice/apache2.service
           ├─2100 /usr/sbin/apache2 -k start
           ├─2101 apache_log               
           ├─2102 apache_log               
           ├─2103 /usr/sbin/apache2 -k start
           ├─2105 /usr/sbin/apache2 -k start
           ├─2106 /usr/sbin/apache2 -k start
           ├─2107 /usr/sbin/apache2 -k start
           ├─2108 /usr/sbin/apache2 -k start
           ├─3245 /usr/sbin/apache2 -k start
           ├─3251 /usr/sbin/apache2 -k start
           ├─3252 /usr/sbin/apache2 -k start
           ├─3264 /usr/sbin/apache2 -k start
           ├─3271 /usr/sbin/apache2 -k start
           └─3272 /usr/sbin/apache2 -k start

Jun 22 07:46:12 TXHReadyNAS apache2[2105]: [cgi:error] [pid 2105] [client 192.168.68.101:50045] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:14 TXHReadyNAS apache2[3264]: [cgi:error] [pid 3264] [client 192.168.68.101:50047] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:16 TXHReadyNAS apache2[3271]: [cgi:error] [pid 3271] [client 192.168.68.101:50049] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:18 TXHReadyNAS apache2[3264]: [cgi:error] [pid 3264] [client 192.168.68.101:50052] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:21 TXHReadyNAS apache2[3271]: [cgi:error] [pid 3271] [client 192.168.68.101:50059] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:23 TXHReadyNAS apache2[3272]: [cgi:error] [pid 3272] [client 192.168.68.101:50065] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:25 TXHReadyNAS apache2[3271]: [cgi:error] [pid 3271] [client 192.168.68.101:50072] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:25 TXHReadyNAS apache2[3272]: [cgi:error] [pid 3272] [client 192.168.68.101:50073] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/
Jun 22 07:46:27 TXHReadyNAS apache2[3271]: [cgi:error] [pid 3271] [client 192.168.68.101:50091] AH01215: Co
nnect rddclient failed: /frontview/lib/dbbroker.cgi, referer: https://192.168.68.108/admin/

Not really sure, but I think those errors indicate that the ReadyNAS application hasn't fully started.

Do you have a backup of your data (other than the time machine backups?)  If you don't, then I suggest doing that.

After that, you could try doing an OS reinstall from the boot menu.  That will also

• reset the admin password to password
• reset the network interface to use DHCP with no bonding (likely already is set up that way)
• disable volume quota (which can be re-enabled on the volume settings wheel).

I don't have a recent backup to an external drive. I would like to take one but I'm not sure how as I've always used the admin GUI for that.

I have tried the OS reinstall before creating the post on this forum but there was no change in behaviour.  Also, more recently I tried downgrading to firmware 6.10.5 using steps I saw elsewhere on the forum:

cd /root
wget https://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNASOS-6.10.5-arm.zip
unzip ReadyNASOS-6.10.5-arm.zip
echo /root/ReadyNASOS-6.10.5-arm.img > /etc/.flash_update
reboot

But it didn't help

---

tommyhackett wrote:

I don't have a recent backup to an external drive. I would like to take one but I'm not sure how as I've always used the admin GUI for that.

 

---

How is the external drive formatted?  Does it mount when you connect it to your PC?

It doesn't mount when I connect it to my mac. I think the format is USB External Physical Disk • GUID Partition Map

---

tommyhackett wrote:

It doesn't mount when I connect it to my mac. I think the format is USB External Physical Disk • GUID Partition Map

---

What matters here is the file system - NTFS, BTRFS, EXT, FAT32, etc.

Looks like you might be using a file system that the Mac can't read.  Once we get past your main problem, you might want to fix that - backups you can't access on your other devices aren't worth very much.

Can you access the shares with finder?

I can access the shares from ReadyNAS in my Finder yes, it works via AFP

---

tommyhackett wrote:

I can access the shares from ReadyNAS in my Finder yes, it works via AFP

---

Ok.

One option is to make a fresh backup from the Mac - either to its local disk (if there is enough room) or to an external disk that is formatted for the Mac.  FreeFileSync is one tool that could be useful here (there are likely others).

You could also connect your existing backup disk to the NAS USB port, and then see if it mounts.  If it does, it is possible to update the backup manually using the linux CP command.  This could be quicker, but you'd still have a backup you can only access on the NAS.

I think I'd prefer to backup the NAS to the external drive using the NAS USB port. Because if I can't fix this NAS then I would need to buy a new one soon any way. I've connected it, how can I tell if its mounted?

---

tommyhackett wrote:

 Because if I can't fix this NAS then I would need to buy a new one soon any way. 

---

One aspect here is that you could end up replacing it with a different vendor's NAS.  New ReadyNAS are very scarce - although Netgear hasn't announced anything, many here (including me) think that Netgear has exited the NAS business.  They haven't introduced a new platform in 5 years.

---

tommyhackett wrote:

I've connected it, how can I tell if its mounted?

---

Just entering mount in ssh will show you all the mounts - the USB drive should be on the list (which might be pretty long).  This will also tell you the file system.

FWIW, mount | grep -v md127 | grep -i "/dev/" will shorten the list.

I guess it doesn't show here? :

root@TXHReadyNAS:~# mount | grep -v md127 | grep -i "/dev/"
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600,ptmxmode=000)
/dev/md0 on / type ext4 (rw,noatime,nodiratime,data=ordered)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
mqueue on /dev/mqueue type mqueue (rw,noatime,nodiratime)

root@TXHReadyNAS:~# mount
udev on /dev type devtmpfs (rw,noatime,nodiratime,size=10240k,nr_inodes=187949,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600,ptmxmode=000)
/dev/md0 on / type ext4 (rw,noatime,nodiratime,data=ordered)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime,nodiratime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime,nodiratime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime,nodiratime,size=516520k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,devices)
mqueue on /dev/mqueue type mqueue (rw,noatime,nodiratime)
configfs on /sys/kernel/config type configfs (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,noatime,nodiratime)
/dev/md127 on /data type btrfs (rw,noatime,nodiratime,nodatasum,nospace_cache,subvolid=5,subvol=/)
/dev/md127 on /home type btrfs (rw,noatime,nodiratime,nodatasum,nospace_cache,subvolid=256,subvol=/home)
/dev/md127 on /apps type btrfs (rw,noatime,nodiratime,nodatasum,nospace_cache,subvolid=257,subvol=/.apps)

---

tommyhackett wrote:

I guess it doesn't show here? :

 

---

Correct.

Try 

for devlink in /dev/disk/by-id/usb*; do readlink -f ${devlink}; done

This should tell you the device name (sdxx) if the system has found the USB drive.

If it has, then you can manually mount it - for instance

mount /dev/sdxx /mnt

should mount device sdxx on /mnt

Looks like that gets me two results

root@TXHReadyNAS:~# for devlink in /dev/disk/by-id/usb*; do readlink -f ${devlink}; done
/dev/sdc
/dev/sdc1

How can I know which one to use?

Ah, I saw elsewhere it should be sdc1
I tried mounting but got

mount: unknown filesystem type 'ntfs'

Thought I might be able to install ntfs-3g but got an error

root@TXHReadyNAS:~# apt-get install ntfs-3g
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ntfs-3g : Depends: libgcrypt11 (>= 1.4.5) but it is not installable
           Depends: libgnutls26 (>= 2.12.17-0) but it is not installable
E: Unable to correct problems, you have held broken packages.

---

tommyhackett wrote:

Ah, I saw elsewhere it should be sdc1
mount: unknown filesystem type 'ntfs'

---

Interesting.  You should be able to see the backup on a mac then (probably just read-only though).

Try

mount -t ufsd /dev/sdc1 /mnt

ufsd is the package that Netgear uses for NTFS (which comes from Paragon I think).

Ah, this worked

mount -t ufsd /dev/sdc1 /mnt

So I can see all the files on there now. How should I go about removing them and copying all the files from my NAS onto there please?

---

tommyhackett wrote:

So I can see all the files on there now. How should I go about removing them and copying all the files from my NAS onto there please?

---

If you just want to update a backup of a share folder the drive, you can use 

cp -au /data/sourceshare /mnt

the -a option stands for archive, and it will recusively copy files and folders. The -u option stands for update - it will copy files that are missing on the destination, and files that are older on the destination.  It will not delete files that are no longer on the source.

Be careful to make sure the destination is always somewhere /mnt.  You don't want to accidentally fill the OS partition.

More information on this command is here:

• https://www.linuxtechi.com/cp-command-examples-linux-beginners/
• https://man7.org/linux/man-pages/man1/cp.1.html

Deleting files/folders can be done with the rm command. Recursive deletion of a folder is done with

rm -rf /mnt/foldername

Of course be very careful not to delete anything in /data or in the OS folders - only delete stuff in /mnt.

More information on the command is here:

• https://www.geeksforgeeks.org/rm-command-linux-examples/
• https://man7.org/linux/man-pages/man1/rm.1.html

When you are finished, you need to unmount the disk by entering

cd //
umount /mnt

Note the spelling of the second command - umount, not unmount.

The command will fail if you are already somewhere in the /mnt folder tree - the first command just makes sure that is not the case.

First I would like to remove the old backup and start fresh - there would be a lot of files on there that I've since deleted and no longer want.

I'm getting an error that I can't work out:

rm: cannot remove 'mnt/blablabla': Directory not empty

And this is happening a lot. It looks like it shouldn't be a permissions issue, because using ls -l I see owner is root and I'm logged in as root.

---

tommyhackett wrote:

I'm getting an error that I can't work out:

rm: cannot remove 'mnt/blablabla': Directory not empty

---

Are you using rm -rf?  

That's with rm -rf yes