Woodpusherghd

Members
  • Posts

    214
  • Joined

  • Last visited

Everything posted by Woodpusherghd

  1. That makes sense. I tried another estata caddy that doesn't have a port multiplier and the disk mounts.
  2. [Solved] Since upgrading to 6.9 I've been unable to mount drives which I have been previously able to mount on 6.8. Diagnostics are attached. I have an external caddy (StarTech) and I've tried both estata and usb connections, no luck. BTW, the drives mount via usb (hot plug) in my Windows 10 VM. Diagnostics attached. tower-diagnostics-20210417-1442.zip
  3. Thanks. I'll check the cabling, I guess vibrations could have loosened something as I haven't been tinkering around with the server.
  4. Diagnostics attached. Thanks. tower-diagnostics-20210313-0702.zip
  5. One of my WD Red HDs was disabled due to write errors. Could this be due to cabling, power connection issues? The drive is less than 2 years old. In any event, a new drive is on its way. I've attached a smart report. Thanks. WDC_WD20EFRX-68EUZN0_WD-WCC4M7KKJXRN-20210312-2251.txt
  6. As the title states, I'm having difficulty setting up mail on my Ubuntu VM. I have a small home network and in addition to my unRaid box, I have a standalone PC running Ubuntu in which I have successfully set up Postfix and I able to send mail. When I attempt to send mail from my Ubuntu VM, it results in the error "dns=5.0.0, stat=Service unavailable." I have basically copied my Postfix config from my working Ubuntu installation, but apparently I'm missing something unique to the VM installation. In the vm I have set my host name as the fqdn. Any thoughts? As an afterthought, I have apps running on the vm which have built-in mail capability which are successfully sending email notifications so I suspect it's a Postfix or Sendmail mis-configuration. I would like to get this working as I have BackupPC running on the vm and it can only send email notifications through postfix or another mta.
  7. I often mount a drive in a Star Tech external caddy via esata as an unassigned disk. When it drops off line (without being unmounted, usually happens a few hours after mounting) the following error message is flooding the system log: Sep 18 10:31:01 Tower kernel: BTRFS error (device dm-0): bdev /dev/mapper/Unassigned_Disk_VM errs: wr 0, rd 8019, flush 0, corrupt 0, gen 0 I have enabled esata in the motherboard bios for this sata connection. Any suggestions? Diagnostics attached. tower-diagnostics-20200918-1033.zip
  8. Going forward you can enable the syslog server in settings. It will write the syslog to your flash drive. I don't think you can recover the log once the system has rebooted if the syslog server wasn't enabled.
  9. Since the multi-language update to the Local Master plugin, the Yoda icon no longer appears on the dashboard banner even though SMB settings indicate my unRaid tower is the local master. Not appearing is the icon to the dark side leads. (As per Yoda.)
  10. Same issue with RC8 and RC9. I reverted back to 6.7.2 and no issue. I guess I should try to pass through the USB controller to the VM.
  11. I have the same issue with RC6. In my case my logitech unifying receiver is not passed through to my Windows 10 VM, I have to use the usb hot plugin to assign it to the VM. No problem with RC5. I also have experienced lock ups when attaching my Iphone via usb in RC6. Again no problem with RC5.
  12. Upgraded to RC6 and experienced spontaneous shut downs. I also experienced lock ups when attempting to attach my IPhone via usb. No problems with RC5 which I have down graded to. I've attached my syslog which I have been mirroring to my flash drive as well as my diagnostics file from RC5. I'll upgrade again to obtain a diagnostic file from RC6 if that would be helpful Let me know. I suspect the culprit may be the latest qemu which is implemented in RC6. Another suspect is the auto fan plugin which I disabled when I noticed my cpu temps were spiking which may have caused the shut downs but doesn't explain the lock ups when attaching my phone. tower-diagnostics-20191120-1239.zip syslog.txt
  13. I would check your usb flash drive for corruption. If you have a windows pc, run a file check on the flash drive and let it correct any errors.
  14. I didn't have this problem with RC5 which reverted qemu but I have it once again with RC6 with the latest stable qemu. I posted in the usb hot plug thread and the plugin author said it wan't a problem with his plugin. A minor annoyance.
  15. I have had 2 unclean shutdowns in the past 24 hours. To trouble shoot, I have enabled "mirror syslog to flash" in my syslog server. Are there any additional steps I should take to track down the suspects causing the shut downs? Thanks
  16. Reverting qemu fixed the problem I had with my Windows 10 VM when I had to manually detach my Logitech unifying receiver and then re-attach it to my VM in order to use my mouse/keyboard in the VM.
  17. Trying out 6.8.0-RC3. When I start my Windows 10 VM, I must detach my Logitech unifying receiver from the VM using the plugin ( I have a HDMI switch and I can switch back and forth from my VM and my unRaid GUI) and then reattach it for my wireless mouse and keyboard to be usable in the VM. I didn't have this issue with 6.7.2.
  18. I made some progress. After booting into my Windows 10 VM I switched back to the unRaid GUI and using the libvirt hotplug usb plugin, I detached the unifying receiver from the VM and then reattached it. Now I can use my wireless mouse and keyboard in ther VM. I'm starting to believe that the plugin is not fully compatible with RC3. I've attached diagnostics. tower-diagnostics-20191023-1127.zip
  19. Same issue with RC3. Tried normal boot (Not GUI) same problem. I can use my VM with a wired mouse and keyboard so the issue lies with the Logitech unifying receiver. Diagnostics attached. tower-diagnostics-20191019-1140.zip
  20. Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM. I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver. Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard. When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM. When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu. BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch. In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted. It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't. Anyone else experience this problem?
  21. I had a similar problem. Here is a line from my fstab file. I'm running a ubuntu server 18.04 vm: Backup /mnt/Backup 9p noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=0,trans=virtio,version=9p2000.L,_netdev,rw 0 0
  22. When I unmount and remove a disk that is an unassigned device I get the below errors. The disk is formatted as NTFS in Windows 10. When I remount the disk, the errors disappear. I mount the disk via a USB dock. Any thoughts? BTW, the errors in the log constantly repeat and I dont seem to have a device sdo. I've attached a diagnostic file . Oct 7 07:45:58 Tower ntfs-3g[3913]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Oct 7 07:45:58 Tower ntfs-3g[3913]: Failed to read index block: Input/output error Oct 7 07:45:58 Tower kernel: Buffer I/O error on dev sdo1, logical block 36, async page read tower-diagnostics-20191007-1153.zip