mikedpitt420

Yes. But I am thinking the issue may be that I shouldn't have plugged a mini SAS cable from the backplane to 4 sata slots on the motherboard. I think I may have burned out the board. I just ordered another motherboard and another lsi 8 drive card so everything is mini sas to mini sas.

I'm sorry. I don't know what that is. Can you elaborate a bit?

Just purchased a Supermicro 836 case, Supermicro X10SRH-CLN4f board, Intel Xeon E5 2630. Supermicro RAM as well. I have just booted it up, and it fails to see almost every disk I have. I have an LSI card (that was flashed, I had thought but now am seeing BIOS again) with 2 mini sas connectors going to 2 of the mini sas connectors on the backplanes in the case. The other two mini sas backplanes I just have hooked up to cables that make them split to 4 SATA connectors each, which are all plugged directly into the motherboard, and 2 SSDs (old and new cache) both also plugged directly into the motherboard, not using the backplane. The system can see the 2 SSDs plugged directly into the motherboard, and 4 of the ones in the backplane and it seems completely random. I have attached my diagnostics. Can anyone help me with this? tower-diagnostics-20190110-0545.zip

Well just to be safe I'm going to stick with Supermicro 836 that I found a good deal on ebay for. Thanks very much

Well the motherboard is Supermicro so I'm sure that works, and the two SATA cards worked with my previous case just fine so I know they are compatible. So it doesn't matter about the backplane then? Alright so I should be good to order this? Sorry if that's a dumb question it's just a large purchase, didn't want to screw it up and have to send it back.

It has a backplane though, that's what I'm asking. I've seen tons of posts of people saying this or that backplane isn't compatible. That was the question

Just been looking for a new case and wondering if this would be compatible or not? https://www.newegg.com/Product/Product.aspx?Item=N82E16811192419&ignorebbr=1&nm_mc=KNC-GoogleAdwords-PC&cm_mmc=KNC-GoogleAdwords-PC-_-pla-_-Server+-+Chassis-_-N82E16811192419&gclid=Cj0KCQiAmafhBRDUARIsACOKERPtZyaS5WcTiZ5d8mumhfjtT98ghCsMDlAWVo0ESvU4WACWKaag_YcaAqTBEALw_wcB&gclsrc=aw.ds Athena Power RM-4U4243HE12 12Gb/s 4U Hot-Swap 24-Bay E-ATX Rackmount Server Chassis w/ 12 Gbps Mini-SAS Backplane Supports 24 x 3.5" or 2.5" SAS / SATA SSD / HDD - Support E-ATX (12" x 13") M/B - Supp - OEM

I hope I have found the issue. One of the pins on one of the backplane was cracked. Just emailed Norco and fingers crossed they'll just send me another backplane. I hope swapping this out isn't too much of a pain. Will report back.

I just bought a 16 bay Norco case, and it seems like the backplane is not supported. Is there one that has 16+ bays that someone can recommend that's reasonably priced and works with unRAID?

Just got a Norco case, and it looks like the backplane is not supported. Can someone recommend a reasonable priced server case that has 16+ spots for drives that definitely works with unRAID?

I just was migrating my server over to a new Norco case, this one specifically, https://www.newegg.com/Product/Product.aspx?Item=9SIA3913UN3405 Norco NORCO RPC-4116. It just has simple SATA connectors in the back of the plane so I thought I would be fine. Unraid doesn't seem to see any drives and I get a ton of "SATA link down" when I'm watching the boot up (it says this for 14 drives, 8 connected to the mobo, one 8 port card flashed and one 4 port card flashed). This is also a new motherboard, an Aorus GA-AX370 UEFI motherboard. Is there some weird SATA setting that I'm missing that would cause unRAID to not see any of my disks?

Changing this to mnt/user/system/libvrt/libvrt.img does nothing. There are no files in either libvrt directory.

I see this problem is common in upgrading to 6.5. Although none of the other threads seem to fix my issue. I have designated /mnt/cache/system/libvrt/libvrt.img as my image file. Although when I hit start it never creates the file and my VMs remain stopped. Anyone who can help? tower.zip

No. I try to use the programs as they're intended to avoid things like this. I don't think these mappings are an issue, I may be wrong. I am a mod on a fairly decent sized indexer. I advise loads of people each day how to setup their automation. KISS rings true all the time. Don't try to go outside the box unless you know what you're doing. Again, this may have squat to do with this issue but you aren't making it easier on yourself going outside normal directory conventions. I would just use the downloads folder as it's intended in its' intended place for what it's worth. See if that works, it's worth a try

In a normal Usenet SAB / Sonarr / Couch(Radarr) scenario your downloaded files end up in /mnt/cache/appdata/sabnzbd/config/Downloads or somewhere underneath /mnt/cache/appdata/sabnzbd/ Again, I'm not saying this is your issue, just seems overly complicated for no reason is all

