gathly

Just in case this ends up helping someone else I ran this on the command line in UNRAID and I haven't had a problem with it crashing since. Some linux builds have this power saving option which shuts down USB ports after some amount of time to save power, and this disables that. echo -1 > /sys/module/usbcore/parameters/autosuspend

I know it's literally an official fallacy, but I can't help thinking about the money already spent on all my drives and the months it took to get all my data transferred onto the new system. However, I can definitely start planning now for that better system and work towards it slowly. I haven't looked at the enclosure thread yet, but what do you think of this one? I've had my eye on it. https://www.amazon.com/Thermaltake-Vertical-Mid-Tower-Computer-CA-1X1-00M6WN-00/dp/B0B2KVJNKT/ref=sr_1_1?crid=3F7MEHKMM4C1K&keywords=Thermaltake+Tower+500+Snow+Edition+Vertical+Mid-Tower&qid=1692834534&sprefix=thermaltake+tower+500+snow+edition+vertical+mid-tower+computer+chassis+supports+e-atx+ca-1x1-00m6wn-00%2Caps%2C954&sr=8-1 also, ideally, do you still use a 32GB thumb drive for the OS, or do you do something internally?

Since deciding to go with UNRAID, I've had problems with it crashing. It runs fine, sometimes for days, and then I'll go to log-in to the web interface and I can't connect. The computer is still on, but I can't access it. There's nothing in the syslog to indicate why this is happening. Unfortunately, I started getting into UNRAID without doing enough reading beforehand, so I have it running on a Lenovo Think Station P150 Tiny using a USB hub connecting 6 external drives (4 x 16TB (including parity drive, 1 8TB, 1 4TB, all external) and 1 internal SSD 2TB used as cache. Since I can find no errors in syslog, I assume the issue I'm having is hardware related, and I've since learned that USB can drop connection, and that I should really be using SATA, I'm thinking maybe that's the problem causing the crash. So, first things first, I need to see if I can add an expansion slot to this board. It's a mini-pc, so I don't know what special versions I need to still fit in the case. I see the board has SATA1 and SATA2 printed on it. I've got what could be a PCI or PCIe slot in there. Can someone with more knowledge than me tell me what is best to do. Ideally, money no object, I'd build up a whole new PC that has many SATA ports with space for many drives and I'll plug each drive directly into the board through individual SATA ports using no multipliers or eSATA configurations. But what can I do with this setup and all these external drives? I've thought of pulling the external drives from their cases and getting an enclosure, and using eSATA, but only if I can add it, since I don't have an eSATA port. I assume any USB to eSATA adapter defeats the entire purpose, but I need to connect at least 6 drives. attached are some snapshots of my board and the manual for the think station p350 tiny. p350_tiny_hmm.pdf

Looking at various 10-bay drive enclosures, it doesn't seem like any of them have a SATA out port, so what's the best way to do this?

I've been reading that you shouldn't use USB connected drives for UNRAID, but only direct SATA connections, because USB can drop out, which causes problems with UNRAID. Not knowing this, I already have 8 drives on a USB hub connected to a Lenovo think station. Would it be any better if the drives were placed in a drive enclosure, and all SATA connected there, but the enclosure then connects to the think station via USB 3 cable? Is that exactly the same risk of USB dropping? Would I need to crack open the think station and create a SATA connection and get a drive enclosure that connects to the think station via SATA? I don't know when I'll have the money to set all that up, but when I do, I want to make sure it would actually make a difference.

the i915 driver fix seems to have helped. No crash overnight. Hopefully that was it. Thanks

Thanks. I have followed those instructions. We'll see if it crashes tonight. I also did get another computer to test with, and the network connection problem happened with that one too when trying to copy from windows to an unraid share. It writes for a little while, and then says it can't find the location it was writing too. I'm really not sure what to do if there's some kind of underlying hardware issue. Are there fixes for that, or do I need an entirely new cpu? Could the hardware issue be the flash drive? Because that's easily replaced.

