NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro6 fails to boot (at 98%, "Management service is offline") after hard shutdown
My ReadyNAS Pro 6 is using OS 6.10.10 - and had no issues in the past. Recently, I had to replace a disk (because it started to show problems): 3 TB -> 6 TB (WD). Replacing was no issue, syncing to...
WJ wrote:
I've only removed drive #1 (troubled 3TB) first and replaced it with a new 6 TB drive; then powered up. That would resulted in a sycn (took about 5h).
Only afterwards (and after having shutdown the Pro 6) I've added the additional 6 TB drive. That 2nd sync did not succeed.
The second drive would have needed TWO syncs one for the original 3 TB partition, and then a second sync to expand using the extra capacity. If the first sync succeeded, then it would be better to attempt to mount the volume with that disk install. It would need to be inserted with the NAS powered down though.
Without logs, we don't know what we are dealing with. It would be useful to see the disk partitioning, so if you could post the output of lsblk, that would be helpful.
WJ wrote:
Yes, I do have (weekly) backups but I'd like to avoid a factory reset.
While we might be able to get the volume mounted, there will be some corruption. The best path is to do the reset and restore the files from backup. In addition to getting you a clean system, it could well be the fastest path.
Update: it seems that /home is empty - also /home/admin does not exist
There are many UUID-named directories in the root directory - according to "ls -l" they are created in Dec 2017. But I've never seen them before.
WJ wrote:
Update: it seems that /home is empty - also /home/admin does not exist
Is the volume mounted? /home is a mount point for /data/home - so if the volume isn't there, /home will also be empty.
Do you have a backup of the files?
- Yes, I do have (weekly) backups but I'd like to avoid a factory reset.
Is there anything else I can try, first? mounted:
udev on /dev type devtmpfs (rw,noatime,nodiratime,size=10240k,nr_inodes=504246,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600,ptmxmode=000)
/dev/md0 on / type btrfs (rw,noatime,nodiratime,nospace_cache,subvolid=5,subvol=/)
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=1009832k)
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/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,memory)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,pids)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,perf_event)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,freezer)
debugfs on /sys/kernel/debug type debugfs (rw,noatime,nodiratime)
mqueue on /dev/mqueue type mqueue (rw,noatime,nodiratime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,noatime,nodiratime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
configfs on /sys/kernel/config type configfs (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,noatime,nodiratime)When you added the second 6TB drive, the NAS would need tweo re-syncs -- one to convert and expand the original 3TB RAID1 to a 6TB RAID5 and a second to add a 3TB RAID1 using the additional space on the two 3TB ones. Did you see two re-syncs complete, or just one. The message you get after the first can be misleading and it's easy to mistakenly believe the re-syncs are all completed.
StephenB wrote:
WJ wrote:Update: it seems that /home is empty - also /home/admin does not exist
Is the volume mounted? /home is a mount point for /data/home - so if the volume isn't there, /home will also be empty.
Do you have a backup of the files?
Hmm - just checked: I've only a pretty old manual backup (2020) and I should have also the incremental backup (using the scheduled backup job of the ReadyNAS Pro 6) but I've not confirmed whether that's really readable.
So, I'd really like to mount /data manually so see what's still there.
Should I insert all 3 disks (incl. the one which is not entirely synched) or should I only use the 2 disks which were previously used successfully?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
