seyz

That would probably have been the better approach. Now I'm smarter. I had read my method here in the forum (German) and thought I'd give it a try. But now I've managed it with my method too. Thanks for your answers and support

Hi all, I want to replace two hard disks (1 and 2) from my array with larger ones. I have therefore used Unbalanced to copy the contents of the first hard disk (1) to another larger hard disk (3) in the array. This larger hard disk (3) already contained files in the same folder structure that are also embedded in the share. After copying, all files are now on the large hard disk (3) but the share does not recognize these files. Is there a way to force the share to recapture all files on a disk? And how can I do it better? Is it better to copy the files on the small disk (1 or 2) to a disk that is not yet assigned to a share? In order to include the complete disk in the share after the complete copying? Regards, seyz

Ich habe nun das Mainboard, die CPU und den RAM ausgetauscht. Der Sockel ist gleich geblieben. Ich hätte gerne den RAM noch getestet, aber das ist wegen Inkompatibilität nicht möglich. Die "alte" Hardware läuft einwandfrei in meinem täglich genutzen Arbeitsrechner. Ich kann somit festhalten, dass es ein Problem mit der hardware war. Kann aber ausschließen, dass es sich um einen "einfachen" Defekt der Hardware handelt. Weiter werde ich hier nicht kommen, da Tests immer ewig brauchen und ich diese Zeit nicht investieren will.

Update has worked. Since then I have been able to copy half a terrabyte without any problems. I assume it was due to the bug in the version. Thank you!

Thank you both. I was already afraid that I wouldn't be able to avoid an update. I will deal with it. Thanks again for the quick replies. I would wait with the solved status until I have performed an update, if that is ok?

Hi @itimpi the name of the share is "Serien". To be honest, I can't really say whether it also occurs with "Filme", as I copy much less here.

hello, I have and had several times now the error message during the copying process that it cannot be started because the share is full. It doesn't matter whether I try to copy via Krusader, the network or the console. The error message always remains the same: No space left on device. And exactly that is not correct. The share still has 20 TB free. I have tried to play with the configuration of the share, but without success. I can usually copy for a while after restarting the server until it stops again. Does anyone know the problem? Or does anyone know which settings cause this? raider-diagnostics-20240306-0213.zip

Maybe there was this error message at the beginning with the old disk and I just overlooked it? When I had the error message with the HDD, which then ran again with a SATA port, it looked the same in the GUI. In other words, Unraid reported an unformatted disk. But that was just a thought. I have no idea how I managed it and I'm sure you have much more experience.

I am quite sure. I also have screenshots of it. And without it, I wouldn't have been able to write any data to it. The HDD was empty and new when I inserted it into the server. The fact that hard disks lose their format is not entirely unknown. Unfortunately, the trick with the mainboard's Sata board only worked with one of two.

.Sorry, could not find valid secondary superblock Exiting now. This probably means that nothing more can be done. Unfortunately, the old disk could neither be mounted with UD nor could attempts to repair it be convinced. However, I believe that both have the same problem and are simply not formatted. However it just comes to that. I think I'll bite the bullet and use an unfortunately quite outdated backup. But not until I have formatted the disk ;-).

Ok. I'll wait. I don't know what exactly the problem with this hard drive is. I did a SMART test and found no errors. The hard drive was repeatedly deactivated and emulated by Unraid and no matter what I did (I swapped: controller, CPU, mainboard, RAM, cables; SATA from the MB didn't help either), the error messages kept coming. I kept having errors with other discs, but then they went away. However, the parity rebuild went through without any problems. Because of the endless story, I have now decided to have the hard drive tested by the manufacturer (guarantee). At the moment the disk is no longer in the Unraid server but is hanging on another computer for testing.

@JorgeB thanks for your answer. Has been running for a few hours. Should be ready tomorrow.

Hello, I had a defective hard disk and therefore removed it and inserted a new one. The new one has already been checked in the past, so I started the rebuild based on parity. After 3 days, the rebuild has now been successfully completed, but the hard disk cannot be mounted in the array because there is no file system. Is there a way to format the hard disk without having to rebuild it or can I at least start the rebuild again after formatting? Regards, Felix raider-diagnostics-20240124-2357.zip

here they are raider-diagnostics-20240111-2012.zip

Hello @JorgeB, thank you for your advice. Can you explain how this can happen? I had the same error and followed your recommendation. It actually helped. After a restart it worked again. With a second hard disk, it also worked without replugging, but it took several restarts. Described in more detail: I have various error messages from various hard disks and am looking for the cause (cables replaced, raid controller replaced, mainboard and CPU to follow). The hard disk in question had reported such errors in the dashboard before it failed.