Jump to content

Smart Error on one disc


Go to solution Solved by itimpi,

Recommended Posts

Hello everybody, 

I am new to Unraid and still learning, i use a Old Miditower as Server with 2 HDs and 2 SSDs in it. 
Until now i didnt used a big HDD as Parity Disc but this will come.

I would like to work on on this mashine and install docker and other stuff but i am not shure how bad this Error now is.

It seems that of the two HDDs i used the 1,5 Gig (the older one) has some bad Secotrs, the newer one (4Gig) is ok so far.

This two are my array and the 2 SSDs i got are my cache.
 

I made last day a long SMART test and this is the Error Log from Unraid:

 

ATA Error Count: 945 (device log contains only the most recent five errors)
	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 945 occurred at disk power-on lifetime: 34763 hours (1448 days + 11 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 d1 00 ff ff ff 4f 00      04:58:01.117  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:58:01.096  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:55.772  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:55.752  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:50.278  READ DMA EXT

Error 944 occurred at disk power-on lifetime: 34763 hours (1448 days + 11 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 d1 00 ff ff ff 4f 00      04:57:36.183  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:36.162  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:30.854  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:30.834  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      04:57:25.343  READ DMA EXT

Error 943 occurred at disk power-on lifetime: 34761 hours (1448 days + 9 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 d1 00 ff ff ff 4f 00      03:46:39.117  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:39.096  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:38.151  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:38.133  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:33.636  READ DMA EXT

Error 942 occurred at disk power-on lifetime: 34761 hours (1448 days + 9 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 d1 00 ff ff ff 4f 00      03:46:14.691  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:14.673  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:10.180  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:10.147  READ DMA EXT
  b0 d1 01 01 4f c2 00 00      03:46:10.120  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]

Error 941 occurred at disk power-on lifetime: 34761 hours (1448 days + 9 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 d1 00 ff ff ff 4f 00      03:46:14.691  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:14.673  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:10.180  READ DMA EXT
  25 d1 00 ff ff ff 4f 00      03:46:10.147  READ DMA EXT
  b0 d1 01 01 4f c2 00 00      03:46:10.120  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]

I dont know mutch how to read this.

 

But my questin is now if this are only few sectors i still can use this Harddisk ? are these bad secors now registerd and not used by the system or will i ppbl loose data using this HDD still in my array?

 

I need to Work with Unraid soon but cant wait on other Harddisks 

 

so what is yoru advise ? Take it out or leave it in the array?

 

Thx for help.

tronshome-diagnostics-20240210-1158.zip

Edited by Olivilo
Link to comment
  • Solution

This is a bad sign for disk2:

197 Current_Pending_Sector  -O--C-   100   099   000    -    50

so I think the drive should be replaced.   When you add a parity disk then Unraid is unable to recover a failed disk unless all other disks can be read error free.

 

There is also this:

# 1  Extended offline    Completed: read failure       90%     34760         1693889040

and we normally say that any drive that cannot pass the Extended SMART test should be replaced.

Link to comment

ok i take her out and start only with the 4 Gig HDD

 

when i Buy a big Parity HDD can i add it when my data Drives allready got data on it?

 

Wanna buy a 8 GiG HDD when i travel to germany here in serbia the prices and tech are outdated and overpriced.

Link to comment

Ok i have no HDD to replace and i cant find a explanation how i get with less data drives my array up again its downb and telling a drive is now missing and i cant choose option "unassigned"

 

how do i change this to get my array of 1 hdd up again and working ?

 

Link to comment

You can use Tools->New Config and just have the drives you want left assigned before starting the array.   Easiest to use the "Keep Current Assignments" with the New Config tool and then just remove the drive you no longer want assigned before starting the array.

  • Like 1
Link to comment
On 2/10/2024 at 5:39 AM, Olivilo said:

didnt used a big HDD as Parity Disc but this will come

Just in case you have some misconceptions, Parity doesn't have to be any larger than the largest single data disk in your array. Parity is not a backup and contains none of your data. It just provides a parity bit that allows a missing disk to be calculated from all the other disks.

https://docs.unraid.net/unraid-os/manual/what-is-unraid/#parity-protected-array

 

 

Link to comment

Ok Guys it was a long day with mutch Try and Errors i hope i learns things but nothing really worked what i tried ppbly just a bad wave this day i will try tomorow fresh.

 

One Success ' i could transfer over Local net my Files over to the server and the disc sored it nice. it uses less space than on the old external disc i had.

But all other tries i had were dead ends today.

Virtualization of a MacOS system endet in  neverending installing think the sys i choose was to hard for the old CPU to start.
the installation of Nextcloud with Maria DB endet in that i cant login to the made DB with the credentials i made

last but not least i tried a Enshroudet Server over Stream to start but i think the config or connection top steam diodnt work and it could nothing be downloadet.

I Installed then adminer cause i am not so fammilier with teh commandline commandos to access at least the Maria DB that didnt work neither.

L:ast i was reading all different forums and treid the different aproches endet up in deinstalling few times the docker conmtainers or VMs and try and other approach.


Now i Ask myself if i Deinstall a docker Image with all its stuff is there some config file left that could have old logins that does noot change at a reinstall or is a deinstallation of a docker container or VM a clean deinstallation and i can start with a new try again?

 

Now i am at teh point to reinstall Unraid toaly but i dont knwo how i can keep my shares and allready copied files 

 

Cu tomorrow

Link to comment

I tried to see if they need a Update

but that didnt solve the problem it seems that all dockerapps have lost their Icons and also thery dont work anymore...

where do i Find Logs what coudl explain the actual situation?

 

Thx for help on a Monday

Link to comment

Have you put your server on the internet?

Feb 11 17:49:21 TronsHome sshd[13324]: Connection from 106.XXX.XXX.182 port 50486 on 192.168.1.239 port 223 rdomain ""
Feb 11 17:49:23 TronsHome sshd[13324]: error: kex_exchange_identification: Connection closed by remote host
Feb 11 17:49:23 TronsHome sshd[13324]: Connection closed by 106.XXX.XXX.182 port 50486
Feb 11 17:49:23 TronsHome sshd[13374]: Connection from 106.XXX.XXX.182 port 51396 on 192.168.1.239 port 223 rdomain ""
Feb 11 17:49:33 TronsHome sshd[13374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.58.179.182  user=root
Feb 11 17:49:35 TronsHome sshd[13374]: Failed password for root from 106.XXX.XXX.182 port 51396 ssh2
Feb 11 17:49:38 TronsHome sshd[13374]: Connection closed by authenticating user root 106.XXX.XXX.182 port 51396 [preauth]
Feb 11 17:49:38 TronsHome sshd[13670]: Connection from 106.XXX.XXX.182 port 56968 on 192.168.1.239 port 223 rdomain ""
Feb 11 17:51:38 TronsHome sshd[13670]: fatal: Timeout before authentication for 106.XXX.XXX.182 port 56968
Feb 11 20:03:54 TronsHome smbd[1879]:   read_fd_with_timeout failed for client 118.XXX.XXX.223 read error = NT_STATUS_END_OF_FILE.
Feb 12 06:18:53 TronsHome smbd[24187]:   read_fd_with_timeout failed for client 137.XXX.XXX.31 read error = NT_STATUS_END_OF_FILE.

 

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...