Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cannot clear error message on pool with clean scrub #8275

Closed
montanaviking opened this issue Jan 12, 2019 · 3 comments
Closed

cannot clear error message on pool with clean scrub #8275

montanaviking opened this issue Jan 12, 2019 · 3 comments

Comments

@montanaviking
Copy link

montanaviking commented Jan 12, 2019 •
edited by loli10K
Loading

System information

Type Version/Name
Distribution Name Ubuntu Linux
Distribution Version 18.04
Linux Kernel 4.15.0-43-generic #46-Ubuntu SMP
Architecture Intel® Xeon(R) CPU E5-2630 v2 @ 2.60GHz × 12
ZFS Version ZFS: Loaded module v0.7.5-1ubuntu16.4, ZFS pool version 5000, ZFS filesystem version 5
SPL Version 0.7.5-1ubuntu1

Describe the problem you're observing

Cannot clear ZFS pool errors
This pool is an external USB-3 connected backup hard drive
I have it configured with copies=2 for soft-error/bad sector redundancy on disk.

Describe how to reproduce the problem

One day I discovered the error message on said pool:

# zpool status -v
errors: Permanent errors have been detected in the following files:
        <metadata>:<0x1>

Actions:

  1. scrub this drive
    Results after scrub:
pool: zbackupc1
 state: ONLINE
status: One or more devices has experienced an error resulting in data
	corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
	entire pool from backup.
   see: http://zfsonlinux.org/msg/ZFS-8000-8A
  scan: scrub repaired 0B in 23h40m with 0 errors on Fri Jan 11 20:53:32 2019
config:

	NAME        STATE     READ WRITE CKSUM
	zbackupc1   ONLINE       0     0     0
	  sdf       ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

        <metadata>:<0x1>
  1. reboot computer and
# zpool clear -F zbackupc1

Same errors as above
3. export and import zbackupc1
Same errors as above.

  1. performed a SMART check on the USB drive in question:
d# smartctl -d sat -a -T verypermissive -s on /dev/sde
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error aborted command

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Sat Jan 12 15:20:40 2019 PST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

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:      (  24)	The self-test routine was aborted by
					the host.
Total time to complete Offline 
data collection: 		(  120) 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.
					No General Purpose Logging support.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 531) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       8700
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       7525
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       6518
 10 Spin_Retry_Count        0x0033   250   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       179
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       857
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       54
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       7525
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       31 (Min/Max 13/42)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       3
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   095   095   000    Old_age   Always       -       2306
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       545
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 3
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3 occurred at disk power-on lifetime: 2731 hours (113 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 50 00 3f d1 48 40   at LBA = 0x0048d13f = 4772159

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 c0 80 d0 48 40 00      02:00:29.100  WRITE DMA EXT
  35 00 c8 b8 cf 48 40 00      02:00:29.100  WRITE DMA EXT
  35 00 e0 d8 ce 48 40 00      02:00:29.100  WRITE DMA EXT
  35 00 e0 f8 cd 48 40 00      02:00:29.099  WRITE DMA EXT
  35 00 f0 08 cd 48 40 00      02:00:29.099  WRITE DMA EXT

Error 2 occurred at disk power-on lifetime: 2730 hours (113 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 50 00 2f b6 04 40   at LBA = 0x0004b62f = 308783

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 d8 58 b5 04 40 00      01:56:38.422  WRITE DMA EXT
  25 00 10 20 c0 cc 40 00      01:56:38.422  READ DMA EXT
  35 00 b0 a8 b4 04 40 00      01:56:38.422  WRITE DMA EXT
  35 00 10 98 b4 04 40 00      01:56:38.422  WRITE DMA EXT
  35 00 f0 a8 b3 04 40 00      01:56:38.421  WRITE DMA EXT

Error 1 occurred at disk power-on lifetime: 2730 hours (113 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 50 00 77 e7 89 40   at LBA = 0x0089e777 = 9037687

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 e8 90 e6 89 40 00      01:54:29.355  WRITE DMA EXT
  35 00 a0 f0 e5 89 40 00      01:54:29.354  WRITE DMA EXT
  35 00 80 70 e5 89 40 00      01:54:29.354  WRITE DMA EXT
  35 00 f0 80 e4 89 40 00      01:54:29.354  WRITE DMA EXT
  35 00 b8 c8 e3 89 40 00      01:54:29.353  WRITE DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               80%      4484         -
# 2  Extended offline    Interrupted (host reset)      80%      2743         -
# 3  Extended offline    Aborted by host               90%      2590         -
# 4  Extended offline    Aborted by host               90%      2589         -
# 5  Extended offline    Interrupted (host reset)      90%      2557         -
# 6  Extended offline    Aborted by host               90%      1548         -
# 7  Extended offline    Aborted by host               90%       449         -
# 8  Extended offline    Aborted by host               10%       445         -
# 9  Extended offline    Aborted by host               90%         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.

Do you think there is actually a problem with this pool when scrub showed no errors?

Thanks in advance!
Phil
@montanaviking
Copy link
Author

Moreover, it appears from SMART that my external USB drive had a write error, Google shows this is likely due to bad USB cable and/or USB controller. But I'm still wondering how to clear the ZFS errors? It appears that the drive is working since a scrub showed no errors? Thanks, Phil

@richardelling
Copy link
Contributor

Know that the error log contains messages from the current and previous scrub. If the data is recovered, then 2 scrubs can be needed to clear the log message. If the data cannot be recovered, then the message will remain. See also zpool events for detailed information.

@montanaviking
Copy link
Author

It appears that a second scrub solved the problem. I might also have a problem with my USB controller and/or cable. Thanks for you help! Phil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richardelling @montanaviking