mgladwin

Members
  • Posts

    88
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

mgladwin's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Just closed the connection. And now Disk 9 has disabled after I restarted which I know is due to bad cables so I will leave this for the time being until I can get the breakout cables replaced. I haven't touched sleep at all. What do you mean when you say 'from the monitor'? And by 'from the VM', I assume you mean in the Windows 10 VM sleep settings?
  2. Tight VNC seems fine so far. I've gone in and out of the VM a few times etc to test and no errors in the syslog yet. I'll keep using it for now I and see how it goes. EDIT: LOL, literally as I wrote the above, libvert has locked up and I wasn't even connected to the VNC. So same issues with VNC as RDP.
  3. Sure. Will give it a shot tomorrow and let you know.
  4. It actually seems fine as long as I don't RDP into the VM at all.
  5. I'll be frank, I don't know much about this at all but I am also getting the freezing when trying to run Blue Iris in a Windows 10 VM. Runs fine for a time, and then libvert crashes and I have to restart unRAID to get it back. This in turn causes an unclean shutdown as I assume libvert wont exit in time before it forces the shutdown. I have tried both i915-GVTg_V5_4 and i915-GVTg_V5_8 which give the same result. This is the only VM I use so wouldn't have thought it was overloaded but Blue Iris is set up to use QuickSync so maybe that's contributing. Running an Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor I assume there isn't much I can do apart from upgrade the CPU etc?
  6. It is/was the cables causing the issue. I have it working for now and was able to get both drives mounted and rebuilt from parity. New cables are on the way. Thanks for your help.
  7. Its as if unRAID can see Disk 9 but cant read/write to it. Must be something to do with the LSI SAS card maybe as both disks are on this same card. However other disks are also on this card and working fine.
  8. Hi all, I went to simply add an SSD into my server for Blue Iris just now and upon the GUI coming back up, I could see the SSD in Unassigned Devices but I also had two array disks unmountable and one of them had been disabled. I shutdown, unplugged the new SSD and started up again but both disks are still unmountable and one of them is still disabled (says its being emulated). I have tried xfs_repair in maintenance mode on Disk 9 which is the one not disabled and the check seemingly doesn't find any issues. I tried first with -n and then without -n. Still same results. Disk 5 is emulated so I figure I can just re-build it once I sort out Disk 9 but I don't really know how to sort out Disk 9. Diagnostics attached but they are after a restart or two. Cheers for any help as not sure what to do now. EDIT: Syslog seems to note that it cant read superblock on /dev/md9. Also added a screenshot of Main tab if it helps. Sep 12 22:52:48 Tower kernel: md: disk9 read error, sector=7814037056 Sep 12 22:52:48 Tower kernel: XFS (md9): last sector read failed Sep 12 22:52:48 Tower root: mount: /mnt/disk9: can't read superblock on /dev/md9. Sep 12 22:52:48 Tower emhttpd: shcmd (814): exit status: 32 Sep 12 22:52:48 Tower emhttpd: /mnt/disk9 mount error: not mounted Sep 12 22:52:48 Tower emhttpd: shcmd (815): umount /mnt/disk9 Sep 12 22:52:48 Tower root: umount: /mnt/disk9: not mounted. tower-diagnostics-20210912-2312.zip
  9. Thank you. I have removed the plugin as I dont 'really' need it so hopefully all good going forward.
  10. My server has been running fine on 6.9.1 for weeks now and only today i decided to upgrade to 6.9.2. The download and upgrade went fine but after the required reboot, the server complained of an unclean shutdown. I had used the normal reboot button on the GUI to invoke the reboot so nothing out of the ordinary and i had no terminals open at time of reboot. Attached is diagnostics from the flash before and after the reboot. I cant see anything jumping out at me but i also don't know what i am looking for. Server is currently doing a parity check now. I have adjusted the shutdown timeout to 65 seconds and applied it to see if it helps but wont know until parity check is finished so i can reboot again and test. Any comments as to why this may have happened appreciated. Cheers tower-diagnostics-20210513-1049.zip tower-diagnostics-20210513-0914.zip
  11. Do you know the best way to fix this? I believe the power supply and single rail is big enough but how do you go about getting the connectors you need? Its something I have wanted to "fix" for a while but its never really been an issue until now so Ive just left it.
  12. Hey all, I'm getting these errors and no matter what I try, I cant seem to get on top of them. This disk was originally on a Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) controller (getting same errors) so I moved it to the onboard SATA controller and seemingly still getting the errors. I have replaced the sata cable a few times with no luck. Its a brand new disk so technically should be good.. However I may have to many HDD's in this system for the current power supply and I do have molex connectors piggy backed a few times to get the right amount of power connectors I need but these errors happen when all other disks are spun down. So i figure it could be a power issue but not so much a lack of power, but maybe quality of power coming through the piggy back cables etc?? I have done a fair bit of reading on this and typically its power or sata cable issue. I'm leaning towards power as its a new disk and getting same errors on different controllers but thought i would ask here before i make my next move. The power supply is a 500W model and I think has a single 32A 12v rail from memory. I have only ever seen these errors on this same disk. All the other disks connected to either the onboard controller or the LSI controller have never had an issue that i am aware of. Dec 19 01:43:13 Tower kernel: ata6.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen Dec 19 01:43:13 Tower kernel: ata6.00: irq_stat 0x00400040, connection status changed Dec 19 01:43:13 Tower kernel: ata6: SError: { HostInt PHYRdyChg 10B8B DevExch } Dec 19 01:43:13 Tower kernel: ata6.00: failed command: READ DMA EXT Dec 19 01:43:13 Tower kernel: ata6.00: cmd 25/00:00:58:23:03/00:01:f9:00:00/e0 tag 13 dma 131072 in Dec 19 01:43:13 Tower kernel: res 50/00:00:57:22:03/00:00:f9:00:00/e0 Emask 0x50 (ATA bus error) Dec 19 01:43:13 Tower kernel: ata6.00: status: { DRDY } Dec 19 01:43:13 Tower kernel: ata6: hard resetting link Dec 19 01:43:19 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 19 01:43:19 Tower kernel: ata6.00: configured for UDMA/133 Dec 19 01:43:19 Tower kernel: ata6: EH complete Dec 19 02:17:55 Tower kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x4890c00 action 0xe frozen Dec 19 02:17:55 Tower kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed Dec 19 02:17:55 Tower kernel: ata6: SError: { Proto HostInt PHYRdyChg 10B8B LinkSeq DevExch } Dec 19 02:17:55 Tower kernel: ata6.00: failed command: READ DMA EXT Dec 19 02:17:55 Tower kernel: ata6.00: cmd 25/00:00:b8:62:9a/00:02:6a:01:00/e0 tag 12 dma 262144 in Dec 19 02:17:55 Tower kernel: res 50/00:00:47:0a:dd/00:00:7b:00:00/e0 Emask 0x52 (ATA bus error) Dec 19 02:17:55 Tower kernel: ata6.00: status: { DRDY } Dec 19 02:17:55 Tower kernel: ata6: hard resetting link Dec 19 02:18:01 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 19 02:18:01 Tower kernel: ata6.00: configured for UDMA/133 Dec 19 02:18:01 Tower kernel: ata6: EH complete Dec 19 02:21:03 Tower kernel: ata6.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen Dec 19 02:21:03 Tower kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed Dec 19 02:21:03 Tower kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Dec 19 02:21:03 Tower kernel: ata6.00: failed command: READ DMA EXT Dec 19 02:21:03 Tower kernel: ata6.00: cmd 25/00:00:b8:5d:10/00:02:6b:01:00/e0 tag 24 dma 262144 in Dec 19 02:21:03 Tower kernel: res 50/00:00:cf:ba:00/00:00:e9:00:00/e0 Emask 0x50 (ATA bus error) Dec 19 02:21:03 Tower kernel: ata6.00: status: { DRDY } Dec 19 02:21:03 Tower kernel: ata6: hard resetting link Dec 19 02:21:08 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 19 02:21:08 Tower kernel: ata6.00: configured for UDMA/133 Dec 19 02:21:08 Tower kernel: ata6: EH complete Diagnostics attached. Look forward to hearing what others thoughts might be. Cheers. tower-diagnostics-20201221-1019.zip
  13. Thanks Squid. Didn't even know this was a thing. Running the balance command now and will report back if i have any further issues. Thanks for the tip about btrfs as well. @SquidSo ran balance command using:- btrfs balance start -dusage=75 /mnt/cache and got output of:- Done, had to relocate 86 out of 115 chunks Checked using:- btrfs fi df -h /mnt/cache/ and got:- Data, single: total=45.00GiB, used=44.83GiB System, single: total=4.00MiB, used=16.00KiB Metadata, single: total=1.01GiB, used=521.22MiB GlobalReserve, single: total=70.16MiB, used=0.00B But ia m still having same issue after an NZBGet container restart. UPDATE: For some reason it is now working! Thanks all.
  14. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='NZBGet' --net='bridge' -e TZ="Australia/Adelaide" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '6789:6789/tcp' -v '/mnt/cache/appdata/nzbget/':'/config':'rw' -v '/mnt/user/MEDIA/DOWNLOADS/':'/downloads':'rw' -v '/mnt/cache/appdata/nzbget/ppscripts':'/scripts':'rw' -v '/mnt/user/MEDIA/DOWNLOADS/completed/music/':'/music-downloads':'rw' 'linuxserver/nzbget' tower-diagnostics-20190324-0749.zip
  15. Hey all, just started getting this error in NZBGet, nothing has changed as far as config is concerned and a container restart wont fix it. Ive checked permissions while ssh'ed into the container and all seems OK. Not sure what to look at next?? EDIT: So last week I had a disk fill up and NZBGet couldn't write to the disk due to no space left. I have now given all disks some more space but maybe NZBGet hasn't seen this or something? I used Unbalance plugin to move some files from the full disk to one that had some space left on it.