heppy Posted January 15 Share Posted January 15 Saw this in the syslog after a warning came up Jan 10 01:09:38 Tower kernel: I/O error, dev sdh, sector 4648311824 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311760 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311768 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311776 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311784 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311792 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311800 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311808 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311816 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311824 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311832 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311840 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311848 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311856 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311864 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311872 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311880 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311888 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311896 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311904 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311912 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311920 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311928 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311936 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311944 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311952 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311960 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311968 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311976 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311984 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311992 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648312000 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648312008 Dashboard reports an error, Smart Self Test is reporting OK (am now running an extended test) Diagnostics attached....and if it's somehow ok, can I clear the error TIA, Simon tower-diagnostics-20240115-1045.zip Quote Link to comment
JorgeB Posted January 15 Share Posted January 15 Run an extended SMART test on that disk. Quote Link to comment
heppy Posted January 15 Author Share Posted January 15 1 hour ago, JorgeB said: Run an extended SMART test on that disk. yup, as I said in the original post, am doing that already and will post what it comes back with. Thanks Quote Link to comment
heppy Posted January 23 Author Share Posted January 23 On 1/15/2024 at 12:09 PM, JorgeB said: Run an extended SMART test on that disk. I have no idea what this means but I’m presuming replaced the disk immediately? Quote Link to comment
heppy Posted January 23 Author Share Posted January 23 Here’s the downloaded report tower-smart-20240123-0833.zip Quote Link to comment
itimpi Posted January 23 Share Posted January 23 Not sure if the screenshot shows the drive has failed. Normally the section that really matters is this one: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 26203 - # 2 Extended offline Completed without error 00% 26117 - That shows the last extended test completed without error. You should probably now run another one to see if it still passes as that tends to be the best indication of drive health, and failing that is almost invariably accepted as a reason for a RMA (assuming the drive is still under warranty). Quote Link to comment
heppy Posted January 23 Author Share Posted January 23 Perfect, will run another test and thanks for the reply. I should have a mentioned that one of my drives has a broken piece of plastic on the connection which i had to bodge fix with some hot glue so i wonder if that’s the fail point even though the server hasn’t moved in over a year. Will run another extended text. Quote Link to comment
itimpi Posted January 23 Share Posted January 23 Just now, heppy said: I should have a mentioned that one of my drives has a broken piece of plastic on the connection which i had to bodge fix with some hot glue so i wonder if that’s the fail point even though the server hasn’t moved in over a year. Yes - If there is something interfering with the connection to the host this may mean the drive needs replacing even though otherwise it may be perfectly healthy. If the drive passes the extended test (which checks its internals thoroughly) maybe it is worth looking at that connector again before scrapping the drive. Quote Link to comment
Solution heppy Posted January 23 Author Solution Share Posted January 23 I meant to replace that drive anyway, but I’m always terrified of shutting the server down as last time it went into hang on shutdown and I had to force shutdown which was a whole other nightmare! Quote Link to comment
Recommended Posts
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.