Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

stubennatter

Members
  • Joined

  • Last visited

  1. wie oben geschrieben ist es mein zweit Unraid um mal bissel was zu testen oder um mal paar Tage was zu erledigen. Verstehe nur nicht so recht was hier passiert ist, dass es nicht mehr geht, denn es ging ja mal ohne das ich direkt etwas an den Settings geändert hatte...
  2. okay auf UEFI umgestellt, damit BAR aktiviert, leider gleicher Fehler weiterhin
  3. Danke für eure Hilfe, hatte das auch bei der Suche gefunden und habe das neuste Bios drauf, vom 22.2.24 Hatte den gleichen Fehler mit einem anderen Z790 Board genauso vorher, habe Grafikkarte und Board gewechselt, alles auf 0 gesetzt aber den gleichen Fehler. Auch beim anderen board hatte ich das neuste Bios drauf installiert. Dort hatte ich halt erst die Unraid Version im Verdacht, da es ja mal lief und ich nach einer Weile auf die 6.12.8 geupdate. 4G ist aktiviert, BAR ist deaktiviert und ausgegraut im Bios
  4. sorry kann jetzt erst antworten, habe auch noch mal bissel probiert, es ist nicht mal ein Docker gestartet, hatte alles sauber und nur nvidia Treiber drauf, jetzt mal gpu info installiert und dabei gab es auch schon Fehlermeldungen. Datei ist angehangen tower-diagnostics-20240304-1634.zip
  5. Hallo, habe eine zweite Unraid Lizenz und immer mal wieder für Vorrübergehende Projekte genutzt. Aber hatte es letztens mal wieder nutzen wollen und bekomme permanent Fehler, auch ein wechsel der ganzen Hardware brachte keinen Erfolg. vielleicht liegt es auch an der Version. Jedenfalls sobald ich den einen Docker Container starten möchte, der nutzt die Nvidia GPU, gibt es permanet Fehler im Log und der Container funktioniert auch nicht wie er sollte. Unraid 6.12.8 Mar 3 10:33:48 Tower kernel: ACPI Warning: \_SB.PC00.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:48 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:48 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:48 Tower kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. Mar 3 10:33:49 Tower kernel: nvidia-uvm: Loaded the UVM driver, major device number 238. Mar 3 10:33:49 Tower kernel: eth0: renamed from veth642bccc Mar 3 10:33:49 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth37fa6e6: link becomes ready Mar 3 10:33:49 Tower kernel: docker0: port 1(veth37fa6e6) entered blocking state Mar 3 10:33:49 Tower kernel: docker0: port 1(veth37fa6e6) entered forwarding state Mar 3 10:33:49 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:49 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 3 10:33:49 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 3 10:33:49 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 3 10:33:49 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Grüße
  6. is there any option to collect the HDD temps?
  7. upgrade with one more power supply fix the problem
  8. Hi, thanks a lot. Works perfect.
  9. Hi, I use 6.11.5 and want update to 6.12 I had 2x zpool as z1 on 6.11.5 with the Plugin created. After Update I must add a new pool and select all devices from my zpool before. So two question: 1. the name of the new pool must set to the name of the zpool name or could it be a new name? 2. must I select z1 in the setup or how it works? Thanks.
  10. It would be a power problem. but I need more time to upgrade.
  11. hm okay Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] 4096-byte physical blocks Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] Write Protect is off Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] Mode Sense: 7f 00 10 08 Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 18 12:56:28 ServerStation kernel: sdet: sdet1 sdet9 Oct 18 12:56:28 ServerStation kernel: sd 8:0:64:0: [sdet] Attached SCSI disk Oct 18 12:56:29 ServerStation zed[41320]: zed_udev_monitor: skip /dev/sdet since it has a gpt partition already Oct 18 12:56:31 ServerStation zed[41320]: zed_udev_monitor: /dev/sdet9 sectors 16384 < 131072 (minimum) Oct 18 12:56:31 ServerStation zed[41320]: #011dev_name: /dev/sdet1 Oct 18 12:56:31 ServerStation zed[41320]: #011path: /devices/pci0000:80/0000:80:03.1/0000:85:00.0/host8/port-8:1/expander-8:1/port-8:1:31/end_device-8:1:31/target8:0:64/8:0:64:0/block/sdet/sdet1 Oct 18 12:57:40 ServerStation emhttpd: TOSHIBA_MG09ACA18TE_52G0A0R8FJDH (sdet) 512 35156656128 Oct 18 12:57:40 ServerStation emhttpd: read SMART /dev/sdet
  12. the power problem was because I reboot the server for clean diagnostic and after that all disks runing and no UNAVAIL and log from each disk had no power problem, but scrub is still in progress and not changed % pool: fsp2 state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sat Oct 14 11:36:17 2023 27.8T scanned at 2.72G/s, 25.8T issued at 2.52G/s, 261T total 34.2M resilvered, 9.88% done, 1 days 02:32:23 to go config: NAME STATE READ WRITE CKSUM fsp2 ONLINE 0 0 0 raidz1-0 ONLINE 1.05K 876 0 ata-ST18000NM000J-2TV103_ZR5CJZEG ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CL9NE ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CPHVP ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CSXJ4 ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CVH9N ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CW3JS ONLINE 0 0 0 (resilvering) ata-ST18000NM000J-2TV103_ZR5CWN6K ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_82T0A07EFJDH ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_82T0A06YFJDH ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_52G0A113FJDH ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_62X0A0B9FJDH ONLINE 0 0 2 (resilvering) ata-TOSHIBA_MG09ACA18TE_7280A02HFJDH ONLINE 0 0 2 (resilvering) ata-TOSHIBA_MG09ACA18TE_52G0A0R8FJDH ONLINE 1.26K 1.22K 0 (awaiting resilver) ata-TOSHIBA_MG09ACA18TE_62X0A0PGFJDH ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_82T0A04AFJDH ONLINE 0 0 0 (resilvering) ata-TOSHIBA_MG09ACA18TE_72A0A006FJDH ONLINE 2.54K 3.15K 2 (awaiting resilver)
  13. ok thank you, and scrub start automatic new?
  14. Live of Power down first?
  15. Sorry hat etwas gedauert. Bin unterwegs gewesen. serverstation-diagnostics-20231018-1443.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.