All Activity

This stream auto-updates

  1. Past hour
  2. I had 2 drives part of my cache pool. Upon reboot the system said "Unmountable: Unsupported or no file system" Decided to remove one drive from the pool to see if it would start, same error. If I were to re-add that 2nd drive it's saying it will format it. Not sure what to do next without losing my data. unraid-diagnostics-20240329-0710.zip
  3. this is log from previous update attila-diagnostics-20240329-1405.zip
  4. Hi @DoINeedATag, xfs_frs is running when the script starts, and my drives look like this: root@Tower:~# blkid | grep xfs /dev/sdf1: UUID="" BLOCK_SIZE="4096" TYPE="xfs" PARTUUID="" /dev/sdd1: UUID="" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="" /dev/md2p1: UUID="" BLOCK_SIZE="512" TYPE="xfs" /dev/md1p1: UUID="" BLOCK_SIZE="4096" TYPE="xfs" /dev/sdg1: UUID="" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="" /dev/sde1: UUID="" BLOCK_SIZE="4096" TYPE="xfs" PARTUUID="" /dev/md3p1: UUID="" BLOCK_SIZE="512" TYPE="xfs" I tried ruinniong the script and it was blocked by the parity, I disabled the setting that waits for parity and now it seems to be doing something. Search for HDDs... Found HDD with id md1p1 (added) Found HDD with id md2p1 (added) Found HDD with id md3p1 (added) Content of /tmp/.xfs_mtab: /dev/md1p1 /mnt/disk1 xfs rw,noatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/md2p1 /mnt/disk2 xfs rw,noatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/md3p1 /mnt/disk3 xfs rw,noatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 I am going to check back in 2 hours to see if it did anything. Thanks for your help so far
  5. sorry didnt see u need log from previous update , i got log from this new update attila-diagnostics-20240329-1355.zip
  6. I'm guessing this docker is pretty dead in the water
  7. Danke dir dann werde ich das berücksichtigen
  8. Hi HGWBLN Ich biete hier gerne Hilfe an. So wie ich das Verstehe wird Automount nichts bringen, da das NAS halt nicht immer online ist.. Natürlich wäre es deswegen sinnvoll LuckBackup auf dem NAS zu installieren (falls möglich) jedoch ist es auch machbar per Skript. Ob LuckyBackup wirklich neu gestartet werden muss, bin ich mir wirklich nicht sicher.. Ich denke eigentlich nicht. Dennoch hier mal ein Template (weil ich einfach gern Skripte) 😁 Grüsse
  9. Guten Nachmittag zusammen, ich bin am überlegen mir für meinen Unraid Server gebrauchte 12TB Festplatten über Ebay zu kaufen. Es handelt sich um Seagate oder Western Digital Platten, anbei mal ein Beispiellink der Seagate Platten: https://www.ebay.de/itm/355135475369?_trkparms=amclksrc%3DITM%26aid%3D777008%26algo%3DPERSONAL.TOPIC%26ao%3D1%26asc%3D20230811123857%26meid%3Dc7db5f2414964a3cbec085b424f6d32f%26pid%3D101770%26rk%3D1%26rkt%3D1%26itm%3D355135475369%26pmt%3D0%26noa%3D1%26pg%3D4375194%26algv%3DRecentlyViewedItemsV2%26brand%3DSeagate&_trksid=p4375194.c101770.m146925&_trkparms=parentrq%3A8a76320e18e0a8d1cad7ad68ffff86de|pageci%3Abc91a30e-edd2-11ee-a321-467c68b83f31|iid%3A1|vlpname%3Avlp_homepage Der Verkäufer macht einen sehr guten Eindruck, die Bewertungen sprechen für sich, auch hatte ich schon netten Kontakt. Das besondere ist, das es 10 Jahre lang eine neue Platte bei defekt gibt, wenn ich das so richtig verstanden habe Im Falle eines Defektes müsste die Platte zu Ihm gesendet werden, nun ist es ja bei Unraid so, dass die Daten blank abgelegt werden und so vielleich tnoch jemand an die Daten kommen könnte evtl. Das möchte ich vermeiden. Daher habe ich mich gefragt ob ich XFS Verschlüsselt auswählen kann. Das System ist noch nicht aufgesetzt ich habe bisher nur mit rumgespielt. Ich würde mich sehr über Erfahrungen von euch freuen, ob es Sinn macht und wie man das am besten Umsetzt, über die Einstellungen oder bei jeder Platte. Und gibt es risiken? Oder sollte man das ganze über ein Plugin lösen? Über eure Rückmeldungen würde ich mich sehr freuen und wünsche euch schöne Ostertage Viele Grüße
  10. tank-diagnostics-20240329-0941.zip Updated OS. Diag attached
  11. Do you mean something different to the current Unraid Connect feature?
  12. Thanks so much. Will carry out the fixes once the parity check has completed.
  13. root@Tank:~# cat /var/log/Xorg.0.log [ 49.385] X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 [ 49.385] Current Operating System: Linux Tank 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 [ 49.385] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot,/bzroot-gui [ 49.385] [ 49.385] Current version of pixman: 0.42.2 [ 49.385] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 49.385] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 49.385] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 27 16:40:48 2024 [ 49.387] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 49.397] (==) No Layout section. Using the first Screen section. [ 49.397] (==) No screen section available. Using defaults. [ 49.397] (**) |-->Screen "Default Screen Section" (0) [ 49.397] (**) | |-->Monitor "<default monitor>" [ 49.397] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 49.397] (==) Automatically adding devices [ 49.397] (==) Automatically enabling devices [ 49.397] (==) Automatically adding GPU devices [ 49.397] (==) Automatically binding GPU devices [ 49.397] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 49.397] (++) FontPath set to: /usr/share/fonts/TTF [ 49.397] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 49.397] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 49.397] (II) Loader magic: 0x62dd40 [ 49.397] (II) Module ABI versions: [ 49.397] X.Org ANSI C Emulation: 0.4 [ 49.397] X.Org Video Driver: 25.2 [ 49.397] X.Org XInput driver : 24.4 [ 49.397] X.Org Server Extension : 10.0 [ 49.401] (--) PCI:*(2@0:0:0) 10de:0659:10de:063a rev 161, Mem @ 0xfa000000/16777216, 0xa0000000/536870912, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072 [ 49.401] (II) Open ACPI successful (/var/run/acpid.socket) [ 49.401] (II) LoadModule: "glx" [ 49.402] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 49.413] (II) Module glx: vendor="X.Org Foundation" [ 49.413] compiled for 1.21.1.7, module version = 1.0.0 [ 49.413] ABI class: X.Org Server Extension, version 10.0 [ 49.539] (==) Matched nouveau as autoconfigured driver 0 [ 49.539] (==) Matched nv as autoconfigured driver 1 [ 49.539] (==) Matched modesetting as autoconfigured driver 2 [ 49.539] (==) Matched fbdev as autoconfigured driver 3 [ 49.539] (==) Matched vesa as autoconfigured driver 4 [ 49.539] (==) Assigned the driver to the xf86ConfigLayout [ 49.539] (II) LoadModule: "nouveau" [ 49.539] (WW) Warning, couldn't open module nouveau [ 49.539] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 49.539] (II) LoadModule: "nv" [ 49.540] (WW) Warning, couldn't open module nv [ 49.540] (EE) Failed to load module "nv" (module does not exist, 0) [ 49.540] (II) LoadModule: "modesetting" [ 49.540] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 49.546] (II) Module modesetting: vendor="X.Org Foundation" [ 49.546] compiled for 1.21.1.7, module version = 1.21.1 [ 49.546] Module class: X.Org Video Driver [ 49.546] ABI class: X.Org Video Driver, version 25.2 [ 49.546] (II) LoadModule: "fbdev" [ 49.547] (WW) Warning, couldn't open module fbdev [ 49.547] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 49.547] (II) LoadModule: "vesa" [ 49.547] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 49.550] (II) Module vesa: vendor="X.Org Foundation" [ 49.550] compiled for 1.21.1.4, module version = 2.6.0 [ 49.550] Module class: X.Org Video Driver [ 49.550] ABI class: X.Org Video Driver, version 25.2 [ 49.550] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 49.550] (II) VESA: driver for VESA chipsets: vesa [ 49.550] (++) using VT number 7 [ 49.552] (EE) open /dev/dri/card0: No such file or directory [ 49.552] (WW) Falling back to old probe method for modesetting [ 49.552] (EE) open /dev/dri/card0: No such file or directory [ 49.553] vesa: Refusing to run, Framebuffer or dri device present [ 49.553] (EE) Screen 0 deleted because of no matching config section. [ 49.553] (II) UnloadModule: "modesetting" [ 49.553] (EE) Device(s) detected, but none match those in the config file. [ 49.553] (EE) Fatal server error: [ 49.553] (EE) no screens found(EE) [ 49.553] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 49.553] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 49.553] (EE) [ 49.555] (EE) Server terminated with error (1). Closing log file. root@Tank:~#
  14. It would be quite trivial for Unraid to backup your usb and relevant server data to cloud storage. With compression it would take up pretty much no space and very little costs. Or they could just add a backup to GoogleDrive/Dropbox etc, you know like hundreds of totally free apps? so you then just insert a new usb with Unraid image, sign in, restore from backup. All of this is pretty basic stuff. Like I said tons of free apps done by single devs do this. Why can't a aid software with so many users do it?
  15. Closing this out, after 2 weeks no crashes. Seems very likely the UPS was just failing.
  16. Thank you so much - again. So enjoy the beer ;-D
  17. Today
  18. I'm having issues getting octoprint to connect to my printer. Unraid picks it up as a ch340 and presents it as /dev/ttyUSB0 and with an id in the by-id folder. I've tried the normal pass through option and also running the docker in privileged mode but it won't connect. I've tried different USB cables and also plugged the printer into my laptop and it definitely works that way. Does anyone have any suggestions?
  19. That's actually not true. If your Unraid USB died, as long as you had a backup of it, you can just load it on to another USB and your back to where you were. Furthermore, assuming you used the Unraid array, you can still read the drives off the server to recover your data if needed. Truenas boots off a dedicated drive, it doesn't write itself to all the devices on the server...just the drive, or drives (depending how you configured it) it was installed. However, if your boot drive fails, you can restore it, providing you have a back up copy of the config file. Oh and if you encrypted your pools on Truenas, you also have to make sure you also have a backup of the encryption key, because you will not be able to access your data if you failed to do so. It doesn't matter which option you use, all of them can fail and they all have their gotcha's when it comes to restoring them. I don't think it's reasonable to expect fixes within hours. It all depends on the issue, some can be easy to fix, while others can take far longer. It depends on the issue and how much is required to fix it. Furthermore, some issues can be outside the control of the devs, especially when your dealing with opensource. For example the ZFS data issue not long ago had to be fixed by the ZFS devs before it could be rolled out to all the solutions that use it. So sometimes, it's out of your control. Thankfully it was fixed relatively quickly, but sometimes that may not always be the case. It could be that the issues you had were easily fixable, but I wouldn't be expecting Proxomox devs to fix all issues within hours every time, it's unreasonable.
  20. OK, the machine was responsive long enough in Safe Mode so that I could click Start, but rebooted while starting the array. syslog
  21. Encrypted ram is the solution however 99% of unraid users will not have encrypted ram.
  22. Leider werden die nicht richtig erkannt....aber, ich wollte es mal probieren und werde demnächst wieder umbauen
  23. klick mal auf das Zahnrad und deaktiviere alles. Danach nur automount aktivieren. Die Freigabe brauchst du doch auch garnicht.
  1. Load more activity