sonofdbn

Thanks, I feel reassured. I just recently started using Firefox, so didn't come across the second issue before.

I'm on 6.11.5, running dual parity. My disk 4 has generated a few errors, so I am trying to replace it with a new drive (same size). I assigned the new drive as Disk 4 and started the data rebuild. But there's an ominous message next to it saying "All existing data on this device will be OVERWRITTEN when array is started." If I take this literally, this means that after the data rebuild, when the new disk has had all the old data rebuilt on it, all this data will be overwritten when I start the array. Surely this is not what is going to happen? Also a bit confused about whether the array has actually started. Because this is the message I see in the GUI footer: But I'm still able to access files on the shares on the array, presumably through Disk 4 contents being emulated. I thought that if the array was stopped, the disk shares would not be accessible? tower-diagnostics-20230914-1144.zip

That part I understand. My issue is that if, having completed the pre-clear cycle, and therefore having written zeroes to the entire 16TB drive, this will result in writing 16TB of zeroes again, somewhat unnecessarily. Since I have completed one pre-clear cycle and only barely started the pre-read step of the second cycle before stopping, I am hoping that the disk has the two requirements for adding to the array as a cleared disk: - the drive is filled with zeroes - the drive has a signature that affirms this So if I add the drive in its current state to the array, will unRAID recognise it as a cleared drive and therefore allow me to format it as a new array drive? Or can I start a new pre-clear and select just the Verify Signature option? I'm trying to avoid doing an unnecessary re-zeroing of the drive if possible.

I had originally set my brand new disk pre-clear to 2 cycles, but decided it wasn't worth taking the extra time. So I stopped the pre-clear after the post-read had completed (and the next cycle had started with pre-read). What do I need to do now to be able to add this disk to the array? I read through the various choices in the first post, but it's not clear to me what is required now.

Amazing what some patience and reading can do. It turns out that there is a setting for Preclear Queue and the default is 2. So I've changed it to 3 and all is good. Also from this thread I see that it's not possible to change the number of cycles during the pre-clear.

I started pre-clearing three 16TB disks; two started pre-read, but one pre-read started and then almost immediately paused. I tried restarting the pre-clear on that disk, but it went straight to the paused pre-read state. The log shows "Pause requested by queue manager". Should I worry about this? Dashboard shows CPU at under 25% and RAM usage is at 4%. So those should not be causing any problems. Also, having read a bit of this thread, can I set the number of cycles back to 1 during the pre-clear? I currently have the number set to 2, which I understand from an early posting in this thread is unnecessary.

I don't have a definitive answer, but I think the problem might have been self-inflicted. I deleted the MACOSX folder on the server, rather than on the PC, and since the files were still on the PC, Nextcloud might have tried to sync them back before the rsync. Hence the files, or maybe temporary Nextcloud sync ones, were still there in the directory on the server, and some files there were still synced to the backup by rsync, resulting in the non-empty directories that couldn't be deleted.

