geeksheikh

UPDATE -- The above only works until you restart -- to make this permanent add a windows credential start --> credentials manager --> add windows credential

So after digging through the Windows service event logs I found out that Windows Explorer was continuing to try to login as an "unauthorized guest user". After a little more digging I found out how to provide a username password (the unraid share creds) open cmd and type the following net use \\server\share <<password>> /USER:<<USERNAME>> Now open up windows explorer and viola. This problem does only present itself after the update referenced above I did a few fresh installs and went through all the updates and after that update it always broke. Hopefully this can help someone else.

Thanks @Frank1940 -- I will go through the PDF -- note that I have two other Windows machines one the network and I've checked -- that update was installed on those PCs as well and those are working fine. This is very strange because this VM is Win 10 and it fails with the update installed and works when I uninstall it. Very strange. I will keep investigating and report my findings. Thanks for your response.

After Windows installs kb4023057 -- the //SERVER and all shares are no longer accessible. I uninstalled the update and restarted and it worked again. Just wanted to bring this to developer attention. It seems like Windows only let's me pause updates for 35 days so I know I'm good for 35 days but avoiding this update is not a long-term solution. Is this a known issue? Is there a fix? If you need additional logs / details from windows machine after the update -- I can reproduce the issue be reinstalling the update and give you what you need, I'm pretty technical so I should be able to provide additional details if you need them. Thank you.

I'm trying to update OS using the gui and it gets stuck inflating files. Been stuck here for over 30m now. Any ideas? Upgrading from 6.9.2 to 6.11.5 UPDATE -- Seems to have worked when hitting local ip instead of dns.

I bought a reverse breakout cable, I figured I'd give it a try and see if it works. I'll report back. Enclosure has no expander. Planning to just connect sata to mobo and sas to 4-drive rail in the Norco case.

@apandey been doing some reading and I’m wondering if some sata sas reverse breakout cables would work. mobo sata (x4) to mini sas on the back plane. Anyone else got this to work? Cable Matters Internal Mini SAS to SATA Reverse Breakout Cable (SFF-8087 to SATA) 1.6 Feet https://a.co/d/inC8lZf

This is exactly what I was looking for! Thank you!

That’s a decent idea but my case has a back plane with sas connectors that allow the drivers to be hot swappable. Not sure if I could rig it to accept sata and maintain hot swap. I have a NORCO RPC-4220 4U

Can you say more about this? Does this mean a 12gb/s card with 2 ports has only 6 gb/s per port? Does port == lane? If so, would plugging both ports into the expander grant the full bandwidth the expander (i.e. 2 ports to HBA and 4 to drives) I'm thinking about local, data-intensive tasks -- perfect example is parity check / rebuild. If each disk can real-world seq write that's (120MB/s * 20) 2.4GB/s. If my math is write with a single 12gb/s card I shouldn't expect total array throughput to be any greater than 1.5GB/s, is this theory correct?

