lhw1221

okay seems to be good but now i ownly got 12 tb of 13 tb i probebly lost some data but hey the drive is still ser and the most data seems to be back thnx for your help guys

it seems to have workt next step is to try monting again ?? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 240128, counted 63040 sb_ifree 27898, counted 39218 sb_fdblocks 1201212561, counted 1405852858 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 5 - agno = 2 - agno = 1 - agno = 4 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (3:1067419) is ahead of log (1:2). Format log to cycle 6. done

I just gona post te result her i did a the instruction recomendet for xfs using -nv Phase 1 - find and verify superblock... - block cache size set to 714080 entries Phase 2 - using internal log - zero log... zero_log: head block 1069105 tail block 1069083 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_icount 240128, counted 63040 sb_ifree 27898, counted 39218 sb_fdblocks 1201212561, counted 1405852858 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 - agno = 4 - agno = 5 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Thu Mar 9 11:02:56 2023 Phase Start End Duration Phase 1: 03/09 11:02:49 03/09 11:02:49 Phase 2: 03/09 11:02:49 03/09 11:02:49 Phase 3: 03/09 11:02:49 03/09 11:02:53 4 seconds Phase 4: 03/09 11:02:53 03/09 11:02:53 Phase 5: Skipped Phase 6: 03/09 11:02:53 03/09 11:02:56 3 seconds Phase 7: 03/09 11:02:56 03/09 11:02:56 Total run time: 7 seconds

hello to make it short. i was moving some data, and cleaning and first, i got ghost files that i could not move files (was an rsync error). then everything how ever got worse. So at one point, I restarted the machine but had to attend to something else. But unraid does always a parity sync when starts, so when i came back to it a day later i found: Disk 2: Unmountable: Wrong or no file system and unraid told me it found sync errors that it hat fixed. Sadly i can´t just format it and rebuild, cause it turns out ther is data on that drive i don´t have a backup of. if anyone has an idea pls help i did not try anything else befor the error, i tried doing a backup but that gave me yet again a rsync error.

hello guys i did not find a Fitting awnser to my problem so i ask. i try to add or createn the a container whit homeassistant-supervised based one home assistant core. cause i want the abillety to use plugins etc. however i have not enoght expiriance whit docker or unraid to accomplisch what i want. i wold know what to do on debian cause i have instructions (https://i12bretro.github.io/tutorials/0670.html). but not under unraid! can some on tell me waht i have to do under unraid?

Danke für die hilfe ich gucke mir das bei zeiten an

okay i still bootet again in savemode thistime however i disabled docker an the VM Manager (totaly forgot i can do that) taht work! i testet what made probles to be exact Docker works whitout issus however the VM manager as soon as powert up kills the GUI i checkt if is realy just VM manger by loding an backup So i can confirm VM manger seems to be the problem

okay guess i am stupid. XD i now startet up the array befor startig diagnostics. The shares also did mount. netweb-unraid-1-diagnostics-20220731-0439.zip

This is the entire problem i did start the array Like i said i can´t acces the GUI, as soon as the array is started up. So the log is from The Flash Drive. I have to rely on the OS auto creating the log when doing the shutdown. Wen it did not capture the array starting, ther is no way to my knowlege to creat a log file. i only have the CLI on the server directly (not even ssh) (i can send you the other 8 log from previus startups if that helps.)

netweb-unraid-1-diagnostics-20220731-1224.zip

hello the following, i have a strange problem with unraid. When i start the array, the web UI is gone and the sever is no longer controllable over the network (also ssh and telnet is dead). I can only access it directly through the CLI terminal on the machine itself. (which is cumbersome because unraid is always set to US keyboards but I only have de keyboards). Nevertheless the Docker containers are running (and are accessible), almost all of the shares are available and status notifications are still coming in. The only error message I had was that unraid told me my boot stick was corrupt. I replaced it with a new stick, then loaded a backup on it. But no matter which backup I loaded, even with a complete reinstallation, as soon as I started the array it is over. I am very confused because I have not really changed anything. The last time I accessed the server was a few weeks ago to power down a VM. i shold note that i am still kinda new to linux i know the most basic stuff but nothing to advaced Hardware info: ASUS - B85M-E RAM: 16Gg CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz + SATA card currently 8 Drives OS info: unRaid 6.10.3

Hallo folgendes ich suche eine Backup Lösung, womit ich teile meines unRaids automatisch(wöchentlich), auf ein anderes NAS sichern kann. Dabei ist recht egal welches Protokoll ich nutzten muss. Mir reicht wenn ein ähnliches Topic existiert auch ein einfacher link (nur habe ich jetzt nix passendes gefunden)

same problem the the other 2. Aso my knowlege about unraid and so one prevents me from fixing it. I have an working mount to my cloud but i can´t write i use the same script space invader used in his tutorial I also tried mounting OneDrive clouds, but this aprerently don´t work it told me to use the cache flagg. But then i got more complains from the script. Dose anyone knows what is going on. I red that puting the flag shold have fixt it but it don´t

a Question to your Open VPN Client Container it is only Dokumentet 2what if i want a container to only run over the vpn client". But waht if i want to use it to comunicate whit my my unraid server over VPN or use it on an docker Container for an second Connection. is ther any Dokumentation or anything for that ?

hello i did the unriad update today and marinaDB stopt working (not even starting) i have an backup of the my unraid flash, but MariaDB dies even if i do an update of the Container itselve. until now i just ignor the problem and just did not do an update of the container. But it seems i can´t even update unraid. I have no plan About DB Server in General Pls help Protokoll: 022-06-25 6:27:38 0 [Warning] Can't create test file /var/lib/mysql/0c5318a0e27e.lower-test /usr/sbin/mariadbd: Can't change dir to '/var/lib/mysql/' (Errcode: 13 "Permission denied") 2022-06-25 6:27:38 0 [ERROR] Aborting 2022-06-25 6:28:11 0 [Warning] Can't create test file /var/lib/mysql/0c5318a0e27e.lower-test /usr/sbin/mariadbd: Can't change dir to '/var/lib/mysql/' (Errcode: 13 "Permission denied") 2022-06-25 6:28:11 0 [ERROR] Aborting shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & and use the command line tool /usr/bin/mariadb to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /var/lib/mysql/ that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at https://mariadb.org/jira 2022-06-25 06:27:38-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started. 2022-06-25 06:27:38-07:00 [Note] [Entrypoint]: Initializing database files Installation of system tables failed! Examine the logs in /var/lib/mysql/ for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mariadb-install-db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & and use the command line tool /usr/bin/mariadb to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /var/lib/mysql/ that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at https://mariadb.org/jira 2022-06-25 06:28:11-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started. 2022-06-25 06:28:11-07:00 [Note] [Entrypoint]: Initializing database files