I'm trying to use rsync to backup from one unRAID server to another, just using the terminal. I've mounted the destination share using Unassigned Devices, and the command is basically: rsync -avP --delete /mnt/user/Nextcloud/username/files/ /mnt/remotes/Backup_server/Nextcloud/username/files It largely works, but I ran into a problem with an error message saying "cannot delete non-empty directory". Previously I had backed up a sub-directory a few levels down in a folder called custom_banners/__MACOSX (if this looks familiar it's from SpaceInvader). I subsequently deleted this sub-directory on my main server, and now when I run the rsync command above I get the non-empty directory error message, saying it can't delete this directory and its sub-directories. I tried --delete-during as a parameter, but that didn't make a difference. I also get some error messages like this: rsync: [receiver] rename "/mnt/remotes/Backup_server/Nextcloud/username/files/Documents/2021/moroccan-flower/__MACOSX/._moroccan-flower.jM0wjF" -> "Documents/2021/moroccan-flower/__MACOSX/._moroccan-flower": No such file or directory (2) When I check the destination server, that directory does exist, so not sure what's happening here. I don't know if it's just coincidental that both issues involve a "__MACOSX" directory. I think what I'm trying to do is quite simple; I'm not doing anything with Nextcloud when running rsync - and I've tried various times and always get the same issues with the same files and directories. How can I fix this?

My server seems to be a bit sensitive - meaning that cables seem intermittently to come a little loose (UDMA CRC errors). So generally I avoid opening up the case unless absolutely necessary. So here I just rebooted the server without touching anything inside, and everything has been working fine for a few weeks now (I've probably now jinxed the server). So I'll put it down to a connection problem.

I'm on 6.11.5. A few days ago I found that overnight my disk 4 was in an error state "No device identification ()" and shortly after that there had been a write error and the disk had been disabled. So I rebuilt, without incident, and all seemed fine. But this morning, about a day after the rebuild, there was a read error. From my amateur's view of the diagnostics, the disk looks OK, but obviously I'm worried about the errors. Does the disk need to be replaced? tower-diagnostics-20230730-0935.zip

After changing the docker network type to ipvlan, the same problem re-occurred. So (additionally) I switched to the binhex/arch-qbittorrentvpn:libtorrentv1 version of qbittorrent, and now everything is running fine.

One day I'd like to be able to set up MC properly, but even using the barebones MC in a console window works very well for me. I've tried and still use Krusader occasionally but it just acts weirdly sometimes. Recently I was trying to delete some files, but Krusader just didn't. No error message or anything. As usual as a Linux amateur, I thought it was possibly a permissions problem, although I think it deleted other files in the folder which should have had the same permissions. Then I went into Dynamix File Manager and deleted the files with no problem at all. Maybe there was a trash bin space problem in Krusader? But even so, there should have been a notification. (I use the binhex-Krusader docker container.) What I'd like to be able to do in MC is set up the starting panels to some other configuration than the default. Also, the folder/file size numbers are just weird. I read about some way of making it more humanly readable, but again can't get that to stick for when I run MC the next time. Just can't find documentation about MC at the right level for me. If I was forced to use only one, I would go for MC - quirky but works more reliably. I also use WinSCP from my Windows PC. It's great for getting a GUI into the unRAID array and easily changing permissions and viewing text files. Great for people like me who are not into "chmod 777" type commands. Can also move/copy files from PC to array - it's like a fancy FTP client. What it doesn't do is move/copy files within the array (afaik - if I'm wrong please do tell me how - would make it incredibly useful).

Just to close this off: in the end I went with an Intel i5-13500 (and an ASRock Z690 Pro RS motherboard). ECC would have been nice, but just too difficult/expensive to find a reasonable hardware combination.

On qbittorrent I had been using an older version of the container precisely because of the problem described. But recently that older version stopped working and I changed to the latest version, which seems to be running fine, unless it's causing these crashes. I'm not sure, but I think the first crash came before switching to the latest version. For the moment I'll stick to the latest version, but I have changed docker network type to ipvlan. Let's see how things go....

I'm on 6.11.5. Over the last week I've twice had a problem with the web UI becoming unresponsive in parts - some tabs won't open, the main tab shows the unRAID wave in the Unassigned Devices section and after a while the main tab also fails to open. Although the unRAID GUI is unresponsive, other things are running: I can access files and open them. I think the first time the Win10 VM was still running, although this time I can't RDP into it. Both times I've tried "powerdown" via SSH but the server doesn't seem to shut down. The first time I couldn't get into the GUI to get diagnostics (and didn't know that this could have be done via the command line). Unfortunately I can't recall exactly how I shut down the server the first time. Might have been via IPMI. This time (today) I grabbed diagnostics and then tried to shut down via the GUI. Heard the beeps (as before) but after about 45 minutes the server was still on (as before). In the end I shutdown via IPMI. When I rebooted after the first incident, one of my disks was marked as missing. Seemed to be a loose SATA connector; after some replugging I started the server and everything seemed OK. But today I got the unresponsive GUI again. tower-diagnostics-20230714-2143.zip

OK, my (big) mistake. I had set the version to 4.3.9-2-01; I think this was a while back as a workaround for some problem I had. Switched to latest version, and all OK now.

I should add that I'm using PIA and I think my qbittorrentvpn setup is very straightforward. So far still unable to get it going properly. (It's been working fine for ages.)

