danioj
Members
-
Joined
-
Last visited
Everything posted by danioj
-
That makes sense. Loss of data availability and time to fix an issue is I agree something you would prefer to not have to deal with. Hope all is back up and running for you.
-
I’ve stepped back from the forum in recent times but felt compelled to login and respond. (Un)Raid is not for backup, it’s for for availability. If you are sensitive to “Loss” of data you should take appropriate steps to back it up based on your risk appetite for the unexpected.
-
Thank you for the explanation.
-
Well, I’ll post the diags when I get home in the morning. But in the meantime, I can assure you my software version is: unRAID version 6.10.3 Pro Plugin version 2022.06.19 (with UAD Plus 2022.05.17 and UAD Preclear 2022.06.10 also installed) So does this mean that - irrespective of whether it’s a UAD disk or an Array disk - I have to disable spin down globally on an disk to do a SMART test? Seems weird almost a bug I’d say that the spin down function doesn’t recognise a SMART test as disk activity to prevent spin down.
-
I've since reset and the log isn't available. It's repeatable. Go and try and do a long SMART test on a disk that is connected via UAD.
-
I've observed an issue with the plugin that is repeatable. When trying to execute an extended SMART test (as part of my disk preparation methodology), the test will timeout (and never complete) as the disk is spun down after ~30 minutes (which I think is the normal unchangeable spin down delay for this plugin). For some reason the long smart test does not constitute activity and prevent the spin down. I don't think this is expected behaviour. unRAID version 6.10.3 Pro Plugin version 2022.06.19 (with UAD Plus 2022.05.17 and UAD Preclear 2022.06.10 also installed)
-
While “do-able” I think this is really poor advice. To the @JK252 please see the formal security recommendations from @limetech https://unraid.net/blog/unraid-server-security-best-practices TLDR: don’t expose your unRAID server to the internet. ESPECIALLY the maintenance GUI. Someone gets access and a web based command prompt with root permissions is a click away.
-
My2c. You should be able to do everything that you seek to do - yes those things has been done before. You can get a trial license and give it a go to see if it meets your needs. Generally speaking, unRAID is an excellent product supported by a great and active community. The only word of caution I would give you is, if you're primary interest is virtualization, then there might be better solutions out there for you (e.g. Proxmox). The primary reason for my note of caution is that unRAID requires that the storage array is "started" for other services (KVM, Docker etc) to start. In my experience, if there is a problem with an array disk then this often destabilizes the whole system until the disk problem is fixed. To put that into lay terms - your VM's and Docker Containers aren't going to start unless the array is started and will remain stable and operational as long as your array is in good health.
-
Hi All, I build my bother in law a server that was pretty much a mirror of mine (see sig). 2 years ago he run out of pace and wanted a cheap way to upgrade. I stuck in a Marvell PCIE SATA expander and managed to get it nice and stable. So much so, I even bought one. Long story short, he wants to upgrade again (cheapest possible route is the goal). No more space in the case, no more SATA ports "internally" and he doesn't want to upgrade smaller disks to higher capacity disks (my recommendation originally). He saw this: https://www.scorptec.com.au/product/hard-drives-&-ssds/enclosures/56549-ib-3640su3 Now, that Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) card also has 2 external eSATA ports. What sort of stability can he expect from hooking up the above JBOD dock to one of those ports. Will unRAID play nice? Thanks in advance. D
-
Vote Safari please - it needs some love.
-
Nice. Once the market normalises to the introduction of this size consumer drive, I wonder how that will change (if at all) the sweet spot drive for $/TB? For me, in Australia, 8TB is currently the sweet spot.
-
Hey @Squid hope you're doing ok man! I just - randomly - went to the CA AppData Backup / Restore Settings Page and saw this: "NOTE: USB Backup is deprecated on Unraid version 6.9.0 It is advised to use the Unraid.net plugin instead" I kind of get this, given unRAID's own new functionality. However, I would prefer to keep using your functionality instead. I assume (given the settings are still there and the backup keeps working each night) that this feature isn't truly depreciated. I hope you plan on keeping things going!! A local backup is desirable to me and your plugin makes it very easy.
-
I am raising this bug report to formally capture discussions on the 6.10.0-rc1 release thread relating to a possible bug. In summary, I have found that emhttpd keeps issuing read SMART events consistently to my array disks, which is spinning them up. The effect is that my usually spun down Array is pretty much spun up 24x7. Here are the relevant discussions in that thread. There was some suggestion that the CATurboWrite Plugin or my Marvel Controller (which only has 3 disks of 16 connected to it) could be at fault but I have since removed the plugin and have confirmed that this issue appears to also be experienced by another user @Mathervius who doesn't have a Marvel controller. Diagnostics are attached. Chosen minor but really feels a bit more than that. Having the array spun up all the time isn't desirable at all. unraid-diagnostics-20210902-1852.zip
-
Posting this here in the hope that it assists someone in the future. I host my instance of HomeAssistant in a VM on unRAID. I have recently purchased a ConBee II USB-Gateway so I can add Zigbee devices. I added the USB using the unRAID VM GUI, like I imagine most would, by just checking the tick box next to the device. This didn't work. While Home Assistant found the device, the integration would not add (there were communication errors). The trick was to add the device as a serial-usb device. AFAIK you cannot do this via the GUI. So I added the following code to my VM config: <serial type='dev'> <source path='/dev/serial/by-id/<yourusbid>'/> <target type='usb-serial' port='1'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='4'/> </serial> I was then able to add the integration easily. Interestingly, it didn't auto discover, but that's just an aside. Note, <yourusbid> can be found via the command line - it contains the device serial so its not to be posted.
-
I previously mentioned (on the release thread) that I had experienced a few random crashes since upgrading to 6.10.0-rc1. Each crash required a hard reset of the server making capturing diagnostics problematic. I enabled syslog mirroring though and have been able to capture the following error: Aug 24 08:58:01 unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window] Aug 24 08:58:01 unraid kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs Aug 24 09:56:19 unraid kernel: ------------[ cut here ]------------ Aug 24 09:56:19 unraid kernel: WARNING: CPU: 3 PID: 4821 at net/netfilter/nf_conntrack_core.c:1132 __nf_conntrack_confirm+0xa0/0x1eb [nf_conntrack] Aug 24 09:56:19 unraid kernel: Modules linked in: nvidia_modeset(PO) nvidia_uvm(PO) veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle xt_nat xt_tcpudp ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nvidia(PO) nct6775 hwmon_vid jc42 ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel drm crypto_simd cryptd rapl ahci ipmi_ssif agpgart intel_cstate mpt3sas syscopyarea intel_uncore sysfillrect sysimgblt i2c_i801 libahci fb_sys_fops input_leds intel_pch_thermal video i2c_algo_bit raid_class i2c_smbus scsi_transport_sas i2c_core led_class backlight thermal button acpi_ipmi fan ipmi_si [last unloaded: igb] Aug 24 09:56:19 unraid kernel: CPU: 3 PID: 4821 Comm: kworker/3:1 Tainted: P O 5.13.8-Unraid #1 Aug 24 09:56:19 unraid kernel: Hardware name: Supermicro X10SL7-F/X10SL7-F, BIOS 3.2 06/09/2018 Aug 24 09:56:19 unraid kernel: Workqueue: events macvlan_process_broadcast [macvlan] Aug 24 09:56:19 unraid kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x1eb [nf_conntrack] Aug 24 09:56:19 unraid kernel: Code: e8 7e f6 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 92 f4 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 c6 ed ff ff e8 09 f3 ff ff e9 22 01 Aug 24 09:56:19 unraid kernel: RSP: 0018:ffffc9000015cd20 EFLAGS: 00010202 Aug 24 09:56:19 unraid kernel: RAX: 0000000000000188 RBX: 0000000000008091 RCX: 00000000b4e7b974 Aug 24 09:56:19 unraid kernel: RDX: 0000000000000000 RSI: 000000000000033c RDI: ffffffffa0264eb0 Aug 24 09:56:19 unraid kernel: RBP: ffff888390b048c0 R08: 00000000f0e26b20 R09: ffff88818087a6a0 Aug 24 09:56:19 unraid kernel: R10: ffff88822f778040 R11: 0000000000000000 R12: 000000000000233c Aug 24 09:56:19 unraid kernel: R13: ffffffff82168b00 R14: 0000000000008091 R15: 0000000000000000 Aug 24 09:56:19 unraid kernel: FS: 0000000000000000(0000) GS:ffff8887ffcc0000(0000) knlGS:0000000000000000 Aug 24 09:56:19 unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 24 09:56:19 unraid kernel: CR2: 00007f9528a8af73 CR3: 000000000200a005 CR4: 00000000001726e0 Aug 24 09:56:19 unraid kernel: Call Trace: Aug 24 09:56:19 unraid kernel: <IRQ> Aug 24 09:56:19 unraid kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Aug 24 09:56:19 unraid kernel: nf_hook_slow+0x3e/0x93 Aug 24 09:56:19 unraid kernel: ? ip_protocol_deliver_rcu+0x115/0x115 Aug 24 09:56:19 unraid kernel: NF_HOOK.constprop.0+0x70/0xc8 Aug 24 09:56:19 unraid kernel: ? ip_protocol_deliver_rcu+0x115/0x115 Aug 24 09:56:19 unraid kernel: ip_sabotage_in+0x4c/0x59 [br_netfilter] Aug 24 09:56:19 unraid kernel: nf_hook_slow+0x3e/0x93 Aug 24 09:56:19 unraid kernel: ? ip_rcv_finish_core.constprop.0+0x351/0x351 Aug 24 09:56:19 unraid kernel: NF_HOOK.constprop.0+0x70/0xc8 Aug 24 09:56:19 unraid kernel: ? ip_rcv_finish_core.constprop.0+0x351/0x351 Aug 24 09:56:19 unraid kernel: __netif_receive_skb_one_core+0x77/0x98 Aug 24 09:56:19 unraid kernel: process_backlog+0xab/0x143 Aug 24 09:56:19 unraid kernel: __napi_poll+0x2a/0x114 Aug 24 09:56:19 unraid kernel: net_rx_action+0xe8/0x1f2 Aug 24 09:56:19 unraid kernel: __do_softirq+0xef/0x21b Aug 24 09:56:19 unraid kernel: do_softirq+0x50/0x68 Aug 24 09:56:19 unraid kernel: </IRQ> Aug 24 09:56:19 unraid kernel: netif_rx_ni+0x56/0x8b Aug 24 09:56:19 unraid kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 24 09:56:19 unraid kernel: macvlan_process_broadcast+0xc7/0x10b [macvlan] Aug 24 09:56:19 unraid kernel: process_one_work+0x196/0x274 Aug 24 09:56:19 unraid kernel: worker_thread+0x19c/0x240 Aug 24 09:56:19 unraid kernel: ? rescuer_thread+0x2a2/0x2a2 Aug 24 09:56:19 unraid kernel: kthread+0xdf/0xe4 Aug 24 09:56:19 unraid kernel: ? set_kthread_struct+0x32/0x32 Aug 24 09:56:19 unraid kernel: ret_from_fork+0x22/0x30 Aug 24 09:56:19 unraid kernel: ---[ end trace 44186f4b6dd2c3e1 ]--- After a reset, all is well and there appears to be no obvious regularity of trigger for the above. EDIT: set to urgent as per priority definition instructions given it was a server crash.
-
You spurred me on to do something I have been meaning to do @ezhik. You're absolutely right, the stock Intel cooler is a POS. It always annoyed me how the system would get to unstable temperatures in some conditions (e.g. 40 degree day and under load) so I have been meaning to switch it out. Well, now I have done so. Ordered a Noctua NH-L9i immediately after I read your post and it came today. It's now installed and stress tested and Temps are visibly lower both idle and under load. EDIT: I have my server in a dedicated comm's cupboard in my home office and I've just noticed (as I ponder the end of the day) how much quieter it is too.
-
I know this is an old topic but I felt compelled given recent activity. Since I built my server initially back in 2016: It has served me so well and has nary skipped a beat. Temps are still low and it has allowed me to scale up tremendously. Today ... well it makes me glad of the planning and time I put into deciding the right parts. When I built it I speculated that I would be able to get capacity up to 56TB with 8TB drives. Today may array has a usable size of 87TB and there are still some of the original 3TB WD Red's in there too (see my Sig). Heaps of head room especially with sizes of disks today. I think when I upgrade, well, I don't think I will. I think I will keep this bad boy going and retire it to be the backup server and build a new rig. I don't think I could part with it now! LOL! Some photos - then and now!
-
Haha. Gotchya. I'll keep an eye out. Thanks for the update.
-
@ljm42 I read some of your comments regarding this Plugin on the 6.10.0-rc1 thread. While I am going to maintain my distance from the remote access component of the Plugin - I do see value and convenience in the functionality to backup / restore the OS USB. The only thing that makes me pause is that, AFAIK, the backup functionality still doesn't use encryption. Are there any plans to introduce enrcyption?
-
Interesting reply. I think I will leave it there with remote access using this feature. Given the ease at which an OpenVPN or Wireguard (using either your router or unRAID itself - native or via a Docker) connection can be established I see no reason why I would change that. It was good to experiment though. Thank you @ljm42 for taking the time to make such a thorough reply, it is appreciated.
-
Interesting feature that I have just setup. Was interested in remote access. Got it up and running fine. For kicks, I went to https://<MYDOMAINNAME>:MYSERVERS_WAN_PORT It brought up the unraid gui. Is this expected? Thinking about it, I guess it is, given I've forwarded the random port number I chose to 443 of the unraid box. For some reason I had in my head that a remote connection not coming from the MyServers server would just be dropped. Im not sure how I feel about it though. Given we bang on (quite rightly) about how unraid isn't hardened for Internet access, isn't this an exploit just waiting to happen? Isn't this ultimately relying on the unraid standard login page being able to withstand an attack? I mean technically - given everyone knows that the login for unraid is 'root' and the port unraid is serving on via my wan address is just a simple port scan of my wan ip away - that would mean an attacker is a guess of my root password away from full access to my server. Yes, my root password is very very complex - I mean I don't even know it - but its still technically a possibility. Given the above and if the unraid gui is always exposed anyway - then why bother with MyServers for remote access at all? Why wouldn't I just access unRAID via that random port and just use my complex root password? Its feels a bit like creating a fancy way to access my house via next door (which has great security) when I still have a gate to the house hidden behind a bush somewhere (albeit largely non visible and hard to find - but not impossible) on the boundary protected by a complex code that someone can just bang away at for as long as possible until they guess it (or get bored). Maybe Im thinking about this all wrong and or the gui shouldn't come up when I access the port directly. *Shrug*. Think Ill turn this off for now and go back to using VPN for remote access. EDIT: Maybe this could be hardened (if it is expected) with a firewall rule that drops any connection made to that WAN port by anything other than the MyServers server? hmmm.
-
I woke this morning to SWAG not working. In the log I get this: nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 youtube-dl.subfolder.conf in the proxy-confs is there without a .sample at the end. I did not change this.
-
Thanks for the guidance. For now I’ve just switched to using the graphics card and have switched the BIOS to prioritise the card. All is well. If my use case changes and I need to use the card in a VM then I might try your solution to allow me to use the on board GPU for maintenance. Until then, the easy solution works given I only have unRAID and no VMs using the card.
-
I know this behaviour (or similar) has been raised recently but I cannot find the definitive solution so I am reaching out for some help. I cannot get to the graphical logon prompt on a screen connected directly to the server in unRAID OS GUI Mode, all I get is a black screen following the text boot sequence (which is displayed on screen as you would expect). Once at the black screen I can ctrl-F1 which will take me to the command prompt where I can log in as if I was in normal unRAID OS mode. Everything else operates (including access to the WEB-GUI from a browser on a seperate machine) just fine. I run a Supermicro - X10SL7-F motherboard which has Aspeed AST2400 onboard video. I have the Nvidia Plugin installed so I can leverage the power of my installed Nvidia GeForce GTX 1050 Ti in Docker Containers. I have done some troubleshooting and run the server in unRAID OS GUI Safe Mode where the graphical login prompt comes up just fine. This helped me identify that it was likely a Plugin causing the behaviour. Through a process of elimination I got to this plugin. When installed I can't access the graphical login prompt, when removed - I can. I am running unRAID version 6.9.2 I am running Nvidia Plugin version 2021.05.19 Nvidia driver version installed is 470.42.01 (latest as of time of writing) I do not boot UEFI. My BIOS is set to prioritise the onboard Aspeed video and my screen is plugged into the VGA port on the motherboard. Diagnostics are attached. unraid-diagnostics-20210623-1323.zip
-
I find this interesting. Should LT decide not to implement code to require ALL Arrays to start before allowing Docker and VM services to start, then you essentially bypass the current restriction. Pondering this for 2 mins only, I guess you would have to define some sort of Array Hierarchy. Which come online first, what order, which one is responsible for allowing other services to start (#1?). If it was #1, you would just create a simple small (even RAM disk) Array just to get services running. Like I said ... interesting.
