September 28, 20241 yr I just picked up two 12 TB Ultrastar HC520 manufacturer recertified drives from ServerPartDeals. I intend for one of them to replace my existing 4TB parity, and the other to be added as an array drive (replacing a couple of 13 year old WD Black drives). I am able to format both of them in Unassigned devices, and have run 3 preclear cycles on one of them. However, when I click the mount button in Unassigned Devices, I get the following error message pop up: FAIL! Device '/dev/sdd' failed to mount. Check the syslog for details. The "MOUNT" button then changes to "UNMOUNT" as if it successfully mounted. If I look in the log it looks like it successfully mounted: Sep 28 14:46:49 Tower unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks/5PKPMMDB'... Sep 28 14:46:49 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdd1' '/mnt/disks/5PKPMMDB' Sep 28 14:46:49 Tower kernel: XFS (sdd1): Mounting V5 Filesystem Sep 28 14:46:50 Tower kernel: XFS (sdd1): Ending clean mount Sep 28 14:46:50 Tower unassigned.devices: Successfully mounted '/dev/sdd1' on '/mnt/disks/5PKPMMDB'. Sep 28 14:46:50 Tower unassigned.devices: Adding SMB share '5PKPMMDB'. I am also able to enable a disk share on each of them, and have successfully copied a large blu-ray .mkv file to each of them and played it from those drives. I also google searched the error message, and got a result saying that they were able to fix a similar issue by running xfs_repair -L /dev/sdd in the console. When I run that, I get an interesting result: root@Tower:~# xfs_repair -L /dev/sdd Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .......................................................................................................... .......................................................................................................... I guess my question is, do I have a problem here? Or am I good to go ahead and use these drives? If I'm good to go, why are these errors happening, because it certainly seems like something is wrong. Edited September 28, 20241 yr by Ccheese4
September 28, 20241 yr Go to Tools->PHP Settings and see if there are PHP warnings. That can cause a mount fail message. Also use the UD disk check to check the disk.
September 28, 20241 yr Author 48 minutes ago, dlandon said: Go to Tools->PHP Settings and see if there are PHP warnings. That can cause a mount fail message. Also use the UD disk check to check the disk. Thanks for the response. I don't have PHP Settings under Tools. Is this new for 6.12? I'm still running 6.11.3, as I haven't had time to deal with upgrading (and I read about some issues when 6.12 first launched). Looks like those are mostly fixed now, so I should probably update to the latest since it's been a year... The only UD check I can see is the little check box next to my partitions that is labeled "File System Check". Is this the UD Check you were referring to? Clicking that gives the following output: FS: xfs Executing file system check: /sbin/xfs_repair -n '/dev/sdd1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 2 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 4 - agno = 3 - agno = 0 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. No file system corruption detected!
September 28, 20241 yr Community Expert 50 minutes ago, Ccheese4 said: Clicking that gives the following output: Filesystem doesn't need repairing. FYI this will never work, you were missing the partition: 3 hours ago, Ccheese4 said: xfs_repair -L /dev/sdd And you should only use -L if asked, so it would be: xfs_repair /dev/sdd1
September 28, 20241 yr Author thanks. So do you think these drives are good? I'm definitely not as well versed as you guys are. Just trying to make sure before I commit one to my parity.
September 29, 20241 yr Community Expert 8 hours ago, Ccheese4 said: So do you think these drives are good? The filesystem looks OK, for the drive you would need to post the SMART report.
September 30, 20241 yr Author On 9/29/2024 at 3:05 AM, JorgeB said: The filesystem looks OK, for the drive you would need to post the SMART report. Report is below. Shows no errors. It's just making me nervous because I don't know what's causing the mounting errors, but maybe it's nothing to worry about. smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: HGST Ultrastar DC HC520 (He12) Device Model: HGST HUH721212ALE600 Serial Number: 5PKPMMDB LU WWN Device Id: 5 000cca 291f41bfa Firmware Version: LEBDT3P2 User Capacity: 12,000,138,625,024 bytes [12.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.3/5405 ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Sep 30 07:02:59 2024 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 87) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. 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: (1296) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance P-S--- 132 132 054 - 96 3 Spin_Up_Time POS--- 169 169 024 - 404 (Average 374) 4 Start_Stop_Count -O--C- 100 100 000 - 10 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate PO-R-- 100 100 067 - 0 8 Seek_Time_Performance P-S--- 140 140 020 - 15 9 Power_On_Hours -O--C- 100 100 000 - 65 10 Spin_Retry_Count PO--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 10 22 Helium_Level PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 100 100 000 - 12 193 Load_Cycle_Count -O--C- 100 100 000 - 12 194 Temperature_Celsius -O---- 166 166 000 - 36 (Min/Max 24/52) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0 241 Total_LBAs_Written -O--C- 100 100 000 - 3573588332 242 Total_LBAs_Read -O--C- 100 100 000 - 90313589 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 255 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 5501 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x12 GPL R/O 1 SATA NCQ Non-Data log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x15 GPL R/W 1 Rebuild Assist log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 256 Current Device Internal Status Data log 0x25 GPL R/O 256 Saved Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa6 GPL VS 1 Device vendor specific log 0xb2 GPL VS 688 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 63 - # 2 Short offline Completed without error 00% 0 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 36 Celsius Power Cycle Min/Max Temperature: 24/39 Celsius Lifetime Min/Max Temperature: 24/52 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (77) Index Estimated Time Temperature Celsius 78 2024-09-30 04:55 36 ***************** ... ..(126 skipped). .. ***************** 77 2024-09-30 07:02 36 ***************** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 10 --- Lifetime Power-On Resets 0x01 0x010 4 65 --- Power-on Hours 0x01 0x018 6 3573588332 --- Logical Sectors Written 0x01 0x020 6 3490055 --- Number of Write Commands 0x01 0x028 6 90313589 --- Logical Sectors Read 0x01 0x030 6 154902 --- Number of Read Commands 0x01 0x038 6 236511150 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 65 --- Spindle Motor Power-on Hours 0x03 0x010 4 65 --- Head Flying Hours 0x03 0x018 4 12 --- 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 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 36 --- Current Temperature 0x05 0x010 1 37 N-- Average Short Term Temperature 0x05 0x018 1 - N-- Average Long Term Temperature 0x05 0x020 1 52 --- Highest Temperature 0x05 0x028 1 24 --- Lowest Temperature 0x05 0x030 1 46 N-- Highest Average Short Term Temperature 0x05 0x038 1 25 N-- Lowest Average Short Term Temperature 0x05 0x040 1 - N-- Highest Average Long Term Temperature 0x05 0x048 1 - N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- 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 1 --- Number of Hardware Resets 0x06 0x010 4 2 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged 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 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 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
September 30, 20241 yr Community Expert Disk looks fine, almost certainly just a filesystem problem, most often they are caused by an unclean shutdown/unmount
October 1, 20241 yr Author 12 hours ago, JorgeB said: Disk looks fine, almost certainly just a filesystem problem, most often they are caused by an unclean shutdown/unmount Ok thanks! Sorry, not that I don't believe you. I'm just trying to understand. So if I delete the partition and reformat it, it still throws that error from my first message (failure to mount) when I attempt to mount it in UD, even though it actually does mount. Why is that? If I've just reformatted without an unclean shutdown, it should be a "fresh" filesystem right?
October 1, 20241 yr Community Expert 5 hours ago, Ccheese4 said: So if I delete the partition and reformat it, it still throws that error from my first message (failure to mount) Where do you see that? It's not a stock Unraid message, and it's failing to mount the whole disk, the filesystem is using a partition, /dev/sdd1, not /dev/sdd
October 1, 20241 yr Author 14 hours ago, JorgeB said: Where do you see that? It's not a stock Unraid message, and it's failing to mount the whole disk, the filesystem is using a partition, /dev/sdd1, not /dev/sdd Well, it was an error that popped up (similar to the window that pops up to have you type 'Yes' to format a drive) after I clicked "Mount" on the drive in UD. The message would say "FAIL! Device '/dev/sdd' failed to mount. Check the syslog for details.". However, I just so happened to update to 6.12.13 last night. Now when I click Mount, it mounts without any drama or error message. So I guess we can just chalk this up to an Unraid bug with the old version? Thanks for all your help though!
October 2, 20241 yr Community Expert 9 hours ago, Ccheese4 said: So I guess we can just chalk this up to an Unraid bug with the old version? At most, you can consider it a UD plugin issue, if it happens again, report it in the existing plugin support thread.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.