opiekeith Posted February 19, 2020 Share Posted February 19, 2020 I have setup unraid for the first time and after putting my new/used drives in I got an alert saying that I got a read error. These drives are used but come with a warranty, so want to make sure that the dirve is ok, or I will just get it replaced. At the time of the error, I was doing a lot with the drives so it could have been something that I was doing that threw the error. If I post my Diagnostics zip, can someone look at it and help me out? TIA, Keith Quote Link to comment
trurl Posted February 19, 2020 Share Posted February 19, 2020 9 minutes ago, opiekeith said: post my Diagnostics zip Save us the trouble of asking for it. Quote Link to comment
opiekeith Posted February 19, 2020 Author Share Posted February 19, 2020 (edited) Sorry, just did not want to post it unless it was appropriate. My array shows healthy, but for my last SMART test it says that errors occurred - Check SMART report. I am still trying to figure out Unraid. hades-diagnostics-20200218-1934.zip Edited February 19, 2020 by opiekeith Quote Link to comment
JorgeB Posted February 19, 2020 Share Posted February 19, 2020 It does look like a disk problem, you should run a long SMART test on disk1, and do the same for disk2. Quote Link to comment
opiekeith Posted February 19, 2020 Author Share Posted February 19, 2020 (edited) Thanks for the reply. Once I finish moving my files back onto the storage, I will do that. I also read that read errors also might be because of the cabling to them. Is that sometimes the case? I don't have another breakout cable for these SAS drives, but it is easy enough to get. Edited February 19, 2020 by opiekeith Quote Link to comment
opiekeith Posted February 19, 2020 Author Share Posted February 19, 2020 So it seems that it does not do an extend smart test on these HGST SAS drives. I click the button and after about 5 seconds the start button comes back. Has anyone run into this before? Quote Link to comment
JorgeB Posted February 20, 2020 Share Posted February 20, 2020 Try a manual test: smartctl -t long /dev/sdX And post the output if you get an error. Quote Link to comment
opiekeith Posted February 20, 2020 Author Share Posted February 20, 2020 (edited) I will do this. I rebooted it into the SAS controller and running test from the LSI controller currently. I am still a noob with unraid and just now found the console button. I should be able to run that command from the console within unraid right? Edited February 20, 2020 by opiekeith Quote Link to comment
JorgeB Posted February 20, 2020 Share Posted February 20, 2020 14 minutes ago, opiekeith said: I should be able to run that command from the console within unraid right? Yep Quote Link to comment
opiekeith Posted February 22, 2020 Author Share Posted February 22, 2020 (edited) That command seems to be working. Extended Background Self Test has begun Please wait 617 minutes for test to complete. Estimated completion time: Sat Feb 22 16:35:44 2020 Any idea why I was unable to run this within the gui? Edit - It did seem to run in the gui but did not show it was running. root@Hades:~# smartctl -l selftest /dev/sde smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.98-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === Self-test execution status: 89% of test remaining SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background long Self test in progress ... 7 NOW - [- - -] # 2 Background long Completed - 45907 - [- - -] # 3 Background short Completed - 45878 - [- - -] # 4 Background short Completed - 5082 - [- - -] Also my disk test from the HBA controller did not find any errors. I did get another cable for the SAS drives that I will put in tomorrow. I read that with read errors it is common to have cable loose or bad. It was cheap and I could always use another cable. Edited February 22, 2020 by opiekeith Quote Link to comment
JorgeB Posted February 22, 2020 Share Posted February 22, 2020 15 minutes ago, opiekeith said: Any idea why I was unable to run this within the gui? I believe not all GUI options work with SAS drives. 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.