Hi, I couldn't find this topic addressed here. 3 PCIe 4.0 slots on MOBO 1 Intel RAID Expander Card (RES2SV240) 1 GPU 20 7200 RPM 6gb/s disks I have a lot of options of how to wire things up given my LSI SAS cards and I'm not sure the best way. I can EITHER use 2 LSI 9211-8i (6gb/s) and the expander card (molex powered) or 1 LSI 9300-8i (12gb/s) and the expander card (pci powered). A couple of questions / thoughts. I think the molex powering the expander card may not provide enough max watts to support max power draw causing drives to power bump -- hence I'm wondering if just using the pcie power directly to power the expander may be more stable. Question - LSI bandwidth per port -- can the LSI 9300-8i (12gb/s) offer all 12gb/s through a single sas port or is it just 6 gb/s per port? This is important as it raises the question, should I feed the expander card with 2 inputs from the HBA or is one the same? Does adding 2 inputs help the bandwidth through the adapter at all or should I just dedicate 1 port to expander and 1 port to a sas rail of drives (4)? Question - Any thoughts as to if there's any difference between having 2 6gb/s HBAs vs 1 12 gb/s HBA? I'm trying to figure out the most efficient way to plug in the cables to maximize throughput. I'm not a SAS expert and I know networks have bandwidth limitations per port as do switches...just curious as to where the bottlenecks would be in this setup with HBAs and the expander. The reason I need the expander is because I have 20 drives and only 2 free PCIe slots (don't want to pay for a 24 port HBA). Furthermore, the power concern in #1 above is why I'm thinking it may be more stable to have just a single HBA and plug the expander directly into PCIe rather than rely on the molex connector for power. Looking for help, thanks in advance.

This is the last question I have for now -- If I can confirm my model numbers / firmware version (without ripping into the case) that would be fantastic. Any ideas on how to do that? I was able to use sas2IRCU to list the two devices

I have a double parity

I understand you now. I meant if one of my disks were to fail during the parity rebuild the contents of the failed disk would be lost. Based on what you said, it sounds like that's accurate.

Is there a way to determine the exact model number of my sas controllers? I have an idea but don't want to be guessing. I see these two lines for cm0 and cm1 -- so it appears I have 2 sas controllers but not sure how to ensure I select the right firmware based on LSISAS2008 and LSISAS2116 mpt2sas_cm0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.24.01.00) mpt2sas_cm1: LSISAS2116: FWVersion(17.00.01.00), ChipRevision(0x02), BiosVersion(07.24.01.00)

Thank you again @trurl and @JorgeB Yes, I know but the disk was offline and I wanted to ensure it wasn't power issues when I ran the extended self-test, this was the main reason I tested it outside of the array. Gotcha -- are you aware of firmware updates that can resolve power bumps? Trying to guestimate if firmware is likely to solve the issue or if I should assume power path / backplane is . I know you can't answer the root cause other than power but curious as to if firmware updates have resolved similar issues in the past? Wouldn't this invalidate existing parity and in resulting in a risk of data loss during the parity rebuild?

One more question, do you recommend upgrading to the latest firmware version (the post you linked looks like it's upgrading to 16.00.10.00). I'm still on unraid 6.9.2 -- have been waiting until these issues were confirmed resolved before upgrading. Should I (do I need to) upgrade unraid first to ensure it's compatible with the latest LSI firmware version?

thank you for reviewing for me. Strange how it's been working for years and all of a sudden starts having power issues...but I guess it happens. Since it just bumped offline is there anyway to tell unraid that this disk contents are fine and to add it back without having to rebuild it? I will look into updating the LSI firmware. Are there firmware improvements that you're aware of that can resolve intermittent power issues?

Hi @JorgeB -- Ok, so I've got another disk with issues. I haven't been able to verify if it's in the same slot (or backplane) as the others that were having issues but hopefully you can look at the diagnostics (attached) and make some guess as to what could be causing these read errors. Thank you. unraid-diagnostics-20230110-1037.zip

yes I did reboot. I had 2 months of uptime but had to reboot for ... reasons. Will post If i get another, thanks

Whoops sorry, forgot to upload those. Just generated them now, hopefully the diags you need are still there. unraid-diagnostics-20230109-1222.zip

Hello, I have two drives that are claiming to get read errors (twice in the last month). I pulled the drives and ran an extended self test AND a full sector test (surface test) with hard disk check software (hard disk sentinel). All checks passed without any issue. I removed drive from the disk, restarted array (to clear it out), removed disk from historical devices, put the disk back into the array to have the contents full rebuilt on the drive. About 3 weeks, worked without issue and then boom, read error again. I even switched the drive bay in the physical server expecting that if it was a hardware issue the disk# would change that had the error. But, same disk had read errors again (even in the other slot). My question is, what could keep causing read errors on same disk in different drive slots (different back planes, sas cables, power) when all tests keep passing on the disk outside of the array? Uploaded SMART report and other test results for reference. Thanks in advance for your input.

Happened to me today too. Restarted array / unraid. Docker came up and so did a few VMs but some failed. Tried to start manually, failed --> error, VNC no available port Looked in syslog --> Failed to add multicast for WSDD: Address already in use Disabled VM service Disabled Docker re-enable VM service -- worked re-enabled docker -- worked

Hi, I'm having net stability issues with some of my docker containers, and after reviewing logs; this is what I found. arp (unraid ip) moved from br0 mac to shim-br0 mac arp (unraid ip) moved from shim-br0 mac to br0 mac This happens about every 10-20 minutes. Can someone please help me figure out what's going on here / how to fix it? Much appreciated. pumbaa-diagnostics-20220219-1014.zip

Just closing this out. I have confirmed that the enclosure is unable to capture the device ID. The ORICO enclosures are not compatible with UD, they send through a single deviceID to UD I replaced the enclosure with a Sabrent USB 3.2 4-Bay 3.5 and it works great. It's keeping the drives down at 85F degrees whereas the other enclosure wasn't compatible with UD and the drive temperature were around 110F consistently. So I'd highly recommend this little Sabrent enclosure if you need one for UD.