• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Pro-289's Achievements


Rookie (2/14)



  1. Have you tried testing the RAM yet? That would be a good start. At the initial boot menu, select the RAM test instead of the default loading of unraid os. I know bad memory can create all kinds of random problems in an os. A windows pc can crash many different ways with unstable RAM.
  2. I believe I've recently had an EMI issue myself. I had a bad power supply that was arcing voltage inside, probably due to a bad capacitor. You can hear the voltage noise from 20 feet away. I think it was getting inside everything on my system. Tried changing out cables, reseating everything and moving cables around. Misc drives being flagged with CRC errors, and even one drive being disabled. Just to be extra safe after I replaced the power supply and all cables, I went a little unconventional and also put snap-on ferrite beads around all SATA cables and the main trucks of my power cable splitters. Thirty dollars of what the heck why not, and so far so good with no CRC errors on 10 hard drives and one SSD cache drive. Would have probably been fine with just a new power supply. It would have been interesting to keep the bad power supply while adding ferrite beads.
  3. I just did an update from 6.9.2 to 6.10.3. I use a custom banner. The first thing I noticed after the upgrade was the solid color overlay on the top-right that used to be translucent and was covering a good portion of my banner. I found the option to put it back to almost how it was before by selecting "Show banner background color fade:" option to No. But I'm still left with a huge circle and down arrow. When I click it it states "Enhance your experience with My Servers". I click it and then select "No thanks", but it still stays on the screen. How do I get rid of that advertisement on my banner bar?
  4. So downloaded something and used TV Rename to rename the episodes in a standard way. I just happened to be browsing the drives through the web interface to make sure it's going to my new drive. But it appears they used a non-standard character. Not sure how to display the character here, or if it'll paste correctly. But it is this dash character – I copied it from my windows explorer filename and pasted here. When any file has this character the whole Name field of the filename is blank, just wipes the string from the display. You should be able to recreate it as I just copied what I pasted above and inserted that into another file and it disappeared from the "Index of" view of my share or drive. I just did another test, and found a lot of other non-standard characters are wiping the filename. Like ALT+255. Rename a file with the character by pressing ALT and then 255 on the num pad. It's a legal character to name the file, but apparently unraid don't like it.
  5. Yup, worked like a champ. Got my 4TB as parity now without risking issues during the 15 hour rebuild. Maybe when I get another 4TB, I'll set that as Parity 1 then remove Parity 2 for optimum performance. Thanks for the help.
  6. So what happens afterwards when I remove Parity 1? Will I get warnings about the drive missing, which of course I should? How do I then make the array happy to keep using Parity 2 without Parity 1? I've heard of "new config" before, but not sure how that works.
  7. I have a 3TB parity drive and some 3TB and 2TB data drives. I bought a 4TB drive that I now want to upgrade the 3TB parity. I just had some ultra dma crc issues with a few drives after moving around cables. One went disabled during a write I presume. I had a faulty/arcing power supply which I replaced. Changed out all my cables. Put some ferrite beads over my sata cables for the hell of it. I rebuilt that disabled drive and everything on it seems okay without error. I know I could disable the 3TB parity, assign the new 4TB as parity and rebuild it. But during that 12hr rebuild time frame if I have an issue with a data drive then I'm not protected from getting my array out of wack. Seems the easiest way if possible would be to install a new parity drive and have it copy from old to new in offline mode. Pull the old drive and start the array with out any rebuild, then run a parity check for good measure. When you do Dual Parity drives, are both drives exactly the same as each other? So could I add my 4TB as Parity 2 and have it rebuild onto that. Then remove my 1st 3TB parity and drop back down to a 1 parity drive array without rebuilding again?
  8. I ran a preclear script years back on some 2TB and 3TB drives I've added. Glad I did. Found one that had issues during the write/read/verify. Afterwards I ran a SMART test in my windows machine and verified the drop in health. I RMA'd that sucker just a few days after receiving it. The replacement passed and I've been error free since, but have never had an error on any drive. I have nine drives now since I started with a couple a decade ago. I plan on getting a 4TB and replace my 3TB parity drive to accommodate more 4TB drives. Currently I have a mix of 2TBs and 3TBs. Sometime later I'll get another 4TB to swap with my aging 2TBs. But I've always loved that preclear process to verify my purchase.
  9. Fast forward 6 years. Any progress? Lots of nerdy crap in here. But no way to hook into the low level file system to know what's going on? Of course at first the cache needs to know what's there and read everything. Then afterward hook into the filesystem to always know what happens afterwards. I've been struggling with the add-on for years of never working right for me. Having low-level kernel support would be such a benefit. I'm surprised throughout all the years of Linux that it doesn't have some sort of file caching option already. I'm bumping this thread for future development.
  10. Interesting thing is when I go to the web interface, I can navigate to the Shares and browse the root and maybe one more sub folder in. But once I get to actual files, just the hard drive that stores those files will spin up. That seems normal though.
  11. I just tried to access the drive letter from the command prompt. Six of the eight drives powered up right after. The directory paused a few times while the drives powered up. A few hours earlier I even had all drives powered up viewing all the folders so the names were all in the cache. And I have fresh install of Cache Directories, where the main items I changed from default are cache pressure to 4 and enabled Scan User Shares. Plus I've also updated to Win 10 and disabled SMB 1.0 to force SMB 2.0+. My last attempt will be to disable Samba altogether and only use NFS.
  12. I'll have to try that next. I uninstalled a few plugins and disabled ProFTP and SSD Trim. Of course I also uninstalled Cache Dirs to see what happens. The only plugins I have enabled now are Dynamix System Buttons and Community Applications. I just opened the mapped driver letter while watching the Array Devices in the web browser. Each drive powered up in numerical order, from 1 to 8. Windows timed out since each drive had to power up one by one. Maybe that's a normal process without Cache Directories, I don't know. I'll have to put CD back and try the process again.
  13. I do have a mapped drive letter to the share. Although when I access the share directly using \\IPADDRESS\ it still does the same thing. I checked my mapped drive properties and the indexing option was enabled. I disabled it and it's now going through every file and setting each attribute to disabled. But even after disabling Indexing, the option is still enabled when I go back to properties again. And of course the most annoying part is that every drive has to spin-up ONE BY ONE! If all 8 could spin-up at the same time would be a bit less aggravating, but still annoying that they even spin-up in the first place. I am excluding appdata, system plus a few others I didn't want. I only included the two shares I cared about. There's only two main shares that I have. One has 5,800 files, and the other has 3,200 files. It seems like 8GB of RAM should be able to hold at least 9,000 indexes. But I've noticed every time I transfer files to the array my Cached RAM usage increases as viewed with the System Stats plugin. So I'd assume every time I transfer data to the drives it kicks out the directory cache from RAM. But that would be an issue only while I'm using the Cache Directories plugin. But it seems I have this problem while using the Cache plugin or not, and while transferring data to the drives or not. I think I've even tried to disable viewing thumbnails too. But my folder views are always in Detail mode that doesn't show a thumbnail anyway.
  14. I've been battling this for a long time now. I've tried with Dynamix Cache Directories and with it disabled. I have 8 drives and 1 parity, and an SSD cache drive. When I open my share it pauses for a bit while usually 6 or 7 of the 8 drives spin up. Then the share shows. I don't have any drives grouped for spin up. I've even tried accessing the share with a rarely used laptop, and it did the same thing. Tried Windows 7 and 10. It seems it's something in the config of the server since both computers did it. Plugins I have installed: Community Applications, Dynamix Cache Directories, Dynamix SSD TRIM, Dynamix System Buttons, Dynamix System Information, Dynamix System Statistics, ProFTPd. Not sure if any of the plugins are causing it, or if that's even possible. Sometimes I hate just accessing my library for a 3 second look at something because almost all the drives will spin up. Has anyone run into this before and found a solution?
  15. I just installed this in v6.7.2. The file access seems to work after I press Refresh the file I had played showed up. But, I have 5 out 8 disks that spin up every time I open the Share folder in Windows 7. I even tried with thumbnails disabled. And I have Dynamix Cache Dirs installed. After the 5 disks spined up I noticed my total reads went up by 12. Why the heck are my drives spinning and reading just opening the share?