hawihoney

Members
  • Posts

    3416
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by hawihoney

  1. Ach das steckt einfach in mir drin. Wenn man Backup sagt, dann sollte man es auch richtig machen. Die Abwägung, ob ein Datum wichtiger als ein anderes ist, blockiert nur und im Zweifel ärgert man sich dann doch. Und der Aufwand ist lächerlich gering. Wie gesagt: Keine 10 Zeilen, und saubere Backups lassen ruhig schlafen.
  2. Davon muss man einfach ausgehen. Alles andere wäre fahrlässig. Bei Nextcloud/MariaDB und Plex/SQLite kann das sonst ziemlich in die Hose gehen. Außerdem sollte man jeweils 2-3 Sekunden Pause einbauen, damit sich die Caches oder Transaktionen "entladen". So mache ich das seit Jahren für Nextcloud/MariaDB: docker exec mariadb /usr/bin/mysqldump ... # Dump docker stop nextcloud docker stop mariadb rsync mariadb ... # appdata rsync nextcloud ... # appdata rsync Nextcloud ... # data docker start mariadb docker start nextcloud So hat man einen binären sowie einen SQL Dump der Datenbank plus beide appdata Folder plus Nextcloud data. Bei Plex gilt das ebenfalls (binär und dump der Datenbank plus appdata Folder): docker stop plex echo '.dump metadata_item_settings' | sqlite3 ... # Abspielstatus echo ".dump" | sqlite3 ... # Dump rsync plex ... # appdata docker start plex Da User Scripts alles parallel startet glühte mein Backup immer. Deshalb habe ich mir ein riesiges Python Script mit Arrays für tägliche, wöchentliche und monatliche Jobs gebaut. Läuft astrein.
  3. tree is a standard tool. Just try the following to see what it does: tree /mnt/disk1 I'm running dual parity, but in case three or more disks fail at once, I want to know what is lost and where it was stored.
  4. This! I'm running tree for all disks every night.
  5. In the past I did experience lots of SMB issues with big files or mass of data. What helped here: 1.) Fetch the data - don't push it. What I mean is: Initiate the copy from the Unraid machine, not from the Windows machine. 2.) Don't write to a user share, write to a disk share. 3.) If possible, combine both 1.) and 2.). This is my own experience. Since using this workaround I never had problems again.
  6. Thanks. But why is that switch called Pass-Through then? It has nothing to do with Pass-Through. It simply ignores disks with that activated switch. Wouldn't it be better called "Ignore" or "Don't mount"? IMHO it does suggest something that doesn't happen.
  7. Can pleae somebody explain the "pass-through" switch on the settings page of hard disks? I simply don't get it. I need to pass through several hard disks by id to a VM. These hard disks are shown within the Unassigned Disks area on Unraids main page. I've set the pass-through slider for these disks but they do not appear on the VM creation page. My understanding is, that a disk, that's set to pass-through, is blocked and available for pass-through selection on the VM page. Am I wrong? Is that pass-through slider simply misnamed and should be called "ignore".
  8. The file, OP did copy /mnt/user --> /mnt/user, was stored on cache already. I don't know what it is, but the user share layer seems to eat performance. That's my own personal experience. I never did measure that but it was a huge difference here. Plex with it's over 1 million metadata directories stored on the PCI NVMe is snappy since changing the directory entries from /mnt/user to /mnt/cache. As I wrote, I don't use user shares at all since some months.
  9. Nothing you want to hear: I had to ignore user shares to have "usual" speed on my PCI NVMe M.2 cache disks. In fact I changed all locations of Dockers and VMs from /mnt/user to /mnt/cache. No big deal to do and results in no more speed problems.
  10. Ah, thanks. Something like that should be added to the logs IMHO. Currently the read error is written to syslog, the positive rewrite should be mentioned after that as well.
  11. I'm currently running a parity check on a dual parity system. During that parity check one disk showed 128 read errors. What puzzles me now is, why didn't Unraid throw that disk out? And what happens with the data that couldn't be read? Was ist replaced from the parity disks? Is the data, that couldn't be read, still on that failing disk? Do the bits and bytes of both parity disks and the failing data disk still match or is there different data on these three disks now? Diagnostics attached. Thanks in advance. tower-diagnostics-20210110-0856.zip
  12. Since nearly a year I'm running TOSHIBA MG07ACA12TE (12 TB) drives in my arrays. Since over 3 years I'm running TOSHIBA HDWE160 (6 TB) as data drives. Never had a problem with Toshibas til now (knock on wood). Had some problems with WDC WD60EFRX (6 TB) in the past. Really long time runners in my arrays are these old ones: HGST HUS724020AL (2 TB). Really good stuff.
  13. New UD release from today flashes (repaints) it's area completely including it's headers every second. If I'm the only one who experiences that I can send a video. Unraid 6.8.3, Windows 10 and Android, Chrome.
  14. Stupid question to the post above. Linux seems to see AW11. Is it possible to mount it manually: root@Tower:~# ls /dev/disk/by-label AW11@ UNRAID@
  15. The same as in the screenshot of the main page above. UD shows sdb1/AW11 while mount reports sdb1/Elements. sdb1/Elements is not attached to mainboard. Currently attached, but not mounted and not useable, is sdb1/AW11. Unraid is completely out of sync here. Can't believe that something like that still happens.
  16. Thanks. Did that and received several errors. Something I need to care about? ***EDIT*** Did remove unmodified config and example files and did let Swag to fetch new ones - except one (site-confs/default.conf). Looks good so far. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so') Server ready
  17. root@Tower:~# mount | grep sdb /dev/sdb1 on /mnt/disks/Elements type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096) root@Tower:~# umount /dev/sdb1 umount: /mnt/disks/Elements: not mounted. Funny result.
  18. Reboot? Oh, sh*t. This is USB, disks can go offline. User simply remove them without unmounting before. Something they do on Windows, etc. all the time. Linux can't work with that? Unbelievable. In my case I could not Unmount thru the UD plugin. It simply didn't unmount. So I simply removed the device. Thanks.
  19. I want to migrate from the Letsencrypt docker to the SWAG docker. All docs and even Spaceinvaderones' YT tutorial show how to replace folders like dns-conf, proxy-conf, etc. But no (!) doc I found says a word about the site-confs folder. This is the only one with changes here. Is there a reason why the site-confs folder is not mentioned at all for the migration process? Can I simply move the files over to SWAG? Here are SIOs commands: https://drive.google.com/file/d/1Ho3w3ksNbZNC3HbUYU3U4I0r0hrVlZHE/view
  20. Thanks, did it. Thought when mount shows a device but I can't umount it, it must be a Unraid/Linux problem.
  21. Please have a look at the two screenshots. As you can see there's a device sdb with the partition AW11 shown on the Main tab. Two historical devices/partition U33 and R15 are visible as well. On the console you can see a partition ELEMENTAL on sdb. This is an old already removed USB device. I can't umount that device. The AW11 USB stick is attached currently and shown on the Main tab. BUT it's missing in the mount list. ELEMENTAL is shown instead. Needless to say that if I navigate to AW11 on the Main tab the folder/file list is empty. This is the only free USB port I'm using. No way to swap USB ports, because the rest is blocked with USB license sticks passed thru to VMs. What's happening here? And is there a way to fix that without rebooting the server? Any help is highly appreciated. Diagnostics attached. tower-diagnostics-20201223-1107.zip
  22. I'm not quiet sure if this is an Unraid or Unassigned Devices problem. As a Linux noob it looks as an Unraid thing to me. Please have a look at the two screenshots. As you can see there's a device sdb with the partition AW11 shown on the Main tab. Two historical devices/partition U33 and R15 are visible as well. On the console you can see a partition ELEMENTAL on sdb. This is an old already removed USB device. I can't umount that device. The AW11 USB stick is attached currently and shown on the Main tab. BUT it's missing in the mount list. ELEMENTAL is shown instead. Needless to say that if I navigate to AW11 on the Main tab the folder/file list is empty. This is the only free USB port I'm using. No way to swap USB ports, because the rest is blocked with USB license sticks passed thru to VMs. What's happening here? And is there a way to fix that without rebooting the server? Any help is highly appreciated. Diagnostics attached. tower-diagnostics-20201223-1107.zip
  23. Thanks in advance. IMHO: Don't modify user content in an entryfield automatically. It becomes a can of worms to decide and filter what's unwanted and what's intended. If you need to, check for unwanted characters and simply popup a small dialog "Non-ASCII characters detected. Are you sure?" and let the user decide.
  24. [BUG] German Umlauts [äöüÄÖÜß] disappear during save I do have some scripts that do require German Umlauts (see above). I can put them into the big edit field but they disappear after saving the user script. For example: Within a user script I do call a python script to export data. I enter something like that (shortened): python3 [path]/ExportData.py -l Hörbücher After saving and reopening the script this is what became stored: python3 [path]/ExportData.py -l Hrbcher Thanks.
  25. Just went there to look. That's what I found: It took me 30 seconds to find out that this is nothing I can consider right now. Will be ready in the same timeframe like muItiple array pools in Unraid I guess