aurevo

Hoopster's answer sounds very logical. Does your server just run or does it also use the AMD card after the upgrade?

The current status is as follows: I have rebuilt the CPU, the mainboard back to the old components. In parallel I exchanged the power supply with an identical one. After that I had the parity restored and currently it looks good, even if the previously mentioned hard disks still show errors (though not always, the errors had disappeared temporarily). Would you be so kind to have another look at the logs? Currently the hard drives are connected onboard and with the LSI controller. In normal use, the server is running as desired again and no longer outputs errors. tower-diagnostics-20200319-0125.zip

Hello, I would be very grateful if you could help me with a somewhat complicated situation (in any case, it's opaque for me at the moment). My server needs access to two networks. I have an internet line from Vodafone, I would like to use it only for the plex docker. But the Plex docker should also be accessible locally in the LAN. For all other connections I would like to use the second internet line via O2 (JDownloader, Sonarr etc.). Vodafone is accessible via a Fritzbox, from which I can pull a cable directly into one of the network ports of the server. O2 and the LAN (with TVs and other devices like WLAN Mesh are connected) can be reached via an ASUS router (Internet via LTE using a TP link on the router's WAN port). Does anyone have an idea how I can best do this?There are two network cards in the server, which could be connected directly by cable, whether from the Fritzbox or the ASUS router. The Fritzbox network is in the network 192.168.1.0/24, the ASUS router in the network 10.10.10.0/24. Many thanks in advance.

Where this errors with both controllers? This is for sdf, which ones having these errors too? No, I did not changed the Power Supply. No Power Supply at hand actually.

The unassigned device ST6000... I can not mount it through UD

I just switched to the old SATA controller. Diagnostics attached. Now everything is available, but I can't mount the ddrescue-dest, although it was mountable before I changed the adapter, now the only option is to format. The four Toshiba HDD still showing error state. tower-diagnostics-20200308-0036.zip

I think in the next few days I will first install the old controller again and test it. For the exchange of the power supply I would have to take all components apart again. I flashed the controller according to the following instructions: https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=522038 Is the manual still the most current one, or are there new options in the meantime?

I used the same power cables that were working for several months without problems. The SAS-SATA cable are brand new and one of them I already replaced. You got a recommendation for me? Otherwise I would install the old port multiplier again and test if it works with it. Currently it is a D2607-A21 crossflashed. But I don't know how I can test or see if it's the controller.

I just started the array, the parity sync ran for a moment and then the parity disk was no longer available. The ddrescue-disk could be mounted and I was able to access it for a short time, but this is now not possible from Windows (e/a device error). I almost think something is wrong with the SAS controller. tower-diagnostics-20200304-1759.zip

Yes, then I actually had a wrong understanding of how it works. So I can now start the configuration and test if UD mounts the new hard disk. In order to use my shares later as before you have to restore the old assignments (with the new disk), right?

So I could start like this? And is my Windows VM on the cache devices affected or deleted?

Can I do a new config without the defective disk3? Or should I use Preserve current assignments?

I disconnected the defective 4TB disk and now this is the state. One disk missing. Parity, Disk 4, 5 and 6 are on Port 1 SAS-Controller. Disk 7 and the ddrescue-dest are on Port 2 SAS-Controller. SSDs and the both 3TB disks are on the mainboard onboard. As I said before I changed the SAS-Cable yesterday so I do not think that it is the cable. Also disk 4 and 5 seem to have errors which where yesterday without errors. Why is disk 6 emulated or disabled but also shown as available in the disk slot 6?

Wanted to try, but now the next problems when starting the array with all disks to mount via UD. The ddrescue-dest also not available to mount. tower-diagnostics-20200304-1355.zip

Too many wrong and/or missing disks! Is there any "trick" or do I have to connect all drives again?

Diagnostics attached. tower-diagnostics-20200304-1240.zip

Should the disk be mountable right after disk clone? Pushing "MOUNT" is showing "MOUNTING" for a few seconds and nothing happens. And after sync / rebuild will the 6TB become available or only 4TB?

As seen attached, is it normal, thar there are no errors? Disconnected any other disk than the "failing" 4TB disk and the new one (6TB). How to mount the disk without loading the Keyfile and starting the array?

Do I have to create a new config for that like you mentioned in the post before? "you could sync parity with the disk unmountable then rebuild, partition would be correctly recreated during that, but it will take longer." - How exactly are the steps I have to do after ddrescue finished? And thanks again for your patience.

I hope ddrescue runs through now without problems, I will report at the end. Would you be so kind to check the log again, if the hard disk TOSHIBA_HDWE160_9699K69FF56D - 6 TB had problems as well? It has been spontaneously unavailable the last few days and was no longer part of the array or was not recognized by the SAS controller. At first I thought it was due to the cable, but I already exchanged it for a new one and the problem was the same.

Old one was 4TB, new one 6TB, so I only can mount it and copy over data or can it be same size or bigger? Parity check / rebuild is also needed because the parity was not given, that was the reason to use ddrescue. Screen is not installed. Can I use the one from the Nerd Pack?

So it is running now for at least six hours. If it finishes, how to show UnRAID to take the new cloned disk as the old one? Do I assign the new hard disk to the old slot, or can I leave it in the new slot and UnRAID notices that the old data is there? If the SSH connection terminates unexpectedly, is ddrescue still running in the background or do I need to restart the process? And is it then aborted, or does it continue at the old location?

Yes, from source to destination. But how too find the right /dev/sdX?

I ask one more time before I make a mistake and the data is finally lost: My defective disk is part of the array, my new disk isn't. The disks are not mounted and I use ddrescue as follows: ddrescue -f /dev/sdX /dev/sdY /boot/ddrescue.log How do I decrypt the data, or is the hard disk copied encrypted to the new hard disk? And which hard disk is my source and which destination?

Also changed power cable. Copy started with good speed, get lower and abort via Krusader. Interesting, that the disk was completely not recognized on the Fujitsu Controller and now is recognized, but partially defect. Does the ddrescue also works on encrypted volumes? And any way I need another disk with same space or more, right?