rilles

˙ʎɐp ɹᴉǝɥʇ ǝʌɐɥ sʇɐq pɐlƃ ɯ,I ˙sʇɐq ǝʇɐᴉɔǝɹddɐ op I puɐ sǝᴉʌoɯ uɐɯʇɐq ǝɥʇ llɐ pǝɥɔʇɐʍ ǝʌ,I

I searched for any other mention of this, but could find none. I just bought an external Seagate 18TB drive and plugged it into my unraid box (6.1.1.5 on a i5-10400) to preclear it Using UD preclear - the system segfaults after a few minutes Using the binhex docker preclear it segaults after a few hours No diagnostics dump because once the system faults, it goes into a weird voodoo half baked state, somethings work but most unraid actions do not work. Any ideas why an external usb drive would blow up unraid? I dumped the syslog below. Mar 27 23:19:02 Tower kernel: general protection fault, probably for non-canonical address 0xfff7888533ab41d8: 0000 [#1] PREEMPT SMP NOPTI Mar 27 23:19:02 Tower kernel: CPU: 3 PID: 4124 Comm: usb-storage Not tainted 5.19.17-Unraid #2 Mar 27 23:19:02 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. B460MDS3H/B460M DS3H, BIOS F5 11/23/2021 Mar 27 23:19:02 Tower kernel: RIP: 0010:end_bio_bh_io_sync+0x1e/0x34 Mar 27 23:19:02 Tower kernel: Code: cc 83 c8 ff 0f bd c7 c3 cc cc cc cc 0f 1f 44 00 00 53 48 89 fb 48 8b 7f 40 f6 43 14 10 74 05 f0 80 4f 01 10 31 f6 80 7b 18 00 <48> 8b 47 38 40 0f 94 c6 ff d0 0f 1f 00 48 89 df 5b e9 41 19 16 00 Mar 27 23:19:02 Tower kernel: RSP: 0018:ffffc90000d63de8 EFLAGS: 00010246 Mar 27 23:19:02 Tower kernel: RAX: ffffffff8126075f RBX: ffff8887abe3ff00 RCX: 0000000080150001 Mar 27 23:19:02 Tower kernel: RDX: ffff8881043cc200 RSI: 0000000000000000 RDI: fff7888533ab41a0 Mar 27 23:19:02 Tower kernel: RBP: ffff8887abe3ff00 R08: ffff8887abe3fe40 R09: 0000000080150001 Mar 27 23:19:02 Tower kernel: R10: ffff8887abe3fe40 R11: 0000000000030d80 R12: 0000000000000000 Mar 27 23:19:02 Tower kernel: R13: 0000000000040e00 R14: 0000000000000200 R15: ffff88816939b000 Mar 27 23:19:02 Tower kernel: FS: 0000000000000000(0000) GS:ffff88883f2c0000(0000) knlGS:0000000000000000 Mar 27 23:19:02 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 27 23:19:02 Tower kernel: CR2: 00007f806f234000 CR3: 000000000420a004 CR4: 00000000007726e0 Mar 27 23:19:02 Tower kernel: PKRU: 55555554 Mar 27 23:19:02 Tower kernel: Call Trace: Mar 27 23:19:02 Tower kernel: <TASK> Mar 27 23:19:02 Tower kernel: blk_update_request+0x22c/0x2e2 Mar 27 23:19:02 Tower kernel: ? usb_stor_invoke_transport+0x3a/0x426 Mar 27 23:19:02 Tower kernel: scsi_end_request+0x27/0xf0 Mar 27 23:19:02 Tower kernel: scsi_io_completion+0x15f/0x466 Mar 27 23:19:02 Tower kernel: usb_stor_control_thread+0x1b8/0x200 Mar 27 23:19:02 Tower kernel: ? preempt_latency_start+0x2b/0x46 Mar 27 23:19:02 Tower kernel: ? _raw_spin_lock_irqsave+0x2c/0x37 Mar 27 23:19:02 Tower kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a Mar 27 23:19:02 Tower kernel: ? fill_inquiry_response+0x14/0x14 Mar 27 23:19:02 Tower kernel: kthread+0xe4/0xef Mar 27 23:19:02 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Mar 27 23:19:02 Tower kernel: ret_from_fork+0x1f/0x30 Mar 27 23:19:02 Tower kernel: </TASK> Mar 27 23:19:02 Tower kernel: Modules linked in: rpcsec_gss_krb5 xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs dm_crypt dm_mod dax nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc i915 iosf_mbi drm_buddy i2c_algo_bit ttm x86_pkg_temp_thermal intel_powerclamp drm_display_helper coretemp gigabyte_wmi wmi_bmof kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore drm_kms_helper i2c_i801 nvme i2c_smbus r8169 drm ahci nvme_core mpt3sas realtek libahci intel_gtt agpgart i2c_core input_leds led_class raid_class scsi_transport_sas syscopyarea sysfillrect Mar 27 23:19:02 Tower kernel: sysimgblt fb_sys_fops wmi thermal fan video backlight acpi_tad acpi_pad button unix Mar 27 23:19:02 Tower kernel: ---[ end trace 0000000000000000 ]--- Mar 27 23:19:02 Tower kernel: RIP: 0010:end_bio_bh_io_sync+0x1e/0x34 Mar 27 23:19:02 Tower kernel: Code: cc 83 c8 ff 0f bd c7 c3 cc cc cc cc 0f 1f 44 00 00 53 48 89 fb 48 8b 7f 40 f6 43 14 10 74 05 f0 80 4f 01 10 31 f6 80 7b 18 00 <48> 8b 47 38 40 0f 94 c6 ff d0 0f 1f 00 48 89 df 5b e9 41 19 16 00 Mar 27 23:19:02 Tower kernel: RSP: 0018:ffffc90000d63de8 EFLAGS: 00010246 Mar 27 23:19:02 Tower kernel: RAX: ffffffff8126075f RBX: ffff8887abe3ff00 RCX: 0000000080150001 Mar 27 23:19:02 Tower kernel: RDX: ffff8881043cc200 RSI: 0000000000000000 RDI: fff7888533ab41a0 Mar 27 23:19:02 Tower kernel: RBP: ffff8887abe3ff00 R08: ffff8887abe3fe40 R09: 0000000080150001 Mar 27 23:19:02 Tower kernel: R10: ffff8887abe3fe40 R11: 0000000000030d80 R12: 0000000000000000 Mar 27 23:19:02 Tower kernel: R13: 0000000000040e00 R14: 0000000000000200 R15: ffff88816939b000 Mar 27 23:19:02 Tower kernel: FS: 0000000000000000(0000) GS:ffff88883f2c0000(0000) knlGS:0000000000000000 Mar 27 23:19:02 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 27 23:19:02 Tower kernel: CR2: 00007f806f234000 CR3: 00000001a39be005 CR4: 00000000007726e0 Mar 27 23:19:02 Tower kernel: PKRU: 55555554

mine was busted too -- woot to sharrensen for the advice. backup again.

I'm using this mod for an intel comet lake i5-10400 / b460 chipset - works great.

bzfirmware was the missing bit. all good - hope to do some load testing now to see if my AMD still crashes with this newer then 6.8.3 kernel. thanks for doing this.

After lots of googling and some guessing - this worked modprobe.blacklist=amdgpu

I have a AMD 2200G with built in graphics. The machine boots up fine but the display stops working at this point Tower kernel: amdgpu 0000:09:00.0: Direct firmware load for amdgpu/raven_gpu_info.bin failed with error -2 Tower kernel: amdgpu 0000:09:00.0: amdgpu: Failed to load gpu_info firmware "amdgpu/raven_gpu_info.bin" Tower kernel: amdgpu 0000:09:00.0: amdgpu: Fatal error during GPU init Tower kernel: [drm] amdgpu: finishing device. Tower kernel: amdgpu: probe of 0000:09:00.0 failed with error -2 what do I need to add to stop the amdgpu fail?

I have tried this headless kodi time to time, its so close to working but no cigar. I finally setup a VM with xubuntu and loaded kodi on top of that. its very clunky to setup and use via the virtual console - but it works to update my mariadb on a regular schedule.

after lots of reading and not understanding why my unraid was acting strange - it is possible that a quirk of UD may be causing my issue. overview of unraid issue: To protect the data on my drives I enabled encryption. To enable autostart I inserted into /boot/config/go the line "cp /boot/config/keyfile /root" This seemed to go well with the drive autostarting on bootup. Then I bought a giant usb drive to use as an array backup, so I installed unassigned devices and UD plus so that I could also encrypt the usb drive. I do a reboot and all is not well. The UD luks encrypted usb drive does auto-mount... but my array no longer auto starts its asking me for a keyfile or keyphrase. If I open a console window and go into /root the keyfile is not there. If I pass in a keyfile from the webGui then it start and the keyfile is in /root does anyone have any idea what is going on? why is the keyfile not getting copied from the go script (or why is it getting deleted after emhttp starts)? is UD somehow doing something with the encrypted UD that touches /root/keyfile in some way?

that was the issue. when I first started dong this I did not realize that letsencrypt requires the rproxy to allow inbound access from the internet.

Assuming you have a cache drive. "/mnt/cache/appdata/caddy/config" <-- this is the directory to put your config file and certs into. I remember some ancient days when I had to use vi - go to the spot you want to edit and press "i" and then edit when you are done editing press escape. press ":" and then "w" to save the file and then ":" and then "q" to exit. root@Tower:/mnt/cache/appdata/caddy/config# v -rw-r--r-- 1 root root 693 Apr 18 15:35 Caddyfile -rw-rw-rw- 1 nobody users 1350 Apr 18 15:16 caddy-selfsigned.crt -rw-rw-rw- 1 nobody users 1704 Apr 18 15:16 caddy-selfsigned.key here is my copy of the "Caddyfile" config file (192.168.1.243 is the IP of my unraid server) :443 { # tls ${SSLCERTIFICATE} ${SSLKEY} tls caddy-selfsigned.crt caddy-selfsigned.key # or 'tls self_signed' to generate a self-signed certificate # This setting may have compatibility issues with some browsers # (e.g., attachment downloading on Firefox). Try disabling this # if you encounter issues. gzip # The negotiation endpoint is also proxied to Rocket proxy /notifications/hub/negotiate 192.168.1.243:8008 { transparent } # Notifications redirected to the websockets server proxy /notifications/hub 192.168.1.243:3012 { websocket } # Proxy the Root directory to Rocket proxy / 192.168.1.243:8008 { transparent } }

"tls self_signed" is for testing only and only lasts 7 days. created a 5 year self signed cert in Ubuntu: openssl req -x509 -nodes -days 1825 -newkey rsa:2048 -keyout caddy-selfsigned.key -out caddy-selfsigned.crt copied it to unraid file share, copy it from the share to /mnt/cache/appdata/caddy start caddy, launch console and edit CaddyFile with vi. change "tls self_signed" to "tls caddy-selfsigned.key caddy-selfsigned.crt" restart caddy and away you go. I tried some of the ngix dockers but I could not get any of them to work, either due to letsencrypt errors or just to hard and fiddly for an amateur.

just download this and trying to use this with bitwarden. Issue is I cannot seem to get a LetsEncrypt cert - every time I try to create one I get an "internal error". if I look at my proxy error its basically missing the .pem file (probably related to the error) edit: read through the above now understanding it a bit better - no luck. giving its own unique IP has the same error.

So I watch space invaders video and a few others and my head was exploding in anger and frustration. I don't want to expose this to the internet, I don't want a domain and I don't need a real cert, waaay too much fiddling. So scraped the bitwarden_rs docker site and they have a few easier suggestions - the one I used was Caddy 1.x (also a unraid docker) https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples you can't use localhost so make sure you enter your server IP address, and I enabled "tls self_signed" works fine for me now on all browsers.

I'm using Ubuntu and firefox with Bitwarden over port 80 and it has been working fine, that is until the last day or two it appears firefox (v75.0) was auto updated and now it has the same issue as chrome. When I try to login a little red box appears "This browser requires HTTPS to use the web vault. Check the bitward_rs wiki for details on how to enable it" I guess I'm going to watch to watch spaceinvaders video to setup a proxy. grr.