huladaddy

I've recently had problems automounting my unraid SMB shares on my NixOS laptop. The problems seems to have begun after my laptop upgraded from kernel 6.5.9 to 6.6.0. Here is my nixos config: fileSystems."/mnt/media" = { device = "//undrobo/media"; fsType = "cifs"; options = let automount_opts = "x-systemd.automount,noauto,x-systemd.idle-timeout=60,x-systemd.device-timeout=5s,x-systemd.mount-timeout=5s"; in ["${automount_opts},credentials=/home/user/smb-secrets,uid=1000"]; }; and this is the error I get: Nov 09 10:53:42 framework systemd[1]: Mounting /mnt/media... Nov 09 10:53:42 framework mount[23125]: mount error(2): No such file or directory Nov 09 10:53:42 framework mount[23125]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) Nov 09 10:53:42 framework systemd[1]: mnt-media.mount: Mount process exited, code=exited, status=32/n/a Nov 09 10:53:42 framework systemd[1]: mnt-media.mount: Failed with result 'exit-code'. Nov 09 10:53:42 framework systemd[1]: Failed to mount /mnt/media. and this is what dmesg is reporting: [ 2481.296367] CIFS: Attempting to mount //undrobo/media [ 2481.296465] CIFS: VFS: cifs_mount failed w/return code = -2 and finally, this is what the mount point looks like: ❯ sudo ls -al /mnt total 0 drwxr-xr-x 1 root root 20 Jun 9 10:26 . drwxr-xr-x 1 root root 98 Dec 16 2021 .. drwxr-xr-x 2 root root 0 Nov 9 10:12 media

Thanks for the quick reply. I don't quite understand the above. The message that shows is that the "Device is disable, contents emulated", which I understand. So, if I shut down and replace the drive, can I start the array while the new drive is rebuilt. I don't know what you mean by "slot is showing unmountable".

I have a failed disk that I need to replace. When I shut the machine down, replace the drive, then bring it back up again, can I start the array immediately? Or do I have to wait until the new drive is added? If I recall correctly, replacing a drive can take a long time as the drive is rebuilt.

Do we know if the issue has been fixed?

Any tips on getting Searx to work? This is all I'm getting in the logs: searx version 1.0.0-224-762c1c41 ⚠️ Check new version /etc/searx/uwsgi.ini.new to make sure searx is working properly ⚠️ Check new version /etc/searx/settings.yml.new to make sure searx is working properly Listen on 0.0.0.0:8080 [uWSGI] getting INI configuration from /etc/searx/uwsgi.ini WebUI is not loading. What's the secret?

Does anyone know if there are plans to create a SimpleLogin docker container? Looks like an incredible package! edit: or how about AnonAddy? This looks even better.

Thanks very much for the advice. Appreciate it. Regarding cache, I guess I can replace it with a larger drive. Is it recommended for appdata to be put on cache? Isn't it better to have it on the array for data protection? I have the appdata share set to not use cache.

If I made space by deleting files, how could I go about balancing?

Thanks for the advice. Is there any way to balance the free space across all the drives?

I have some new information. I can see that 3 of my physical drives are actually filling up. All of my shares are set to high-water and automatically split directories. diagnostics-20210819-1324.zip

I have begun getting errors related to my disk being full. binhex-sabnzbdvpn: tee: /config/supervisord.log: No space left on device Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/supervisor/loggers.py", line 102, in emit self.stream.write(msg) OSError: [Errno 28] No space left on device JellyFin: [16:49:57] [FTL] [1] Main: Error while starting server. Full: SQLitePCL.pretty.SQLiteException: database or disk is full Because of this error, JellyFin no longer runs. but this is what my filesystems look like: Filesystem Size Used Avail Use% Mounted on /dev/loop2 20G 9.6G 9.8G 50% / tmpfs 64M 0 64M 0% /dev tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup shm 64M 0 64M 0% /dev/shm shfs 53T 53T 299G 100% /tv /dev/loop2 20G 9.6G 9.8G 50% /etc/hosts tmpfs 3.8G 0 3.8G 0% /proc/acpi tmpfs 3.8G 0 3.8G 0% /sys/firmware and this is what my docker volume looks like: Label: none uuid: 717af81f-c683-4ca7-98de Total devices 1 FS bytes used 9.12GiB devid 1 size 20.00GiB used 13.52GiB path /dev/loop2 What is going on? What is causing these errors?

I just started getting the following: [22:11:55] [FTL] [1] Main: Error while starting server. Full: SQLitePCL.pretty.SQLiteException: database or disk is full but this is what my filesystems look like: Filesystem Size Used Avail Use% Mounted on /dev/loop2 20G 9.6G 9.8G 50% / tmpfs 64M 0 64M 0% /dev tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup shm 64M 0 64M 0% /dev/shm shfs 53T 53T 299G 100% /tv /dev/loop2 20G 9.6G 9.8G 50% /etc/hosts tmpfs 3.8G 0 3.8G 0% /proc/acpi tmpfs 3.8G 0 3.8G 0% /sys/firmware and this is what my docker volume looks like: Label: none uuid: 717af81f-c683-4ca7-98de Total devices 1 FS bytes used 9.12GiB devid 1 size 20.00GiB used 13.52GiB path /dev/loop2 Any thoughts?

docker.img is mounted read/write. I have a bunch of other containers that are working just fine. This is the error I see inside Sabnzbd: Saving /config/admin/postproc2.sab failed

Anyone?

I started receiving this message: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/supervisor/loggers.py", line 102, in emit self.stream.write(msg) OSError: [Errno 28] No space left on device I'm assuming this is writing to /config. df is reporting that /config is 100% full, but there is still over 200 GB free on that mount. No other mounts are full.