snapraid + adding new drive

  • I don't see how without a way to narrow down what the issue is. Clearly the USB device being reset isn't a good sign. It could be bad controller, bad usb cable, bad drive. To find out which you need to be able to swap each out.

    well usb cables was changed, so i dont think its cable issue, HW odroid -> rpi was replaced....


    so using exclusion method ... remains only Controller of usb box or drives... as i dont have an option to replace/change usb box with controller is it possible at least check the drives -> then we can be 100% sure its controller, right?

  • I'd never say 100% but, yes, very very likely. Preferably you'd be able to check the drives outside the suspect enclosure but I've had individual ports on controllers go bad so if the same drive is the one having issues try changing the port it's on (changing the physical drive order in the bay). If the same bay is acting up then it's the controller but that one port. I've seen this a number of times.


    If SMART checks come back OK as well as badblock or bbf (self promotion) then while still possible to be a problem it is less likely.

  • It *could* be the OS drivers as well being flaky but that's going to be harder to show without having the exact same device to compare against. When I used USB3/eSATA enclosures I had 4 of the same so it was clear that one of them was physically bad vs a software bug. Though even then... it's plausible that the hardware issue could be worked around in software.


    It's complicated is what I'm getting at :)

  • I'd never say 100% but, yes, very very likely. Preferably you'd be able to check the drives outside the suspect enclosure but I've had individual ports on controllers go bad so if the same drive is the one having issues try changing the port it's on (changing the physical drive order in the bay). If the same bay is acting up then it's the controller but that one port. I've seen this a number of times.


    If SMART checks come back OK as well as badblock or bbf (self promotion) then while still possible to be a problem it is less likely.

    hi,
    what do you mean by BBF (Self promotion)?


    do you guys recommend some good enclosure for 4-5 drives with nice controller?

  • https://github.com/trapexit/bbf


    My own tool which is similar to badblocks.


    https://github.com/trapexit/me…ki/Real-world-deployments


    Those are the enclosures I used to use. They worked OK but I would have occasional issues that I simply don't have now with my HBA. I was using them over eSATA however so I can't speak to their USB stability. I know this isn't ideal but 1 to 1 drive to controller setup is probably better when using USB. Almost all sata -> usb bridges will reset the whole set of drives if something acts up. Was why I used eSATA.

  • If you (or anyone else) happen to be in the Manhattan/NYC area I've a few of those ICYCube's and a esata SansDigital I'm not using and willing to part with on the cheap.


    Regarding other chipsets... in my journeys it always seemed like every single enclosure had its haters. Very hard to suss out which were systemically bad and what were just one offs.

  • would be nice ... but i am located in Europe :(



    anyways new errors in dmesg after i run (output contains sdb) as label is sdb... so can be confusing ...
    fsck.ext4 -v -cf /dev/sde1


    e2fsck 1.43.4 (31-Jan-2017)
    Checking for bad blocks (read-only test): 87.80% done, 5:45:26 elapsed. (0/0/0 errors)
    87.80% done, 5:45:27 elapsed. (0/0/0 errors)
    87.80% done, 5:45:28 elapsed. (0/0/0 errors)
    done
    sdb: Updating bad block inode.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information



    sdb: ***** FILE SYSTEM WAS MODIFIED *****



    115513 inodes used (0.06%, out of 183148544)
    31882 non-contiguous files (27.6%)
    48 non-contiguous directories (0.0%)
    # of inodes with ind/dind/tind blocks: 0/0/0
    Extent depth histogram: 112815/2688
    688894149 blocks used (94.04%, out of 732566385)
    0 bad blocks
    91 large files



    95874 regular files
    19628 directories
    0 character device files
    0 block device files
    0 fifos
    0 links
    2 symbolic links (2 fast symbolic links)
    0 sockets
    ------------
    115504 files







    [217087.413302] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808258
    [217087.447952] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808258
    [217087.482877] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808262
    [217087.503562] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808262
    [217087.546546] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808257
    [217087.570059] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808257
    [217087.592536] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808260
    [217087.614416] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808260
    [217091.144361] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808258
    [217091.170173] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808262
    [217120.311089] EXT4-fs error: 2 callbacks suppressed
    [217120.311102] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808258
    [217120.336290] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808262
    [217120.358645] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808257
    [217120.380678] EXT4-fs error (device sde1): ext4_lookup:1594: inode #19800065: comm mergerfs: deleted inode referenced: 19808260



    i am going to execute smrtctl full test.

  • smartctl -t long from sde




    smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.19.75-v7l+] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org



    === START OF INFORMATION SECTION ===
    Model Family: Western Digital Red
    Device Model: WDC WD30EFRX-68EUZN0
    Serial Number: WD-WCC4N0TXA2EX
    LU WWN Device Id: 5 0014ee 2108f8e52
    Firmware Version: 82.00A82
    User Capacity: 3,000,592,982,016 bytes [3.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ACS-2 (minor revision not indicated)
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Fri Jan 17 13:07:19 2020 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: 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: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: (39120) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    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: ( 393) minutes.
    Conveyance self-test routine
    recommended polling time: ( 5) minutes.
    SCT capabilities: (0x703d) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
    3 Spin_Up_Time 0x0027 183 182 021 Pre-fail Always - 5808
    4 Start_Stop_Count 0x0032 088 088 000 Old_age Always - 12471
    5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
    7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
    9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 6001
    10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 16
    192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 4
    193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 24576
    194 Temperature_Celsius 0x0022 113 103 000 Old_age Always - 37
    196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
    200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0



    SMART Error Log Version: 1
    No Errors Logged



    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 5994 -
    # 2 Short offline Completed without error 00% 4890 -
    # 3 Short offline Completed without error 00% 5338 -
    # 4 Short offline Completed without error 00% 4621 -
    # 5 Short offline Completed without error 00% 3880 -
    # 6 Short offline Completed without error 00% 3139 -
    # 7 Short offline Completed without error 00% 2420 -
    # 8 Short offline Completed without error 00% 1676 -
    # 9 Short offline Completed without error 00% 959 -
    #10 Short offline Completed without error 00% 216 -



    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.

  • other errors in dmesg:



    [1082971.690389] EXT4-fs (sde1): error count since last fsck: 32
    [1082971.690418] EXT4-fs (sde1): initial error at time 1579211329: ext4_lookup:1594: inode 19800065
    [1082971.690466] EXT4-fs (sde1): last error at time 1579373719: ext4_lookup:1594: inode 19800065
    [1169480.550140] EXT4-fs (sde1): error count since last fsck: 32
    [1169480.550168] EXT4-fs (sde1): initial error at time 1579211329: ext4_lookup:1594: inode 19800065
    [1169480.550221] EXT4-fs (sde1): last error at time 1579373719: ext4_lookup:1594: inode 19800065
    [1255989.430415] EXT4-fs (sde1): error count since last fsck: 32
    [1255989.430443] EXT4-fs (sde1): initial error at time 1579211329: ext4_lookup:1594: inode 19800065
    [1255989.430493] EXT4-fs (sde1): last error at time 1579373719: ext4_lookup:1594: inode 19800065
    [1342498.280334] EXT4-fs (sde1): error count since last fsck: 32
    [1342498.280369] EXT4-fs (sde1): initial error at time 1579211329: ext4_lookup:1594: inode 19800065
    [1342498.280413] EXT4-fs (sde1): last error at time 1579373719: ext4_lookup:1594: inode 19800065
    [1429007.136022] EXT4-fs (sde1): error count since last fsck: 32
    [1429007.136053] EXT4-fs (sde1): initial error at time 1579211329: ext4_lookup:1594: inode 19800065
    [1429007.136096] EXT4-fs (sde1): last error at time 1579373719: ext4_lookup:1594: inode 19800065



    Basically, all the errors are related to the drive sde, is it possible that drive is failing or the controller partially or slot where drive is plugged is broken?

  • thats strange, now i am gettin errors on drive sdd1


    [1689274.647052] EXT4-fs (sdd1): mounted filesystem without journal. Opts: (null)
    [1751324.191246] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751324.254068] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751326.358065] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.623717] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.659709] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.707420] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.739448] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.770588] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.804025] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751337.842491] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751343.120123] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657
    [1751344.180015] EXT4-fs error (device sdd1): ext4_lookup:1594: inode #150994945: comm mergerfs: deleted inode referenced: 151494657



    Sounds insane... ;(

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!