Container launch error

If fsck can be done installing smartmontools should be possible as well.

it is external drive, there is no smart support in case

This seems to be a very special drive. All my external drives including WD MyBook supporting SMART.

all external seagate/wd/toshiba i owned were lack of smart support…

p.s. proxmox tells that smart passed on that drive :smiley:

Nice, let’s blame storj then… Why I’m Leaving Storj as a SNO :sweat_smile:

1 Like

Can you try smartctl -x -d sat /dev/sdc?

1 Like

Seems this log is corrupted even more, or may be a read error (a bad cable?). Likely need to move/delete it to continue, but please try to re-run the hashtable generation to check would it flip or not.

i have tried to rerun: docker run -it --rm -v ${PWD}:/hashstore -v ${PWD}/meta:/meta storj-write-hashtbl write-hashtbl /hashstore several times, each time it stucks on that specific file.
did i understood correctly? im fully safe to delete it?

Not safe, but I do not know, how to fix it. Unlike piecestore, each log file contains dozens pieces, 1GB in total. So it may quickly become DQ, if there are many of such files. More than 4% will definitely end in DQ.
I asked the team, but there are long weekends until Monday.

this one worked:

root@pve:~# smartctl -x -d sat /dev/sdc
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.12-4-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Ultrastar HC310/320
Device Model:     HGST HUS728T8TALE6L4
Serial Number:    VR00N7ZK
LU WWN Device Id: 5 000cca 0c3c04c0b
Firmware Version: V8GNW980
User Capacity:    8,001,563,222,016 bytes [8.00 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/5319
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:    Thu Nov 27 10:59:09 2025 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
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:  (0x80) Offline data collection activity
                                        was never started.
                                        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:        ( 829) 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---   133   133   054    -    92
  3 Spin_Up_Time            POS---   253   253   024    -    135 (Average 391)
  4 Start_Stop_Count        -O--C-   100   100   000    -    664
  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---   128   128   020    -    18
  9 Power_On_Hours          -O--C-   097   097   000    -    25285
 10 Spin_Retry_Count        PO--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    652
192 Power-Off_Retract_Count -O--CK   099   099   000    -    1730
193 Load_Cycle_Count        -O--C-   099   099   000    -    1730
194 Temperature_Celsius     -O----   150   150   000    -    40 (Min/Max 16/68)
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
                            ||||||_ 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
0x2f       GPL     -        1  Set Sector Configuration
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host 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    Aborted by host               90%     14680         -
# 2  Extended offline    Aborted by host               80%     14662         -
# 3  Short offline       Completed without error       00%     14538         -
# 4  Short offline       Completed without error       00%     14538         -

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:                    40 Celsius
Power Cycle Min/Max Temperature:     22/40 Celsius
Lifetime    Min/Max Temperature:     16/68 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    2025-11-27 08:52    61  ***************************************+
 ...    ..( 97 skipped).    ..  ***************************************+
  48    2025-11-27 10:30    61  ***************************************+
  49    2025-11-27 10:31    22  ***
  50    2025-11-27 10:32    22  ***
  51    2025-11-27 10:33    23  ****
  52    2025-11-27 10:34    24  *****
  53    2025-11-27 10:35    24  *****
  54    2025-11-27 10:36    25  ******
  55    2025-11-27 10:37    26  *******
  56    2025-11-27 10:38    27  ********
  57    2025-11-27 10:39    28  *********
  58    2025-11-27 10:40    29  **********
  59    2025-11-27 10:41    30  ***********
  60    2025-11-27 10:42    30  ***********
  61    2025-11-27 10:43    31  ************
  62    2025-11-27 10:44    32  *************
  63    2025-11-27 10:45    32  *************
  64    2025-11-27 10:46    33  **************
  65    2025-11-27 10:47    34  ***************
  66    2025-11-27 10:48    34  ***************
  67    2025-11-27 10:49    35  ****************
  68    2025-11-27 10:50    36  *****************
  69    2025-11-27 10:51    36  *****************
  70    2025-11-27 10:52    37  ******************
  71    2025-11-27 10:53    37  ******************
  72    2025-11-27 10:54    38  *******************
  73    2025-11-27 10:55    38  *******************
  74    2025-11-27 10:56    39  ********************
  75    2025-11-27 10:57    39  ********************
  76    2025-11-27 10:58    39  ********************
  77    2025-11-27 10:59    61  ***************************************+

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             652  ---  Lifetime Power-On Resets
0x01  0x010  4           25285  ---  Power-on Hours
0x01  0x018  6     60659133611  ---  Logical Sectors Written
0x01  0x020  6       752192120  ---  Number of Write Commands
0x01  0x028  6    552148735385  ---  Logical Sectors Read
0x01  0x030  6      3672571563  ---  Number of Read Commands
0x01  0x038  6     91026990650  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           25166  ---  Spindle Motor Power-on Hours
0x03  0x010  4           25166  ---  Head Flying Hours
0x03  0x018  4            1730  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4               5  ---  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               7  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              40  ---  Current Temperature
0x05  0x010  1              58  N--  Average Short Term Temperature
0x05  0x018  1              54  N--  Average Long Term Temperature
0x05  0x020  1              68  ---  Highest Temperature
0x05  0x028  1              16  ---  Lowest Temperature
0x05  0x030  1              62  N--  Highest Average Short Term Temperature
0x05  0x038  1              25  N--  Lowest Average Short Term Temperature
0x05  0x040  1              59  N--  Highest Average Long Term Temperature
0x05  0x048  1              25  N--  Lowest Average Long Term Temperature
0x05  0x050  4          157004  ---  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            1249  ---  Number of Hardware Resets
0x06  0x010  4               5  ---  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            2  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
1 Like

ok, so now what i have
fsck with badblock check and force option - passed
inside:
12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s0

Counting /hashstore/40/log-0000000000000040-00000000...
Counting /hashstore/41/log-0000000000000041-00000000...
Counting /hashstore/42/log-0000000000000042-00000000...
Counting /hashstore/43/log-0000000000000043-00004fc2...
Record count=127898
Using logSlots=18
Processing /hashstore/06/log-0000000000000006-00000000...
Processing /hashstore/10/log-0000000000000010-00000000...
Processing /hashstore/13/log-0000000000000013-00000000...
Processing /hashstore/14/log-0000000000000014-00000000...
Processing /hashstore/15/log-0000000000000015-00000000...
Processing /hashstore/1b/log-000000000000001b-00000000...
Processing /hashstore/1c/log-000000000000001c-00000000...
Processing /hashstore/20/log-0000000000000020-00000000...
Processing /hashstore/24/log-0000000000000024-00000000...
Processing /hashstore/26/log-0000000000000026-00000000...
Processing /hashstore/27/log-0000000000000027-00000000...
Processing /hashstore/28/log-0000000000000028-00000000...
Processing /hashstore/31/log-0000000000000031-00000000...
Processing /hashstore/32/log-0000000000000032-00004fc1...
Processing /hashstore/33/log-0000000000000033-00000000...
Processing /hashstore/35/log-0000000000000035-00000000...
Processing /hashstore/36/log-0000000000000036-00000000...
Processing /hashstore/37/log-0000000000000037-00000000...
Processing /hashstore/38/log-0000000000000038-00004fbf...
Processing /hashstore/39/log-0000000000000039-00004fc6...
record at offset=290528512 in /hashstore/39/log-0000000000000039-00004fc6 has invalid piece header with err=unexpected EOF
record at offset=290499904 in /hashstore/39/log-0000000000000039-00004fc6 has invalid id=13
Processing /hashstore/3a/log-000000000000003a-00000000...
Processing /hashstore/3b/log-000000000000003b-00000000...
panic: runtime error: slice bounds out of range [:36732] with capacity 512

goroutine 1 [running]:
main.(*cmdRoot).iterateRecords(0xc000018400, {0x73e4c0, 0xc00014c030}, {0xc000114a80, 0x2b}, 0x0, 0xc000153b58)
        /go/storj/cmd/write-hashtbl/main.go:188 +0xc45
main.(*cmdRoot).Execute(0xc000018400, {0x73e4c0, 0xc00014c030})
        /go/storj/cmd/write-hashtbl/main.go:109 +0x965
github.com/zeebo/clingy.(*Environment).dispatchDesc(0xc00004dde0, {0x73e450, 0x945540}, 0xc000064240, {{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, ...})
        /go/pkg/mod/github.com/zeebo/clingy@v0.0.0-20230602044025-906be850f10d/run.go:129 +0x6dd
github.com/zeebo/clingy.Environment.Run({{0x73d120, 0xc000018400}, {0x6d8ec6, 0xd}, {0xc000016050, 0x1, 0x1}, 0x0, 0x0, 0x6ef0e0, ...}, ...)
        /go/pkg/mod/github.com/zeebo/clingy@v0.0.0-20230602044025-906be850f10d/run.go:41 +0x198
main.main()
        /go/storj/cmd/write-hashtbl/main.go:29 +0x148

12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s1 - finished, but also had some strange things:

Processing /hashstore/42/log-0000000000000042-00000000...
Processing /hashstore/43/log-0000000000000043-00004fc1...
Processing /hashstore/44/log-0000000000000044-00004fd9...
Processing /hashstore/45/log-0000000000000045-00000000...
record at offset=651274112 in /hashstore/45/log-0000000000000045-00000000 has invalid piece header with err=proto: can't skip unknown wire type 7
record at offset=651243584 in /hashstore/45/log-0000000000000045-00000000 has invalid piece header with err=proto: can't skip unknown wire type 7
record at offset=651242240 in /hashstore/45/log-0000000000000045-00000000 has invalid piece header with err=proto: can't skip unknown wire type 7
record at offset=651241152 in /hashstore/45/log-0000000000000045-00000000 has invalid piece header with err=proto: pb.PieceHeader: illegal tag 0 (wire type 6)
record at offset=651099584 in /hashstore/45/log-0000000000000045-00000000 has invalid piece header with err=proto: can't skip unknown wire type 4
record at offset=651091904 in /hashstore/45/log-0000000000000045-00000000 has invalid id=56
record at offset=651081856 in /hashstore/45/log-0000000000000045-00000000 has invalid id=56
Processing /hashstore/47/log-0000000000000047-00000000...
Processing /hashstore/48/log-0000000000000048-00000000...
Processing /hashstore/49/log-0000000000000049-00000000...
Processing /hashstore/4d/log-000000000000004d-00004fbf...
Processing /hashstore/4e/log-000000000000004e-00004fc2...
Processing /hashstore/4f/log-000000000000004f-00000000...
record at offset=4212736 in /hashstore/4f/log-000000000000004f-00000000 has invalid piece header with err=unexpected EOF
record at offset=4098240 in /hashstore/4f/log-000000000000004f-00000000 has invalid id=75
record at offset=4092032 in /hashstore/4f/log-000000000000004f-00000000 has invalid id=75
record at offset=4090688 in /hashstore/4f/log-000000000000004f-00000000 has invalid id=75
record at offset=4053248 in /hashstore/4f/log-000000000000004f-00000000 has invalid id=75
Processing /hashstore/50/log-0000000000000050-00000000...
Processing /hashstore/51/log-0000000000000051-00000000...
Processing /hashstore/52/log-0000000000000052-00000000...
Processing /hashstore/53/log-0000000000000053-00000000...
Processing /hashstore/54/log-0000000000000054-00000000...

/12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S/s0 - ok
/12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S/s1 - ok

The runtime error originates from code validating piece headers. You can turn off the check by using write-hashtbl with --fast option.

Its getting a bit to hot. Almost hit critical temp.

Has spent some time in over temp. For a HGST this figure is usually minutes or hours. That’s over 100 days if it’s in minutes.

There is a few physical errors. Drive has reset a couple of times.

1 Like

Any news from team? (20 characters)

There is currently no way to save a corrupted log file if it is interfering with the processing of other files.
If it can pass with warnings, then you might decide to keep it, it will have some useful pieces, and maybe can be fixed later.

ok so what should i do now?
rename file, run tool again to finish process, rename file back and launch container?

This will not have any difference between deleting it and renaming in my opinion: when you generate a hashtable, it will not account this renamed log, so when you rename it back the node will not use it, because it’s not aware of it.
It could be helpful only if an improved version of “fsck for hashstore” would be finished, but there is no ETA. So, you may decide either rename it to try to fix it later with an improved version of “fsck for hashstore” or delete.
Of course there is a risk that your node would has lost more than 4% of data and being disqualified meantime.

New day, new error, succeed with recreating meta files, and now faced issue with:

i suppose i need to delate ittrust-cache.json file according to forum, but i do not have it, i do only have this ones:


Should i delete all of them or some specific one?

You need to delete the trust-cache.json file from the config.yaml location.

All of them, but first - please stop and remove the container, then delete all these files and run the container back.
Also would be nice to figure out, why do you have so much of them instead of only one, also, why the latest (actual) is corrupted. Usually it happens only on Windows.

I found a solution with this request: Search results for 'trust: malformed cache: invalid character' - Storj Community Forum (official)