Vitor Ventura

Hello there, Facing some problems, and i dont know where or how to search. Basically, some services wont start, saying "no space left". JellyFin: 6-rc: fatal: unable to write /run/s6-rc/state: No space left on device s6-linux-init-shutdownd: fatal: unable to rename stage 4.new to stage 4: No space left on device s6-supervise s6-linux-init-shutdownd: warning: unable to write supervise/death_tally: No space left on device s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device s6-linux-init: warning: unable to dump kernel environment to /run/s6/container_environment: No space left on devicePostgres_Immich 2026-02-08 04:12:30.573 GMT [1] LOG: database system is shut down sed: cannot rename /etc/postgresql/sedQLYN7T: No space left on device sed: cannot rename /etc/postgresql/sedZQolOM: No space left on device sed: cannot rename /etc/postgresql/sedPjmVnu: No space left on device sed: cannot rename /etc/postgresql/sed0PtNOB: No space left on device sed: cannot rename /etc/postgresql/sedG3ja3V: No space left on device sed: cannot rename /etc/postgresql/sedXwgag9: No space left on device sed: cannot rename /etc/postgresql/sedRBAngh: No space left on device Using SSD storage I'm not sure where to start looking. My cache ssd has enough space. Happy if someone can help. Thanks. venturanas-diagnostics-20260208-1442.zip

Title says everything. Cannot access to my server for more than an hour, cant access via ssh, after pressing power button once, does nothing, cant download diagnostics. I had a hdd replaced few days ago, everything worked well, most of it, but nothibg like this. Im afraid of using reset button and the array messed up... venturanas-diagnostics-20250612-0135.zip

didnt work well :( i have to manual recover all files, via script. many thanks again

try xfs_repair -L /dev/sdn1 ?? tried mount with mount /dev/sdn1 /mnt/temp

i havent touched the hdd i removed. its possible to added to array again to parity pick everything, and them swap again the hdds? Connected via usb and cannot mount. maybe have a possibility to recover the corrupted filesystem, even with the new one swapped?

well, after analysing a few files, checked my Immich, and is completely broken... 😭 in 10 years, 6 with unraid, never had something like this... many thanks for your effort @itimpi and @JorgeB

The folder is giving invalid path error is the lost+found folder. i had lost files, example, i had the season 18 completed of Naruto Shippuden is not possible to recover all files in lost+found? venturanas-diagnostics-20250609-1533.zip

Diagnostics after reboot venturanas-diagnostics-20250609-1412.zip

Yes.

ran via webUi multiple times ran xfs_repair -L and then -v, nothing changed

uploaded diagnostics venturanas-diagnostics-20250609-0908.zip

Sorry for late response, but had the same problems, multiple times during this time. Last week, the same hdd, gave the same problem, and after repair, had 16 current pending sectors, and increasing. Because i had a new hdd, replace him. Stopped array, remove hdd, started array, stopped, added new one, and with docker and vm off, leave to rebuilding it. After all the work, some series (i received notification that had been deleted) didnt shows up, so i ran Compute All and have 667Gb of data in lost+found. How can i recover that data, if i cannot access?

Diagnostics after start array, not maintenance venturanas-diagnostics-20250501-1327.zip

This diagnostics is after finished rebuild venturanas-diagnostics-20250430-2054.zip

slowly rebuild, sometimes is faster

I have a LSI controller 9201-i8 and i haven't touch anything for a 2 years now. Maybe need to turn off remove the sata cable and connect again? follow this https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself should be enough?

i think its this.

this is the output - repairHDD.txt file No the disk is dead... lost+found is completely empty Uploaded new diagnostics. venturanas-diagnostics-20250429-1512.zip repairHDD.txt

i didn't know i had a lost+found from the last repair. Already did, and had a long list, with thousand of lines. Everything is working now, thanks

Yes i confirm, that its been removed from the DB, because, cant access to the files due to corruption. Its the same HDD from the last time. I have a new spare HDD, when an HDD die, permanently.

I use Gotify, connected to Sonarr and Radarr, thats why. I forgot that something happen in the past, i stress a lot when this happen, sorry.

I dont know what to do, starting receive messages that some series and movies is being removed. venturanas-diagnostics-20250419-1602.zip

Hello there, Switch to this container, but having some problems. Any ideia how to solve? 2024-12-07 16:37:31,611:DEBUG:certbot._internal.error_handler:Encountered exception: Traceback (most recent call last): File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort) File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations raise errors.AuthorizationError('Some challenges have failed.') certbot.errors.AuthorizationError: Some challenges have failed. 2024-12-07 16:37:31,611:DEBUG:certbot._internal.error_handler:Calling registered functions 2024-12-07 16:37:31,611:INFO:certbot._internal.auth_handler:Cleaning up challenges 2024-12-07 16:37:31,611:DEBUG:certbot._internal.plugins.webroot:Removing /data/letsencrypt-acme-challenge/.well-known/acme-challenge/RWhZct77DJHBgXLb8bDB5pQEPmQzHSiBqiWseo7Q_MI 2024-12-07 16:37:31,613:DEBUG:certbot._internal.plugins.webroot:All challenges cleaned up 2024-12-07 16:37:31,613:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/opt/certbot/bin/certbot", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/main.py", line 19, in main return internal_main.main(cli_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 1894, in main return config.func(config, plugins) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 1600, in certonly lineage = _get_and_save_cert(le_client, config, domains, certname, lineage) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 143, in _get_and_save_cert lineage = le_client.obtain_and_enroll_certificate(domains, certname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 517, in obtain_and_enroll_certificate cert, chain, key, _ = self.obtain_certificate(domains) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 428, in obtain_certificate orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 496, in _get_order_and_authorizations authzr = self.auth_handler.handle_authorizations(orderr, self.config, best_effort) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort) File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations raise errors.AuthorizationError('Some challenges have failed.') certbot.errors.AuthorizationError: Some challenges have failed. 2024-12-07 16:37:31,615:ERROR:certbot._internal.log:Some challenges have failed.