reefcrazed

Tagging along, I have this exact same issue that recently started. I have a separate thread that I started today.

So this is a new issue that just popped up for me. My version of Unraid is 6.9.2, an array of 8 14tb drives with one as parity. Randomly when I write to unraid it takes forever, like creating a folder or copying a file. Sometimes write are immediate. None of the drives are set to power off, they always have full green balls next to the device. When this happens the website is fully responsive, nothing new in the logs. If I drop to a bash prompt and run htop the CPU's do not appear to go high usage, but in the web interface a core or two will go 100% which is very off. I have seen these pauses last 10 seconds and up to several minutes. Copying to individual disk shares shows the exact same long pauses. The only thing that may be odd with my setup is I run my system at very high drive usage, probably 98% full or so. Would the array being full cause this?

I have the same setup as the OP, same MLB and SAS controller. Mine does the exact same thing with unraid.

What are you running? Has anyone tried ESXi to see if it does register the correct temps now with this update?

The chances are that it is fixed are like probably zero. I am finally ditching my board, 192gb of ECC, dual Xeons and going low power. The monitoring not working does not bother me that bad, but the amount of power used all day does.

I would love to get excited about that, but so far nothing has fixed this. I am pinning it down to the hardware. Post back in a week please?I would love to get excited about that, but so far nothing has fixed this. I am pinning it down to the hardware. Post back in a week please? I would love to be able to keep this board even longer, although it is getting old. I upgraded my processors to the fastest the board will take and I bumped up the ram to 192 gig recently, so it would be nice to finally get this ridiculous problem fixed.

And retardly the problem still exists.

I can just change the mappings I guess.

Also, I tried just doing a net view \\servername and shows nothing. I mean the share is definitely there, if I use the IP address I can get to it. A simple ping or NS Lookup shows the DNS resolution is perfect.

I think they all are either a mix of 2016 server or Windows 10.

I have updated from the first version of Unraid, I really never needed to so I just let it ride all these years. So I updated last week, a billion great changes it seems. I have a domain but I do not want the the Unraid attached. I have the share set for workgroup and public. If I try to go to \\servername\shared I get an error. If I go to the \\192.168.0.30\shared I can get right to it. I am 100% positive my DNS is right. What would cause this?

I have an old install, version 1.0.0 I think those drives are formatted in reiserfs. I tried to mount those drives in Debian last night and could not. I also tried some windows programs and nothing would mount them. I remember in the past being able to mount those drives in windows, but I cannot seem to be able to now. Is there any reason anyone can think of that this would not be possible?

I will in a few days. I need to reboot it after some data is done copying, that will take a while.

Brand new vanilla install, I could never see my shares. I decided to putty into the server and run samba, and boom I can see my shares now. On every reboot samba does not start. On other flavors of linux I am familiar with how to start a server on boot. On Unraid how can I start samba on boot?

So basically you guys are seeing a bug that is an insane 5 years old now. The board has not changed price in all that time either, I paid $319.99 plus tax for it back in 2013.