I recently noticed that no torrents were appearing at all in the Web UI (all categories had a count of 0) and the bottom bar that normally shows upload and download speeds etc. was blank other than a few icons like up and down arrows. I'm on unRAID 6.11.5. Recently I ran "Docker Safe New Perms" to fix some issue in another docker, if that's relevant. supervisord.log

Data rebuild did complete. But there surely shouldn't be random(?) interruptions.

Always seems to happen: I open up the server to do something with the hardware and end up with more problems. This time unRAID (6.11.5) told me there was a disk that had failed, so I replaced it with a pre-cleared standby disk. I took the opportunity to do some general cleaning and change a drive cage and fan position. Then I rebooted and started the data-rebuild on the new disk. After a few hours of rebuilding, one fan got a bit noisy, but looking through the window it seemed to be spinning fine. But when I tried to connect to the server I couldn't reach it over the network. In the end I had no choice but to reboot. So the data-rebuild started again from the beginning (groan). I had lost network connection a few weeks ago, so I'm wondering if there's some underlying problem. (I think the fan and physical changes are just a coincidence.) I'm also hoping there's no problem with the data rebuild. Does unRAID consider a disk pre-cleared (and therefore effectively blank) until the rebuild is complete? (Hence the restart from scratch.) abridged_syslog.log tower-diagnostics-20230625-2228.zip

Thankfully, yes, restarting the server got all the shares back. One thing I noticed after rebooting was that although I had shut down the VMs before running Mover, I hadn't stopped the VM service. Could this have caused the shfs crash? I'm a little concerned that something is causing a problem with Mover if I'm going to incorporate it into regular use.

I'm setting up my second server (6.11.5), and haven't used Mover before. I had set up the share "domains" to "Prefer: vm_nvme" and has set up two VMs. But although there's a ton of spare space on the Nvme SSD, I found the two VM "vdisk1.img" files under "domains" on Disk1 instead of on the SSD. I thought that somehow Mover had run and moved "domains", perhaps before I set up "Prefer: vm_nvme", but it's unlikely because I set up the second VM very recently and way before the scheduled Mover default time of 3:40. Anyway, whatever the cause, I wanted to move the VMs back to the SSD. Doing some reading, I got the impression that Mover would "honour" the Prefer setting and actually move files back from the array to the SSD. (This is contrary to what I had previously thought, which was that Mover only ever moved files in one direction: off the cache pool to the array.) Anyway, I thought no harm in trying - worst that could happen was that Mover did nothing..... So I manually invoked Mover from Settings/Scheduler and nothing seemed to happen. I checked the Main page on the GUI and there wasn't much disk activity (the VMs in total are over 300GB, so any moving wasn't going to be instantaneous). But when I looked at Shares they had all disappeared! I should have had at least appdata, domains and isos. Fortunately it looks like the files are where they were previously. Unfortunately I didn't set up the Mover log. What happened and did I do something wrong? t2-diagnostics-20230617-2223.zip

I must have added at least seven 8TB drives in unRAID and never noticed this really quite large overheard before. My surprise was more that the message says "unmountable", but the disk must have been mounted for parity to be running.

I'm setting up a new server and precleared both the 16TB parity drive (as a stress test, I believe preclearing isn't necessary for a drive that's going to be added as parity) and an 8TB data drive, which I think had data on it before. So I thought both disks should essentially just be blank. After adding them to the array (they're the only two drives), a parity sync started, but at the same time a message popped up for the 8TB data drive: "Unmountable: Unsupported partition layout". So I cancelled the parity check and formatted the data disk. Now it's online but it says that 55.8GB is being used. This seems weird - seems odd that a parity check would start when the disk is purportedly unmountable, and how did I end up with 56GB of data being used? For now I've stopped the array. t2-diagnostics-20230613-1546.zip

I'm trying out HQPlayer Embedded, where you download an .img file and flash it to a USB drive. Then you boot a PC from the USB drive and the software runs in RAM and on the USB drive, without (it seems) writing or installing anything to the hard disk. It works fine this way, but I would like to try to install/emulate this in a VM. I'm trying to avoid having yet another flash drive hanging off my PC. Given that I have the .img file, how would I set up a VM using that file?