New drive not being used in RAID, management service offline
Im using a ReadyNAS202 running 2 x 2TB WD red drives
I noticed my Time Machine backups were starting to fail and then realised one of my disks was degraded. I replaced that with a new one earlier today and now both disks are fine, but Raidar diagnostics is showing I have some serious sounding issues now:
==============================================
Volume root is degraded Volume 1 is inactive Volume data is degraded
==============================================
And I can't load the management service in the browser. What is surprising to me is that time machine backups from my mac are continuing to be successful.
I've tried a firmware reinstall but that hasn't helped.
mdstat.log seems to show that only one of my drives is being used in raid1?
==============================================
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid1 sda3[1] 1948662784 blocks super 1.2 [2/1] [_U]
md1 : active raid1 sda2[0] 523264 blocks super 1.2 [2/1] [U_]
md0 : active raid1 sda1[1] 4190208 blocks super 1.2 [2/1] [_U]
==============================================
Both disks are showing as fine in volume.logs but then only one shows in my Raid Arrays, is this highlighting the issue?
md1 : active raid1 sda2[0] 523264 blocks super 1.2 [2/1] [U_]
md0 : active raid1 sda1[1] 4190208 blocks super 1.2 [2/1] [_U]
unused devices: <none>
======
To use smartctl, would the below command be correct? As I'm not clear on how to specify the device type. The response I get at this point is the same for sda and sdb
======
root@TXHReadyNAS:~# smartctl --all dev/sdb smartctl 6.6 2017-11-05 r4594 [armv7l-linux-4.4.218.alpine.1] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
dev/sdb: Unable to detect device type Please specify device type with the -d option.
To use smartctl, would the below command be correct? As I'm not clear on how to specify the device type. The response I get at this point is the same for sda and sdb
======
root@TXHReadyNAS:~# smartctl --all dev/sdb
Try
smartctl -x /dev/sdb
Note you left out the / before dev in your earlier command.
-x will give you a lot of info, including any errors logged by the drive.
Re: New drive not being used in RAID, management service offline
Ah thanks, here's what I got:
======
root@TXHReadyNAS:~# smartctl -x /dev/sdb smartctl 6.6 2017-11-05 r4594 [armv7l-linux-4.4.218.alpine.1] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION === Device Model: WDC WD20EFZX-68AWUN0 Serial Number: WD-WX42D61CHAJ5 LU WWN Device Id: 5 0014ee 269aab111 Firmware Version: 81.00B81 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Jun 21 12:31:15 2022 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED
General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (20880) seconds. Offline data collection capabilities: (0x11) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 224) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported.
SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/65 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (14)
Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 18 --- Lifetime Power-On Resets 0x01 0x010 4 15 --- Power-on Hours 0x01 0x018 6 5 --- Logical Sectors Written 0x01 0x020 6 0 --- Number of Write Commands 0x01 0x028 6 13030 --- Logical Sectors Read 0x01 0x030 6 857 --- Number of Read Commands 0x01 0x038 6 54000000 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 15 --- Spindle Motor Power-on Hours 0x03 0x010 4 0 --- Head Flying Hours 0x03 0x018 4 19 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 16 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 34 --- Current Temperature 0x05 0x010 1 - --- Average Short Term Temperature 0x05 0x018 1 - --- Average Long Term Temperature 0x05 0x020 1 34 --- Highest Temperature 0x05 0x028 1 31 --- Lowest Temperature 0x05 0x030 1 - --- Highest Average Short Term Temperature 0x05 0x038 1 - --- Lowest Average Short Term Temperature 0x05 0x040 1 - --- Highest Average Long Term Temperature 0x05 0x048 1 - --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 65 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 44 --- Number of Hardware Resets 0x06 0x010 4 13 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 3 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 53960 Vendor specific
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)
...
Re: New drive not being used in RAID, management service offline
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:
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.
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.
Re: New drive not being used in RAID, management service offline
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?
