NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
eduj7im
Feb 09, 2020Aspirant
Ultra 4 on Safe mode, No Volume exist
Hi Team, I'm using a Ultra 4 Readynas on OS 6.10 4x2TB drives I recently have a power outage at my home and all of a sudden my NAS boots on safe mode. Its boots okay, goes to checking FS the...
StephenB
Feb 10, 2020Guru - Experienced User
eduj7im wrote:
I've removed the 2nd drive just to take a photo of it and mount it back again
and now 2nd drive is resyncing any thoughts? on the admin page it says there's 11 ATA errors
Did you hot-insert the drive? (FWIW, you shouldn't have).
eduj7im
Feb 10, 2020Aspirant
Thanks for the response Stephen,
The NAS was shutdown before removing and reinserting it.
- StephenBFeb 10, 2020Guru - Experienced User
eduj7im wrote:
Thanks for the response Stephen,
The NAS was shutdown before removing and reinserting it.
Odd that it resynced then.
FWIW, in order to mount the volume you need both a healthy RAID array and a healthy file system.
It would be good to download the log zip file, and look at disk health,and at mdstat.log.
- eduj7imFeb 10, 2020Aspirant
Hi StephenB
Thanks for the response.
Please Correct me if im wrong,
Looks like the drives are still healthy. How can I check if the FS is healthy?
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid10 sdd2[3] sdc2[2] sdb2[1] sda2[0]
1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[4]
5845994496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md0 : active raid1 zram0[0]
4190208 blocks super 1.2 [1/1] [U]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Mon Feb 10 15:13:15 2020
Raid Level : raid1
Array Size : 4190208 (4.00 GiB 4.29 GB)
Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
Raid Devices : 1
Total Devices : 1
Persistence : Superblock is persistentUpdate Time : Mon Feb 10 15:15:34 2020
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0Consistency Policy : unknown
Name : 37c0ff7c:0 (local to host 37c0ff7c)
UUID : 635c45b3:7a11fd15:43d67b01:fa98d287
Events : 2Number Major Minor RaidDevice State
0 250 0 0 active sync /dev/zram0
/dev/md/data-0:
Version : 1.2
Creation Time : Sat Feb 23 04:13:35 2019
Raid Level : raid5
Array Size : 5845994496 (5575.17 GiB 5986.30 GB)
Used Dev Size : 1948664832 (1858.39 GiB 1995.43 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistentUpdate Time : Mon Feb 10 15:13:52 2020
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0Layout : left-symmetric
Chunk Size : 64KConsistency Policy : unknown
Name : 37c0ff7c:data-0 (local to host 37c0ff7c)
UUID : 55b1fa5f:47eeba04:c7f50a68:191a6770
Events : 3259Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
4 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3- StephenBFeb 11, 2020Guru - Experienced User
You could try running btrfs check /dev/md127 from ssh.
There is risk in using the repair option, but with no options the command won't try to repair anything - it should just analyze.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!