Woodpusherghd
-
Posts
236 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Woodpusherghd
-
-
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.
-
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.
-
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.
-
Post your diagnostics, go to tools, diagnostics.
-
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.
-
1
-
1
-
-
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.)
-
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.
-
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
-
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.
-
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-
1
-
-
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 -
It was a permissions issue. Somehow permissions were changed to root.
-
I'm having a problem copying/moving files from my Windows 10 VM to sub directories in certain unRaid shares I've created. More specifically, I can copy files to a user share but not to sub directories created below the share. I get "permission denied." I can copy/move to the parent directory which is the share. Any thoughts?
-
5 hours ago, lsaranto said:
Do you experience the Radeon reset bug?
i don't think so. VM has been pretty stable. I have been able to Kill the VM and restart it without having to reboot UNraid.
-
I'm passing thru an AMD HD 5450 to Windows 10 using seaBIOS.
-
Any recommendations for a Nvida card (mid to low price range) to be passed thru to a Windows 10 VM? I would like to connect to a monitor and speakers via HDMI.
-
I'm on 6.7.2 and my monthly parity check speed has been cut in half from approximately 90MB/s to 50MB/s. Prior to 6.7.2 speed has been consistently around. 90MB/s. I've made no hardware changes. I've attached my diagnostic file.
-
I'm looking at the above motherboard. Any issues with UnRaid I should be aware of? The reason I'm looking at this board is the number of pcie slots and it's compatible with my current AMD processor. Also I assume it's HVM and IOMMU compatible. My current board is an ASUS M5A97 and my CPU is an AMD FX8350.
-
That was my first thought as the drive was inserted into an IStar cage, so I tried the drive in a dock to see if it was recognized as an unassigned device, same result. Once formatted in Windows it was recognized as an unassigned device in the dock. Weird.
-
I attempted to replace a 1TB data drive with a 2TB WD Blue drive. Following the wiki, I stopped the array, unassigned the 1TB drive, powered down, replaced the drive with the 2TB, powered up the unRaid box, stopped the array but the 2 TB drive wasn't recognized. I removed the drive and it was recognized in my Windows PC. Tried again, same result. I once again tried the drive in my Windows PC but this time I formatted it. Now it was recognized in unRaid. Is this normal? BTW, I'm running unRaid 6.70 rc7.
-
Turns out the culprit was my fstab file. Apparently some update to systemd caused a problem which was solved by adding the following code to my unRaid shares in fstab:
noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=0,Hope this helps others who my encounter this problem.
-
I've been running a Ubuntu server 18.04 VM on Unraid 6.70 RC7. I've been backing up the VM weekly but have recently run into a problem with my latest backup. I was trying to change the cpu pining of my VM (with the my VM shut down) when I restarted, everything was borked. I tried booting my latest backup and it stopped after "Dependency failded for local file system." I successfully booted a previous backup but noticed my network interface changed (after running ip link) from enp9s0 to enp11s0. I edited network .conf and all was well. I also noted my couchpotato DB was corrupt (in root) and I deleted it as well. After updating the server using apt-get dist-upgrade i shut down and when I tried to reboot I received the same error. I've attached a screen shot of the boot screen.
I booted several times with this backup but when I correct network.conf I have the same issue when I try to reboot.
I am currently running the VM using the second to last backup but if I shut down, I'm sure I'll run into the same problem.
Any suggestions on trouble shooting steps? Thanks.
-
In addition to pinning the cores to my Windows VM, I isolated the cores, rebooted, so far, so good. Hopefully I excised the demons!
-
I should have seen that coming...😂
Disk disabled Smart Report
in General Support
Posted
Diagnostics attached. Thanks.
tower-diagnostics-20210313-0702.zip