ridley

I cannot remember now, it was some time ago. I think it was the former.

I am trying to reduce my number of disks down to 8 in total so I do not need to power up the diskshelf. So the 3 , 4Tb and some of the 8Tb drives will be going. I have a 14Tb and another 18Tb to add. What sort of corruption on disk24? I have looked at what is on the other appdata folders on non cache drives and they appear to be (almost) empty, just a folder structure. The system folder on Disk 2 is a folder called docker with 400Gb docker disk image file in it, the docker folder on the cache drive is empty.

8-15 you mean? I removed them and replaced them with larger drives after a bit of unbalancing.

OK it has finished and here are the diagnostics tower-diagnostics-20220815-1740.zip

I think you're right, it seems to have got to bigger files and is now up to 100MB/s and now back to very slow 🙂

Been running mover for 12+ hours now and it is very, very slow. I am talking a MB / s slow, that cannot be right, right?

Diagnostics tower-diagnostics-20220813-2216.zip

Disable the VM whilst sorting out the APPDATA you mean?

What to do with the APPDATA?

No idea, looks like Windows stuff to me and hasn't been modified for a 1/4 century.... I suspect some backup of a windows folder from way, way back.

Is that any better? Thanks for all your help shares.pdf

Will do. Is this perhaps because I recently added a cache drive?

Recently I have been getting execution errors on starting or stopping dockers. Doesn't seem to occur on anyone in particular, and does happen on dockers that have worked for years. Also if I have dockers enabled building parity or a drive is incredibly slow 20MB/s or less, whereas disabled it is 130Mb/s. Any idea what is causing it? tower-diagnostics-20220812-1957.zip

I have just turned on my array and a one of the drives has a red cross and is disabled. I have tried it in three different slots in my DiskShelf as well as in the R720 Server and each time I have the same result. Any ideas on what to try next? tower-diagnostics-20220812-1847.zip

Thanks for the help, diagnostics attached tower-diagnostics-20220808-1557.zip

I am trying to make a VM from my old pc's drives. I have imaged the drives but getting the data files (there are several 1TB files and a couple of 3-4TB files) onto the array is so slow... I have tried across the gigabit network, slow, so tried fitting the drive with the images on in as an unassigned device and transfer from there via MC & Krusader but though they start fast at 200MB/s it goes down and now after 12+hrs it is at less than 10MB/s I have turned on "reconstruct write" to try to speed things up. Any ideas on what I can do to speed this up?

Yes I use the internal one, ironically I cannot get the separate node docker to work reliably.

Any idea why my Node keeps deregistering after not being able to connect to the server, even though the server and node are running on the same machine? I have attached the node log, it looks like the node loses connection to the server (192.168.1.32 is the ip of the server and node) and then if it cannot reconnect drops and then reconnects. Seems odd when both Server and Node are on the same machine. 1080p Node-log.txt

I am wanting to run my old PC inside a VM and so I will need to create images of the drives. I see I can use DSK2VHD and then convert the image to something suitable for the VM but I have several drives in the old PC, do I make several image files or one that covers all the drives? Or is there a better/easier way of doing this?

I am trying to move my old PC into a VM I was wondering if it is possible to image the drives across the network or do I need to install them in the server as unassigned devices and do it from there?

So take it out of the array, reboot, put it back in and reboot, then rebuild?

I have just turned on my server and I have a red cross against one of the 8Tb drives. The drive itself is in a DiskShelf and I have removed the drive, reseated it and even moved it into a different slot but still got the red x. I have just bought two 18Tb drives to replace my 14Tb parity drive and expand the array, but I haven't started that yet and so cannot swap in an 18Tb for the 8Tb. I would prefer not to have to buy another 8Tb or 14Tb! Any advice on a way forward. Logs attached, the drive in question is drive 20 a Seagate. tower-diagnostics-20220802-1411.zip