NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
data degraded, however resync completed
I was upgrading other devices drives and I swapped a good working drive in my ultra 4 (6.6.1), the volume resynced completed, however then it says degraded.
All drive lights are green on the volume page.
No disk errors are on the log.
I powered down, let it sit a few minutes, then booted up, with the same data degraded, no errors in the logs.
I started a scrub, which is progressing very slowly, and I am beginning to regret.
I would pull and re-add the recently added drive, however I don't want to assume that is the drive which is causing the degrade.
Now that I started the scrub, I am unable to download the logs (yeah I should have done that first...).
My questions are:
How can I safely stop the scrub that is in progress?
How do I determine what/which drive is causing the volume to be degraded? (no errors in logs, all drives are green on the volumes page)
Sounds like removing disk 3 and readding it after a minute would be the way forward, yes.
It's weird that it failed to rotate the journal when there is so much free space on the 4GB root volume.
5 Replies
Replies have been turned off for this discussion
well i found the answer to the scrub, there is an X on the progress bar that will stop the scrub.
i was also able to download the logs and I'm looking through them to see if anything stands out
I got ~2k lines of this;
[Tue Jan 10 19:06:06 2017] systemd-journald[1349]: Failed to write entry (19 items, 549 bytes), ignoring: Input/output error [Tue Jan 10 19:06:06 2017] systemd-journald[1349]: Failed to rotate /var/log/journal/f1dc4eef9ce14c55ad1d8a43499867d2/system.journal: No space left on device
which doesn't look good
Physical disk 3 is the one I had swapped, both disks are good, I just swapped a seagate 4tb to a hitachi 4tb, all disks are now hitachi 4tb.
From mdstat.log
md126 : active raid5 sda4[0] sdd4[3] sdb4[1] 5860124736 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [UU_U] md127 : active raid5 sda3[4] sdd3[7] sdc3[8] sdb3[5] 5845988352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] bitmap: 0/15 pages [0KB], 65536KB chunkIt looks like I am missing disk 3 (sdc4) on md126?
/dev/md/data-1: Version : 1.2 Creation Time : Wed Jul 20 14:21:51 2016 Raid Level : raid5 Array Size : 5860124736 (5588.65 GiB 6000.77 GB) Used Dev Size : 1953374912 (1862.88 GiB 2000.26 GB) Raid Devices : 4 Total Devices : 3 Persistence : Superblock is persistent Update Time : Tue Jan 10 20:53:03 2017 State : clean, degraded Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : 3faa22ed:data-1 (local to host 3faa22ed) UUID : 79643dbe:e57091f6:8324232a:d425c1a0 Events : 9049 Number Major Minor RaidDevice State 0 8 4 0 active sync /dev/sda4 1 8 20 1 active sync /dev/sdb4 4 0 0 4 removed 3 8 52 3 active sync /dev/sdd4So, safe to remove, wait a minute, then re-add disk 3 ?
Or should I run some command to force resync on md126 ?
Sounds like removing disk 3 and readding it after a minute would be the way forward, yes.
It's weird that it failed to rotate the journal when there is so much free space on the 4GB root volume.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