Why have you pulled the /downloads directory out from underneath where SAB (and everything else for Usenet) wants to be downloaded ? I don't know if that's necessarily the issue but it's better to keep it simple and inside the box if you aren't quite sure what you're doing. There's a reason why SAB has categories and separates things like movies and TV shows

Thanks! --repair did the trick. I wonder why only that docker was creating this issue. Mike

I have 3 files on my cache drive which will not delete. I stopped the array and ran a check on the (3 month old) cache drive and got this: checking extents checking free space cache checking fs roots root 5 inode 795665 errors 200, dir isize wrong root 5 inode 7350789 errors 1, no inode item unresolved ref dir 795665 index 41031 namelen 12 name nzbdrone.pid filetype 1 errors 5, no dir item, no inode ref root 5 inode 7351526 errors 200, dir isize wrong root 5 inode 7767099 errors 1, no inode item unresolved ref dir 7351526 index 11728 namelen 15 name nzbdrone.db-wal filetype 1 errors 5, no dir item, no inode ref root 5 inode 7767100 errors 1, no inode item unresolved ref dir 7351526 index 11729 namelen 15 name nzbdrone.db-shm filetype 1 errors 5, no dir item, no inode ref Checking filesystem on /dev/sdf1 UUID: 26b1367d-fbda-42ef-98e1-34189018efd9 found 233614036992 bytes used err is 1 total csum bytes: 194593428 total tree bytes: 943652864 total fs tree bytes: 593100800 total extent tree bytes: 106102784 btree space waste bytes: 185965020 file data blocks allocated: 1768305549312 referenced 220438290432 What should I do now? Also, I cannot delete these three files mentioned and they show up with a ? in owner, group, and permissions. The disk mounts and everything seems to be fine except for this. tower-diagnostics-20180311-1949.zip

I think you're right. I guess I'll start a thread. Thanks.

Rebooted, still same thing. Those files won't delete. Also, when I try to stop the array from the GUI it hangs on "unmounting disks". I don't know if that helps or not. I was able to use "powerdown" through SSH, then once it reboots I can stop the array normally. But it seems like if I try to touch those files something happens and the GUI can't unmount the array. EDIT: Stopped the array, ran a test on the (3 month old) cache drive and I get this: which references the 3 files I can't delete. checking extents checking free space cache checking fs roots root 5 inode 795665 errors 200, dir isize wrong root 5 inode 7350789 errors 1, no inode item unresolved ref dir 795665 index 41031 namelen 12 name nzbdrone.pid filetype 1 errors 5, no dir item, no inode ref root 5 inode 7351526 errors 200, dir isize wrong root 5 inode 7767099 errors 1, no inode item unresolved ref dir 7351526 index 11728 namelen 15 name nzbdrone.db-wal filetype 1 errors 5, no dir item, no inode ref root 5 inode 7767100 errors 1, no inode item unresolved ref dir 7351526 index 11729 namelen 15 name nzbdrone.db-shm filetype 1 errors 5, no dir item, no inode ref Checking filesystem on /dev/sdf1 UUID: 26b1367d-fbda-42ef-98e1-34189018efd9 found 233614036992 bytes used err is 1 total csum bytes: 194593428 total tree bytes: 943652864 total fs tree bytes: 593100800 total extent tree bytes: 106102784 btree space waste bytes: 185965020 file data blocks allocated: 1768305549312 referenced 220438290432

I recently found this docker unresponsive. I tried to remove it, as well as the image and delete the data to find that two files / directories are what look to be corrupted and will not delete. How do I get rid of these files and re-install this docker? No matter what I do I can't find a way to delete these files. They also show ? for user and attributes.

I have had an issue with my server just randomly powering off with no apparent reason I can think of. User wgstarks suggested using your (awesome) Fix Common Problems "Troubleshooting Mode". Just a few minutes ago, my server again randomly powered off, a parity check was initiated as it was not a clean shutdown. I did have troublshooting mode running when this happened. I did not get a screenshot of the screen when this happened as it seems completely random and I am unable to reproduce it at will. However I can upload my syslog, but where is the file that the troubleshooting mode log resides (or is it the same file?) so I can also upload this? Thanks again in advance very much Squid, your work and attention to these forums and users speaks for itself. tower-diagnostics-20180209-1918.zip

Thanks very much wgstarks. It is very much appreciated.

And CHBMD, this RAM was on Supermicro's page as tested and supported so I believe it will work out fine. I definitely should have done more research on a dual processor builds before attempting this as it was my first time doing so. I've build hundreds of servers and had to match components etc, but this honestly just threw me for a loop. Glad I've learned my lesson even though it was the hard way and hopefully can help someone else down the line before they make the same mistakes I did.

As I was typing my server literally just randomly powered off. Where do I go to see the logs from this test to try and diagnose the issue? At the moment it was only one person on my Plex and one kodi box that is doing transcoding on it's end, so now I'm thinking this isn't the issue.