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.

The update that came out today fixed the issue.

Just update my SickChill container to the latest version and now it is not booting. I am getting this error: File "/usr/bin/SickChill.py", line 5, in <module> from SickChill.SickChill import start File "/usr/bin/SickChill.py", line 5, in <module> from SickChill.SickChill import start ModuleNotFoundError: No module named 'SickChill.SickChill'; 'SickChill' is not a package

OK. Restoring dockers looks simple. I have restored the .xmls from /config/plugins/docker/dockerMan/templates-user. However, after they start, I don't see a way to get to their GUIs. The option that used to be there when clicking their icon on the docker page is no longer there. Does it have something to do with me accessing the unraid webGUI through My Servers? -- The reason the webUI was not accessible had to do with not having the correct network type specified for use with swag. I had not restored that docker yet. Now, how about plugins? What is the best way to restore plugins and keep all of my old settings?

Actually I do (thanks to the Backup app I installed and forgot about). Unfortunately, there is only one backup (maybe that's how it works) and it is a week old. Can't be sure whether or not I was hacked before or after that. What about looking at modification dates? Can I confidently use files that I think are sufficiently old enough as to not have been hacked? If so, which files should I restore?

OK. Got it up and running. But I noticed something strange. After booting with the new image, I was still unable to access the GUI. I tried to access the GUI from a different machine, and this time I was able to, and I noticed that if I tried to connect using https, it was a no go, but http worked just fine. I confirmed this by trying it from first machine, and lo and behold, if I used http instead of https, I was able to load the GUI. So the question is, did something change upon updating to 6.9.1 that prevented me from loading the GUI through http? Was that my only issue? Now that I have it running, I could try using the backup I made of the flash and see if I can access the GUI using http, but I kinda like the fact that I am starting fresh, just in case there is some remnant of being hacked. So, how can I restore all of my plugins, dockers and all other configurations I may have forgotten about?

Yeah. That sounds like a good idea. Should I use a new flash drive? Could the stick be compromised? Boot sector, etc.? Geez, it has been so long since I first created the flash boot... I have to read up on everything all over again. I don't remember how it's done. So recreate the boot disk, and restore /boot/config/super.dat and /boot/config/Plus.key? That will get my system booted and array working. What about plugins and dockers? How can I restore those? Are all the config files stored in /boot/config? Would there be any harm in restoring my entire config directory? Or maybe just the .cfgs? I would like to avoid as much manual re-installation and configuring as possible. What are your recommendations?

Those diags were made after the problems arose. I got those over ssh. I don't think grabbing new diags would yield anything new. diagnostics-20210320-1408.zip Some questions I have after perusing the filesystem: 1. There is an empty file called /run/xtables.lock Should that be there? 2. Some files in /etc/rc.d are not executable. Should they all be executable? 3. In order to determine if certain files should not be present, can I look at last modified date for clues?

I don't have a monitor. I have always just used the webGUI from a networked machine. At one point I did have a monitor, but after boot, it only displayed a command line. It didn't have a GUI. Can I fix my issues without a monitor (i.e. can I do everything from ssh), or do I need to get a monitor?

Yes, Port 22 is now closed. Can I start the array from the command line?

I just recently updated to the latest 6.9.1 (from 6.8.something), and after I rebooted, the webGUI was no longer available. Luckily, I am able to ssh into the server. Based on the diagnostics, I was told I may have been hacked. I had Port 22 forwarded for a brief while. At this point, I don't know what to do. How can I figure out what has happened and get my system up and running again. Would greatly appreciate some kind soul helping me out. diagnostics-20210316-1437.zip