I posted the syslog above, but here's the one from today. Here's the section from last night. at midnight it starts this activity. is that appdata backup? Maybe that's what is crashing it. The sSMTP authorization fail is the last line before my restart this morning, but there's also one from the previous evening that didn't cause any problems. Jul 13 18:20:01 Tower sSMTP[18208]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials v13-20020a63bf0d000000b00553ebb05d28sm5695272pgf.41 - gsmtp) Jul 13 19:28:20 Tower webGUI: Successful login user root from 10.0.0.107 Jul 13 23:59:02 Tower dhcpcd[1421]: br0: 2c:9e:00:03:1c:14(2c:9e:00:03:1c:14) claims 10.0.0.220 Jul 14 00:00:02 Tower emhttpd: Starting services... Jul 14 00:00:02 Tower emhttpd: shcmd (1686): chmod 0777 '/mnt/user/ab_20230714_000001' Jul 14 00:00:02 Tower emhttpd: shcmd (1687): chown 'nobody':'users' '/mnt/user/ab_20230714_000001' Jul 14 00:00:02 Tower emhttpd: shcmd (1688): /etc/rc.d/rc.samba restart Jul 14 00:00:02 Tower wsdd2[6309]: 'Terminated' signal received. Jul 14 00:00:02 Tower winbindd[6312]: [2023/07/14 00:00:02.266285, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jul 14 00:00:02 Tower winbindd[6312]: Got sig[15] terminate (is_parent=1) Jul 14 00:00:02 Tower winbindd[6314]: [2023/07/14 00:00:02.266301, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jul 14 00:00:02 Tower winbindd[6314]: Got sig[15] terminate (is_parent=0) Jul 14 00:00:02 Tower wsdd2[6309]: terminating. Jul 14 00:00:02 Tower winbindd[7098]: [2023/07/14 00:00:02.266553, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jul 14 00:00:02 Tower winbindd[7098]: Got sig[15] terminate (is_parent=0) Jul 14 00:00:04 Tower root: Starting Samba: /usr/sbin/smbd -D Jul 14 00:00:04 Tower smbd[11959]: [2023/07/14 00:00:04.437505, 0] ../../source3/smbd/server.c:1741(main) Jul 14 00:00:04 Tower smbd[11959]: smbd version 4.17.7 started. Jul 14 00:00:04 Tower smbd[11959]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jul 14 00:00:04 Tower root: /usr/sbin/wsdd2 -d -4 Jul 14 00:00:04 Tower wsdd2[11973]: starting. Jul 14 00:00:04 Tower root: /usr/sbin/winbindd -D Jul 14 00:00:04 Tower winbindd[11974]: [2023/07/14 00:00:04.489470, 0] ../../source3/winbindd/winbindd.c:1440(main) Jul 14 00:00:04 Tower winbindd[11974]: winbindd version 4.17.7 started. Jul 14 00:00:04 Tower winbindd[11974]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jul 14 00:00:04 Tower winbindd[11976]: [2023/07/14 00:00:04.492155, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Jul 14 00:00:04 Tower winbindd[11976]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jul 14 00:00:04 Tower emhttpd: shcmd (1692): /etc/rc.d/rc.avahidaemon restart Jul 14 00:00:04 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Jul 14 00:00:04 Tower avahi-daemon[6353]: Got SIGTERM, quitting. Jul 14 00:00:04 Tower avahi-dnsconfd[6364]: read(): EOF Jul 14 00:00:04 Tower avahi-daemon[6353]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.0.0.220. Jul 14 00:00:04 Tower avahi-daemon[6353]: avahi-daemon 0.8 exiting. Jul 14 00:00:04 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jul 14 00:00:04 Tower avahi-daemon[12010]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jul 14 00:00:04 Tower avahi-daemon[12010]: Successfully dropped root privileges. Jul 14 00:00:04 Tower avahi-daemon[12010]: avahi-daemon 0.8 starting up. Jul 14 00:00:04 Tower avahi-daemon[12010]: Successfully called chroot(). Jul 14 00:00:04 Tower avahi-daemon[12010]: Successfully dropped remaining capabilities. Jul 14 00:00:04 Tower avahi-daemon[12010]: Loading service file /services/sftp-ssh.service. Jul 14 00:00:04 Tower avahi-daemon[12010]: Loading service file /services/smb.service. Jul 14 00:00:04 Tower avahi-daemon[12010]: Loading service file /services/ssh.service. Jul 14 00:00:04 Tower avahi-daemon[12010]: Joining mDNS multicast group on interface br0.IPv4 with address 10.0.0.220. Jul 14 00:00:04 Tower avahi-daemon[12010]: New relevant interface br0.IPv4 for mDNS. Jul 14 00:00:04 Tower avahi-daemon[12010]: Network interface enumeration completed. Jul 14 00:00:04 Tower avahi-daemon[12010]: Registering new address record for 10.0.0.220 on br0.IPv4. Jul 14 00:00:04 Tower emhttpd: shcmd (1693): /etc/rc.d/rc.avahidnsconfd restart Jul 14 00:00:04 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Jul 14 00:00:04 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jul 14 00:00:04 Tower avahi-dnsconfd[12019]: Successfully connected to Avahi daemon. Jul 14 00:00:05 Tower avahi-daemon[12010]: Server startup complete. Host name is Tower.local. Local service cookie is 3025273898. Jul 14 00:00:06 Tower avahi-daemon[12010]: Service "Tower" (/services/ssh.service) successfully established. Jul 14 00:00:06 Tower avahi-daemon[12010]: Service "Tower" (/services/smb.service) successfully established. Jul 14 00:00:06 Tower avahi-daemon[12010]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jul 14 00:00:12 Tower kernel: veth5dbe0f6: renamed from eth0 Jul 14 00:00:12 Tower kernel: docker0: port 1(veth64cb230) entered disabled state Jul 14 00:00:12 Tower kernel: docker0: port 1(veth64cb230) entered disabled state Jul 14 00:00:12 Tower kernel: device veth64cb230 left promiscuous mode Jul 14 00:00:12 Tower kernel: docker0: port 1(veth64cb230) entered disabled state Jul 14 00:00:12 Tower kernel: docker0: port 1(veth7ce0b93) entered blocking state Jul 14 00:00:12 Tower kernel: docker0: port 1(veth7ce0b93) entered disabled state Jul 14 00:00:12 Tower kernel: device veth7ce0b93 entered promiscuous mode Jul 14 00:00:12 Tower kernel: docker0: port 1(veth7ce0b93) entered blocking state Jul 14 00:00:12 Tower kernel: docker0: port 1(veth7ce0b93) entered forwarding state Jul 14 00:00:12 Tower kernel: eth0: renamed from vethd0c0dd7 Jul 14 00:00:12 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7ce0b93: link becomes ready Jul 14 00:10:03 Tower sSMTP[29991]: Creating SSL connection to host Jul 14 00:10:03 Tower sSMTP[29991]: SSL connection using TLS_AES_256_GCM_SHA384 Jul 14 00:10:03 Tower sSMTP[29991]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials s11-20020a170902a50b00b001b53be3d956sm7041214plq.167 - gsmtp) Jul 14 00:20:01 Tower sSMTP[15249]: Creating SSL connection to host Jul 14 00:20:01 Tower sSMTP[15249]: SSL connection using TLS_AES_256_GCM_SHA384 Jul 14 00:20:01 Tower sSMTP[15249]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials bg5-20020a1709028e8500b001b6740207d2sm7018867plb.215 - gsmtp) Jul 14 06:14:29 Tower kernel: Linux version 6.1.36-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Wed Jun 28 07:51:54 PDT 2023 Jul 14 06:14:29 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot syslog

I can't seem to get memtest to run. I see it in the options at boot-time, but when I select it nothing happens. The Lenovo think centre I'm using does have its own diagnostics system in the bios, and I ran that, and it found no issues with the cpu or anything else. I don't have another computer around to try and test the Samba crashes happening from there. Thanks for your help. any other ideas? Is there a better way to capture diagnostics? I know it resets at reboot, so how do I capture the issue in logs after it happens?

here are the diagnostics tower-diagnostics-20230713-0629.zip

I have been setting up a new UNRAID. It has taken weeks to get data transferred, because either file transferring with Krusader gets interrupted when UNRAID crashes, or the SMB connection to my windows computer gets disconnected. I've attached my syslog. Hopefully, there are some clues in there. I don't really know what I'm doing. syslog (1)