Brandnew disk gets disabled, remounts and gets disabled again. All sorts of errors in syslog, could use some help

[janpeeters]

Hi all, I could use some help. I have recently installed Unraid, I was very exited about it but I'm having all sorts of Array errors and I'm not sure how to move forward. 

 

I currently have an array consisting of two 8Tb drives (one of them for parity), two 4Tb disks and a 1Tb Cache SSD.  

I've installed some dockers (set appdata and so to cache only) and copied lot's of files over to the new 8Tb drive with pictures, files, movies, music etc from my Mac mini via SMB. 

 

The problems I encountered are:

- One of the 4Tb discs showed Smart errors regarding faulty sectors, but after running a extended Smart test it now reports no problems.

- My main 8Tb disc suddenly went missing. I checked cables and USB hub but they seem all right. This drive reappeared after a while and I could start a parity rebuild. Somehow it didn't recognise anymore though what was on the drive.

 

My log shows quite a few errors. 

Mar  5 14:06:30 JanServer kernel: mce: [Hardware Error]: Machine check events logged

and e.g. lot of this, for the drive that after a extended Smart check reports no problems. 

Mar  5 20:50:58 JanServer kernel: I/O error, dev sdd, sector 2672586568 op 0x0:(READ) flags 0x4000 phys_seg 256 prio class 2
Mar  5 20:50:58 JanServer kernel: md: disk2 read error, sector=2672586504
Mar  5 20:50:58 JanServer kernel: md: disk2 read error, sector=2672586512

And not only for Disk2 but also for Disk3. 

And this:

Mar  5 21:01:52 JanServer emhttpd: error: hotplug_devices, 1710: No such file or directory (2): tagged device ST4000NM0035-1V4107_ZC10MP8A was (sdd) is now (sdh)
Mar  5 21:01:52 JanServer emhttpd: error: hotplug_devices, 1710: No such file or directory (2): tagged device ST8000DM004-2U9188_ZR15C5NH was (sdc) is now (sdg)
Mar  5 21:01:52 JanServer emhttpd: error: hotplug_devices, 1710: No such file or directory (2): tagged device ST8000DM004-2U9188_WSC291JT was (sdb) is now (sdf)
Mar  5 21:01:52 JanServer emhttpd: error: hotplug_devices, 1710: No such file or directory (2): tagged device WD_My_Book_25EE_574343374B35584A56373132-0:0 was (sde) is now (sdi)

and this:

Mar  5 21:01:52 JanServer kernel: emhttpd[3706]: segfault at 67c ip 000000000041816d sp 00007ffe415ec370 error 4 in emhttpd[404000+1a4000] likely on CPU 0 (core 0, socket 0)

 

Well it's quite a collection hopefully someone would be willing to check the included log and help me get some more insight, I'm wondering if I should start anew, but dockerwise everything is quite nicely organised now, so I hope to get my array in order. 

 

Thanks, Jan

janserver-diagnostics-20240305-2213.zip

Edited March 5 by janpeeters

[trurl]

USB not recommended for assigned disks for many reasons, including the disconnects you are experiencing.

[janpeeters]

5 minutes ago, trurl said:

USB not recommended for assigned disks for many reasons, including the disconnects you are experiencing.

Hi @trurl thanks for the fast reply. How do people create arrays of more then 3 devices if USB hubs are not recommended? Most computers just have a few ports? I'm curious to know and see how I could get all my disks (7) connected.

[JonathanM]

1 minute ago, janpeeters said:

How do people create arrays of more then 3 devices

Most motherboards have 6 or more SATA ports, if you need more drives than that,

 

[janpeeters]

2 minutes ago, JonathanM said:

Most motherboards have 6 or more SATA ports, if you need more drives than that,

@JonathanM Hmmm, I have a Intel NUC that I'd thought to use for Unraid. I guess that might not be a great idea then. Do you know of solutions that could help me use my Intel NUC?

 

@trurl I noticed a post from you where you wrote:

Quote

One reason to not use parity with USB array is because USB may not be a reliable permanent connection. If you get disconnects, the disk will be out of sync and require rebuild. Might be a frequent problem.

Would you expect that if I would go this way I would have less problems? And use a backup solution like Crashplan for file security? Or would then still these drives get easily corrupted because they drop out?

[janpeeters]

Just reporting back. The problem I encountered was due to a faulty USB-port. But because of all the warnings I read anout USB and to prevent further possible parity errors I've created the following workaround:

Unraid needs a drive as an array to be able to startup. So I've installed a small 256Gb SSD as an array disk and a larger 1Tb M.2 memory module as cache. That way I could startup Unraid. I've now connected my four USB drives with a powered USB hub to a stable USB port on the Intel NUC machine. And I have mounted them with Unassigned Devices (and set to auto mount).

 

This has worked well so far. I have an automatic backup running that copies the most important data to another drive, so there's also a duplicate. And I'm going to use a offsite backup service too.

[itimpi]

6 minutes ago, janpeeters said:

small 256Gb SSD as an array disk

You can frequently get away with even less such as a small flash drive if you do not intend to store anything on it.

[janpeeters]

17 minutes ago, itimpi said:

You can frequently get away with even less such as a small flash drive if you do not intend to store anything on it.

Yes, you're right, almost any size would do. But because I couldn't foresee my future usage, I took it on the safe side. A drive like this costs around €36 overhere so it was a no brainer.