Flendor

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Flendor's Achievements

Noob

Noob (1/14)

4

Reputation

  1. I have removed all plugins - disabled Docker - disabled VM Update to 6.11.2 works Go to enable Docker and everything stops working
  2. No VMs at all though the service may startup
  3. Updated to 6.11.2 and have the exact same issue as the previous update to 6.11.1 All starts well. The Array shows as starting, then the GUI drops connection I can no longer access the server via the IP address nor myServer. No ping to the IP address I can login via the console (that still shows the correct IP address) but do not know what to do after that Rebooted from console Was able to grab the last screen of the log before the GUI disconnected. Do not know if this helps or not Nov 5 09:39:41 Fizban avahi-daemon[18937]: Successfully called chroot(). Nov 5 09:39:41 Fizban avahi-daemon[18937]: Successfully dropped remaining capabilities. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Loading service file /services/sftp-ssh.service. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Loading service file /services/smb.service. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Loading service file /services/ssh.service. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface br5.IPv4 with address 192.168.61.39. Nov 5 09:39:41 Fizban avahi-daemon[18937]: New relevant interface br5.IPv4 for mDNS. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface br4.IPv4 with address 192.168.16.38. Nov 5 09:39:41 Fizban avahi-daemon[18937]: New relevant interface br4.IPv4 for mDNS. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.16.39. Nov 5 09:39:41 Fizban avahi-daemon[18937]: New relevant interface br0.IPv4 for mDNS. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Nov 5 09:39:41 Fizban avahi-daemon[18937]: New relevant interface lo.IPv6 for mDNS. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Nov 5 09:39:41 Fizban avahi-daemon[18937]: New relevant interface lo.IPv4 for mDNS. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Network interface enumeration completed. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Registering new address record for 192.168.61.39 on br5.IPv4. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Registering new address record for 192.168.16.38 on br4.IPv4. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Registering new address record for 192.168.16.39 on br0.IPv4. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Registering new address record for ::1 on lo.*. Nov 5 09:39:41 Fizban avahi-daemon[18937]: Registering new address record for 127.0.0.1 on lo.IPv4. Nov 5 09:39:41 Fizban emhttpd: shcmd (165): /etc/rc.d/rc.avahidnsconfd restart Nov 5 09:39:41 Fizban root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Nov 5 09:39:41 Fizban root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Nov 5 09:39:41 Fizban avahi-dnsconfd[18948]: Successfully connected to Avahi daemon. Nov 5 09:39:41 Fizban emhttpd: shcmd (176): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 200 Nov 5 09:39:42 Fizban avahi-daemon[18937]: Server startup complete. Host name is Fizban.local. Local service cookie is 648793137. Nov 5 09:39:42 Fizban avahi-daemon[18937]: Service "Fizban" (/services/ssh.service) successfully established. Nov 5 09:39:42 Fizban avahi-daemon[18937]: Service "Fizban" (/services/smb.service) successfully established. Nov 5 09:39:42 Fizban avahi-daemon[18937]: Service "Fizban" (/services/sftp-ssh.service) successfully established. Nov 5 09:40:03 Fizban nmbd[18891]: [2022/11/05 09:40:03.019571, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: Samba name server FIZBAN is now a local master browser for workgroup WORKGROUP on subnet 192.168.16.38 Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban nmbd[18891]: [2022/11/05 09:40:03.019674, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: Samba name server FIZBAN is now a local master browser for workgroup WORKGROUP on subnet 192.168.16.39 Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban nmbd[18891]: [2022/11/05 09:40:03.019735, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: Samba name server FIZBAN is now a local master browser for workgroup WORKGROUP on subnet 192.168.61.39 Nov 5 09:40:03 Fizban nmbd[18891]: Nov 5 09:40:03 Fizban nmbd[18891]: ***** Nov 5 09:40:03 Fizban kernel: loop2: detected capacity change from 0 to 838860800 Nov 5 09:40:03 Fizban kernel: BTRFS: device fsid d33ddfb9-7bd1-4a4e-9065-6f19dbce08f4 devid 1 transid 1780970 /dev/loop2 scanned by mount (21915) Nov 5 09:40:03 Fizban kernel: BTRFS info (device loop2): using free space tree Nov 5 09:40:03 Fizban kernel: BTRFS info (device loop2): has skinny extents Nov 5 09:40:04 Fizban root: Resize device id 1 (/dev/loop2) from 400.00GiB to max Nov 5 09:40:04 Fizban emhttpd: shcmd (179): /etc/rc.d/rc.docker start Nov 5 09:40:04 Fizban root: starting dockerd ... Nov 5 09:40:10 Fizban kernel: Bridge firewalling registered Nov 5 09:40:10 Fizban kernel: Initializing XFRM netlink socket Nov 5 09:40:10 Fizban avahi-daemon[18937]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Nov 5 09:40:10 Fizban avahi-daemon[18937]: New relevant interface docker0.IPv4 for mDNS. Nov 5 09:40:10 Fizban avahi-daemon[18937]: Registering new address record for 172.17.0.1 on docker0.IPv4.
  4. 6.11 to 6.11.1 upgrade seems to go fine. It downloads the NVDIDIA driver. All done and asks for a reboot. IP address is fixed After the reboot the server comes back up again on the correct IP address, mounts drives, shows array starting... and then the GUI dies, and there is no ping on the server IP address The console shows version 6.11.1 and the original server IP address and can be logged into Reverted back to 6.11 and everyting seemed to worked, except the DelugeVPN docker. Tried again to upgrade, same result. How can i use the console to find if the IP address has changed, or to grab logs?
  5. I was able to revert back a version and then extract the DB file from last weeks backup. This works. Annoying to have lost a week, but not a big issue in the grand scheme of things.
  6. how can you pick out just the radarr.db files from a restore?
  7. Same here. I will be annoyed if i have to start over. I dont really want to do an appdata restore and overwrite everything.
  8. Updated to the latest version this morning and have the exact same result with the same log error messages.
  9. Thanks, the front back plane of 24 bays only has one connection for the HBA, the other two connections appear to be for connection to extra back planes
  10. the aim is to have most of the 36 bays populated at some point
  11. Thanks, does it matter how many ports? Tried this to no success.
  12. You mean replace the Adaptec ASR-71605 - is that the HBA?
  13. Please forgive me if this is in the incorrect place. I have searched for something similar and have struggled to find anything that helped. I am migrating from a Fractal Design 7XL to a SuperMicro 846 rack due to needing to expand the volume of drives. (wish I had seen the 3D printed 24 bay option before I started this) Supermicro X9DRi-LN4+/X9DR3-LN4+, Version REV:1.20A American Megatrends Inc., Version 3.4 BIOS dated: Wed 20 Nov 2019 12:00:00 AM GMT Adaptec ASR-71605 controller with one cable going to each of the front and rear planes 24 front bays, 12 rear bays Two Intel® Xeon® CPU E5-2680 0 @ 2.70GHz 96 Gb DDR3 First attempt at moving the drives over, random drives would become disabled and error counts would go through the roof Second attempt, parity rebuild would have the same impact, drives disabled and errors on all drives Third attempt, Preclear would have the same impact, drives disabled and errors on all drives Put everything back in the original build, all drives are fine, parity rebuild is fine, preclear new drives is fine. Built the new server with a bunch of small size drives that I could beg and borrow to try and work on the issue without losing my data. Preclear these drives causes the same issue. It can maybe cope with one 1TB clear before things start to fail. Formatting the first array start causes the same issue. Parity rebuild again has the same issue. I have attached the log that I could download before things got hairy and loud noises came from the machine. Really have very little idea what I am looking at in these logs, other than red means bad... Your help and assistance would be very much appreciated. syslog-2.txt
  14. I seem to have got most things working now.. looks really good and extremely informative, huge THANK YOU for all your hard work. One last issue seems to be the drive varibales at the top of the dashboard that are all empty/none.
  15. Okay, I have reset the root password and things seem to be happening. Wierd as I set changed the password to what it was in the first place. Thanks anyway