MrBrac Posted September 1, 2022 Share Posted September 1, 2022 My server has been down for while and recently I just fixed it up. Now my shares won't connect at all. I get this when I try connect from my real pc but VMS work. Aug 31 22:24:15 BracServUltra rpc.mountd[22220]: refused mount request from 192.168.1.37 for /isos (/): not exported bracservultra-diagnostics-20220831-2235.zip Quote Link to comment
itimpi Posted September 1, 2022 Share Posted September 1, 2022 Just to check the obvious, do you have the ‘isos’ share setting set to be visible on the network. The default is for it to not be visible. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 I think I used to do that yeah , i think my settings are all messed up. Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 Shares isos is not being exported, go to Shares -> isos -> SMB Security setting to change that. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) I woke up just now and my Docker for sonarr cant write to its database and my vm cant start because it cant reach /etc folder? bracservultra-diagnostics-20220901-1004.zip Edited September 1, 2022 by MrBrac Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 You are having issues with multiple disks, disk10 got disabled and disks 6 and 12 are generating a lot of ATA errors, check/replace cables and post new diags after array start. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 https://www.amazon.com/gp/product/B013G4EOEY/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 I have these are these cables crappy? I should finish read check first right? Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 Not much point since a disk is already disabled. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) What about cables you think those brands are low respect? Edit: I have spare 2 cables so I will try it. Edited September 1, 2022 by MrBrac Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 Don't know those cables but disks 6 and 12 are connected to the onboard SATA, so not that kind of cables. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 Well thats great well I swapped sas cables and I am checking now .. hmm Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) Now my IPV4 address is not set great. All of sudden its working now. Sep 1 11:42:07 BracServUltra ntpd[1463]: bind(21) AF_INET6 2603:9000:760a:7cd3:1227:f5ff:fe38:4985#123 flags 0x11 failed: Cannot assign requested address Sep 1 11:42:07 BracServUltra ntpd[1463]: unable to create socket on br0 (8) for 2603:9000:760a:7cd3:1227:f5ff:fe38:4985#123 Sep 1 11:42:07 BracServUltra ntpd[1463]: failed to init interface for address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985 Sep 1 11:42:07 BracServUltra ntpd[1463]: Listen normally on 9 br0 [fe80::1227:f5ff:fe38:4985%7]:123 Sep 1 11:42:07 BracServUltra ntpd[1463]: new interface(s) found: waking up resolver Sep 1 11:42:07 BracServUltra dhcpcd[1374]: br0: REPLY6 received from fe80::7a29:edff:fe28:3ce4 Sep 1 11:42:07 BracServUltra dhcpcd[1374]: br0: adding address 2603:9000:760a:7cd3::7de/128 Sep 1 11:42:07 BracServUltra dhcpcd[1374]: br0: renew in 255127, rebind in 483817, expire in 604777 seconds Sep 1 11:42:07 BracServUltra avahi-daemon[1842]: Registering new address record for 2603:9000:760a:7cd3::7de on br0.*. Sep 1 11:42:10 BracServUltra ntpd[1463]: Listen normally on 10 br0 [2603:9000:760a:7cd3::7de]:123 Sep 1 11:42:10 BracServUltra ntpd[1463]: Listen normally on 11 br0 [2603:9000:760a:7cd3:1227:f5ff:fe38:4985]:123 Sep 1 11:42:10 BracServUltra ntpd[1463]: new interface(s) found: waking up resolver Sep 1 11:42:10 BracServUltra dhcpcd[1330]: br0: leased 192.168.1.97 for 604800 seconds Sep 1 11:42:10 BracServUltra avahi-daemon[1842]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.97. Sep 1 11:42:10 BracServUltra avahi-daemon[1842]: New relevant interface br0.IPv4 for mDNS. Sep 1 11:42:10 BracServUltra dhcpcd[1330]: br0: adding route to 192.168.1.0/24 Sep 1 11:42:10 BracServUltra avahi-daemon[1842]: Registering new address record for 192.168.1.97 on br0.IPv4. Sep 1 11:42:10 BracServUltra dhcpcd[1330]: br0: adding default route via 192.168.1.1 Sep 1 11:42:12 BracServUltra ntpd[1463]: Listen normally on 12 br0 192.168.1.97:123 Sep 1 11:42:12 BracServUltra ntpd[1463]: new interface(s) found: waking up resolver Sep 1 11:42:28 BracServUltra kernel: r8169 0000:0b:00.0 eth0: Link is Down Sep 1 11:42:28 BracServUltra kernel: br0: port 1(eth0) entered disabled state Sep 1 11:42:29 BracServUltra dhcpcd[1330]: br0: carrier lost Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: carrier lost Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Withdrawing address record for 192.168.1.97 on br0. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.97. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Interface br0.IPv4 no longer relevant for mDNS. Sep 1 11:42:29 BracServUltra dhcpcd[1330]: br0: deleting route to 192.168.1.0/24 Sep 1 11:42:29 BracServUltra dhcpcd[1330]: br0: deleting default route via 192.168.1.1 Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: deleting address 2603:9000:760a:7cd3::7de/128 Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Withdrawing address record for 2603:9000:760a:7cd3::7de on br0. Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: deleting address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985/64 Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Withdrawing address record for 2603:9000:760a:7cd3:1227:f5ff:fe38:4985 on br0. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Leaving mDNS multicast group on interface br0.IPv6 with address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::1227:f5ff:fe38:4985. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Registering new address record for fe80::1227:f5ff:fe38:4985 on br0.*. Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: deleting route to 2603:9000:760a:7cd3::/64 Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: deleting default route via fe80::7a29:edff:fe28:3ce4 Sep 1 11:42:29 BracServUltra dhcpcd[1374]: br0: deleting address fe80::1227:f5ff:fe38:4985 Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Withdrawing address record for fe80::1227:f5ff:fe38:4985 on br0. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::1227:f5ff:fe38:4985. Sep 1 11:42:29 BracServUltra avahi-daemon[1842]: Interface br0.IPv6 no longer relevant for mDNS. Sep 1 11:42:31 BracServUltra ntpd[1463]: Deleting interface #9 br0, fe80::1227:f5ff:fe38:4985%7#123, interface stats: received=0, sent=0, dropped=0, active_time=24 secs Sep 1 11:42:31 BracServUltra ntpd[1463]: Deleting interface #10 br0, 2603:9000:760a:7cd3::7de#123, interface stats: received=0, sent=0, dropped=0, active_time=21 secs Sep 1 11:42:31 BracServUltra ntpd[1463]: Deleting interface #11 br0, 2603:9000:760a:7cd3:1227:f5ff:fe38:4985#123, interface stats: received=0, sent=0, dropped=0, active_time=21 secs Sep 1 11:42:31 BracServUltra ntpd[1463]: Deleting interface #12 br0, 192.168.1.97#123, interface stats: received=5, sent=5, dropped=0, active_time=19 secs Sep 1 11:42:31 BracServUltra ntpd[1463]: 91.209.94.10 local addr 192.168.1.97 -> <null> Sep 1 11:42:45 BracServUltra kernel: Generic FE-GE Realtek PHY r8169-0-b00:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling! Sep 1 11:42:45 BracServUltra kernel: r8169 0000:0b:00.0 eth0: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx Sep 1 11:42:45 BracServUltra kernel: br0: port 1(eth0) entered blocking state Sep 1 11:42:45 BracServUltra kernel: br0: port 1(eth0) entered forwarding state Sep 1 11:42:45 BracServUltra dhcpcd[1374]: br0: carrier acquired Sep 1 11:42:45 BracServUltra dhcpcd[1330]: br0: carrier acquired Sep 1 11:42:45 BracServUltra dhcpcd[1374]: br0: IAID f5:38:49:85 Sep 1 11:42:45 BracServUltra dhcpcd[1374]: br0: adding address fe80::1227:f5ff:fe38:4985 Sep 1 11:42:45 BracServUltra avahi-daemon[1842]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::1227:f5ff:fe38:4985. Sep 1 11:42:45 BracServUltra avahi-daemon[1842]: New relevant interface br0.IPv6 for mDNS. Sep 1 11:42:45 BracServUltra avahi-daemon[1842]: Registering new address record for fe80::1227:f5ff:fe38:4985 on br0.*. Sep 1 11:42:45 BracServUltra dhcpcd[1374]: br0: soliciting an IPv6 router Sep 1 11:42:45 BracServUltra dhcpcd[1330]: br0: rebinding lease of 192.168.1.97 Sep 1 11:42:45 BracServUltra dhcpcd[1330]: br0: probing address 192.168.1.97/24 Sep 1 11:42:47 BracServUltra dhcpcd[1374]: br0: Router Advertisement from fe80::7a29:edff:fe28:3ce4 Sep 1 11:42:47 BracServUltra dhcpcd[1374]: br0: adding address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985/64 Sep 1 11:42:47 BracServUltra avahi-daemon[1842]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::1227:f5ff:fe38:4985. Sep 1 11:42:47 BracServUltra avahi-daemon[1842]: Joining mDNS multicast group on interface br0.IPv6 with address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985. Sep 1 11:42:47 BracServUltra avahi-daemon[1842]: Registering new address record for 2603:9000:760a:7cd3:1227:f5ff:fe38:4985 on br0.*. Sep 1 11:42:47 BracServUltra avahi-daemon[1842]: Withdrawing address record for fe80::1227:f5ff:fe38:4985 on br0. Sep 1 11:42:47 BracServUltra dhcpcd[1374]: br0: adding route to 2603:9000:760a:7cd3::/64 Sep 1 11:42:47 BracServUltra dhcpcd[1374]: br0: confirming prior DHCPv6 lease Sep 1 11:42:47 BracServUltra dhcpcd[1374]: br0: adding default route via fe80::7a29:edff:fe28:3ce4 Sep 1 11:42:48 BracServUltra ntpd[1463]: bind(21) AF_INET6 2603:9000:760a:7cd3:1227:f5ff:fe38:4985#123 flags 0x11 failed: Cannot assign requested address Sep 1 11:42:48 BracServUltra ntpd[1463]: unable to create socket on br0 (13) for 2603:9000:760a:7cd3:1227:f5ff:fe38:4985#123 Sep 1 11:42:48 BracServUltra ntpd[1463]: failed to init interface for address 2603:9000:760a:7cd3:1227:f5ff:fe38:4985 Sep 1 11:42:48 BracServUltra ntpd[1463]: Listen normally on 14 br0 [fe80::1227:f5ff:fe38:4985%7]:123 Sep 1 11:42:48 BracServUltra ntpd[1463]: new interface(s) found: waking up resolver Sep 1 11:42:48 BracServUltra dhcpcd[1374]: br0: REPLY6 received from fe80::7a29:edff:fe28:3ce4 Sep 1 11:42:48 BracServUltra dhcpcd[1374]: br0: adding address 2603:9000:760a:7cd3::7de/128 Sep 1 11:42:48 BracServUltra avahi-daemon[1842]: Registering new address record for 2603:9000:760a:7cd3::7de on br0.*. Sep 1 11:42:48 BracServUltra dhcpcd[1374]: br0: renew in 255086, rebind in 483776, expire in 604736 seconds Sep 1 11:42:50 BracServUltra dhcpcd[1330]: br0: leased 192.168.1.97 for 604800 seconds Sep 1 11:42:50 BracServUltra dhcpcd[1330]: br0: adding route to 192.168.1.0/24 Sep 1 11:42:50 BracServUltra avahi-daemon[1842]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.97. Sep 1 11:42:50 BracServUltra avahi-daemon[1842]: New relevant interface br0.IPv4 for mDNS. Sep 1 11:42:50 BracServUltra dhcpcd[1330]: br0: adding default route via 192.168.1.1 Sep 1 11:42:50 BracServUltra avahi-daemon[1842]: Registering new address record for 192.168.1.97 on br0.IPv4. Sep 1 11:42:51 BracServUltra webGUI: Successful login user root from 192.168.1.37 Sep 1 11:42:52 BracServUltra ntpd[1463]: Listen normally on 15 br0 192.168.1.97:123 Sep 1 11:42:52 BracServUltra ntpd[1463]: Listen normally on 16 br0 [2603:9000:760a:7cd3::7de]:123 Sep 1 11:42:52 BracServUltra ntpd[1463]: Listen normally on 17 br0 [2603:9000:760a:7cd3:1227:f5ff:fe38:4985]:123 Sep 1 11:42:52 BracServUltra ntpd[1463]: new interface(s) found: waking up resolver Edited September 1, 2022 by MrBrac Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 bracservultra-diagnostics-20220901-1156.zip Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 I see you formatted disk10, no data there? Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) Disk 10 is crap disk. I took it off, ATM I can live with losing disk 10. I already lost Disk 10 was really 4. I just want get my VM and shares working for now. I am so damn tired. I downgraded to latest stable as well. /dev/loop3 has errors. Edited September 1, 2022 by MrBrac Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 libvirt.img is corrupt, if you have a backup restore it. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 Just now, JorgeB said: libvirt.img is corrupt, if you have a backup restore it. MY windows VM is running off a real M2. I need copy all my xml data right? Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 XML files for all VMs are stored in libvirt.img, you should always have a backup of that file. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) Fixed VM now. Just share issue and replace disk 10 Edited September 1, 2022 by MrBrac Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 That's also stored in the libvirt.img. Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 1 minute ago, JorgeB said: That's also stored in the libvirt.img. This is only drive I can rip out and replace it with does it look good too you? Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 Looks OK, but that won't fix the current libvirt.img issue, only if you restore a backup, or need to re-create the VM(s), can still point to the same vdisk(s). Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 (edited) 26 minutes ago, JorgeB said: Looks OK, but that won't fix the current libvirt.img issue, only if you restore a backup, or need to re-create the VM(s), can still point to the same vdisk(s). I fixed the VM already its all grand! Ok so new DISK gonna be cleared for 10 replacement . Still shares should work but doesnt right? Edited September 1, 2022 by MrBrac 1 Quote Link to comment
MrBrac Posted September 1, 2022 Author Share Posted September 1, 2022 Sep 1 13:31:37 BracServUltra kernel: ata5: hard resetting link Sep 1 13:31:45 BracServUltra kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Sep 1 13:31:45 BracServUltra kernel: ata5.00: configured for UDMA/33 Sep 1 13:31:45 BracServUltra kernel: ata5: EH complete Sep 1 13:31:45 BracServUltra kernel: ata5.00: exception Emask 0x10 SAct 0x80f01fff SErr 0x90200 action 0xe frozen Sep 1 13:31:45 BracServUltra kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed Sep 1 13:31:45 BracServUltra kernel: ata5: SError: { Persist PHYRdyChg 10B8B } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/60:00:10:57:bb/02:00:02:00:00/40 tag 0 ncq dma 311296 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/00:08:70:59:bb/04:00:02:00:00/40 tag 1 ncq dma 524288 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/58:10:70:5d:bb/01:00:02:00:00/40 tag 2 ncq dma 176128 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/30:18:c8:5e:bb/01:00:02:00:00/40 tag 3 ncq dma 155648 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/f0:20:f8:5f:bb/00:00:02:00:00/40 tag 4 ncq dma 122880 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/40:28:e8:60:bb/01:00:02:00:00/40 tag 5 ncq dma 163840 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/40:30:28:62:bb/03:00:02:00:00/40 tag 6 ncq dma 425984 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Sep 1 13:31:45 BracServUltra kernel: ata5.00: failed command: READ FPDMA QUEUED Sep 1 13:31:45 BracServUltra kernel: ata5.00: cmd 60/c0:38:68:65:bb/00:00:02:00:00/40 tag 7 ncq dma 98304 in Sep 1 13:31:45 BracServUltra kernel: res 40/00:60:d8:73:bb/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 1 13:31:45 BracServUltra kernel: ata5.00: status: { DRDY } Disk 12 keeps giving issues , is it cable or dud? Quote Link to comment
JorgeB Posted September 1, 2022 Share Posted September 1, 2022 Looks more like a power/SATA cable issue but if the issue persists after replacing them it could be the device. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.