trurl

Are you talking about this Unassigned Device the syslog is complaining about? Mar 16 18:16:03 BiggieSmalls unassigned.devices: Adding disk '/dev/sdf1'... Mar 16 18:16:03 BiggieSmalls unassigned.devices: No filesystem detected on '/dev/sdf1'. Mar 16 18:16:03 BiggieSmalls unassigned.devices: Partition 'ST8000VN0022-2EL112_ZA1AH61C-part1' could not be mounted. Mar 16 18:16:03 BiggieSmalls unassigned.devices: Adding disk '/dev/sdf2'... Mar 16 18:16:03 BiggieSmalls unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdf2' '/mnt/disks/Big_Drive' Mar 16 18:16:04 BiggieSmalls ntfs-3g[623]: Version 2017.3.23 integrated FUSE 27 Mar 16 18:16:04 BiggieSmalls ntfs-3g[623]: Mounted /dev/sdf2 (Read-Only, label "Big Drive", NTFS 3.1) Mar 16 18:16:04 BiggieSmalls ntfs-3g[623]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Mar 16 18:16:04 BiggieSmalls ntfs-3g[623]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sdf2,blkdev,blksize=4096 Mar 16 18:16:04 BiggieSmalls ntfs-3g[623]: Global ownership and permissions enforced, configuration type 1 Mar 16 18:16:04 BiggieSmalls unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.)

That depends on how you have your krusader mappings. If you have /mnt mapped then it should already be there. Post your docker run command as explained in this very first link in the Docker FAQ: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564345

Another possibility is your docker image is on the array. Post your diagnostics if you need someone else to take a look.

My guess is you haven't formatted any drives so there is no place to save the image. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

But it may be more trouble than it's worth. People sometimes have problems with flash disconnecting unless they boot from a USB2 port. I strongly recommend this previous recommendation:

https://forums.unraid.net/topic/66327-unraid-os-version-650-stable-release-update-notes/

No but it might make your user shares disappear since cache is part of the user shares. In your diagnostics, I see that /mnt/user0 is mounted, but /mnt/user isn't.

Delete all its content then click on the share to get to its Settings and you can delete it there

Don't really understand what you mean there. What I had in mind is just one additional account, the account for the application to use.

Thanks for this. Running it now

Your cache drive is unmountable. Here is the FAQ for that: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-543490 You might wait for further instructions from @johnnie.black but it will probably be a few hours before he sees this.

The "regular" BOINC doesn't have a webUI. You have to manage it from another computer with the BOINC manager. RDP BOINC includes a virtual desktop with the BOINC manager in it.

If you are going to use that graphic for a VM then you will just have to work like you are running your server "headless". You can still access the Unraid webUI from another web browser on your network.

Since you haven't given us any more information we don't know either. I won't be surprised if the problem doesn't return.

And you can't format any parity drive, because parity has no filesystem. As mentioned, format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. Many people seem to have a very vague and incorrect idea about what format does. Did you format disk1 after you removed parity1? If so it might be possible to rebuild disk1, filesystem problems and all, from that parity1 with a little trickery. Then we could try to repair it. If parity1 was still installed when you formatted disk1 then nothing to do but go to your backups.

Haven't looked at those because syslog is in RAM and only goes back as far as the last reboot. You have to setup syslog server to get it saved somewhere: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 I assume you mean filesystem wasn't recognized on disk1. Parity has no filesystem. You didn't have to format. In fact, that was exactly the wrong thing to do. Even if the filesystem was fine, rebuilding a formatted disk from parity will result in a formatted disk. Format is a write operation. It writes an empty filesystem to the disk. All write operations update parity. So, after formatting a disk in the array, parity agrees the disk has an empty filesystem. The correct thing to do would have been to repair the filesystem. Too late now, but if you had told us what your problem was before you did anything we could have told you exactly what to do. Please ask for advice in the future.

Try simplifying your network setup by renaming config/network.cfg and config/network-rules.cfg on flash so it will use defaults.

Maybe I missed it somewhere, but this is the first mention I've seen about trying to recover any data. Parity check will not recover any data, all it will do is check (and optionally correct) parity. As far as I know you weren't trying to rebuild drive 1. If I had to guess, and I do since you haven't given any information, I would say you probably formatted that disk.

See the post just above yours.

To start, same as always Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

You should have asked at this point, because you should definitely be able to replace 4TB parity1 with 8TB disk. There must have been something else going on that you didn't notice or tell us about. It is OK, but these are not interchangeable so if you want to change it to the parity1 slot you will have to rebuild parity. A parity disk larger than any data disk will allow you to easily replace or add larger disks in the future. For example, now that you have 8TB parity, if one of your 4TB failed, you could replace it with an 8TB

I thought this looked familiar. I have merged your threads.

Why do you have 200G docker image? It is extremely unlikely you would ever need more than 20G unless you have some container misconfigured. Your docker image should not grow. The usual cause of filling/growing docker image is an application that is writing to a path that isn't mapped. Disable docker and delete the docker image. Try it a while without dockers and if it seems OK we can work on what you need to fix with your dockers.

Not sure I understand. Syslog Server lets you set where to save the syslog. Mirror to flash is not the only option. In fact, I have never used it that way.

Put flash in PC and let it checkdisk. While there make a backup. Try again. Be sure to use a USB2 port to boot from. If it still doesn't work, prepare flash as a new install and copy the config folder from your backup. The config folder on flash is all you need to get going just as you were.