Jump to content

RogueWolf33

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

0 Neutral

About RogueWolf33

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I can see this thread is quite old and I am wondering if there may be some updated information regarding how SSD's are handled in an array. Currently I attempt to run this command to determine the style of TRIM my devices are using and the data is limited. I can only assume this has to do with the built in HP controller I am using. I have attempted to switch the SMART controller type from "Automatic" to the HP Specific type of controller listed but this does not help. I fear that I am unable to determine this information due to the RAID controller blocking the query. Is there a vendor or an SSD controller type list that might be able to be referenced before purchasing SSD's for an array? This is currently the only information I get back from the hdparm command: /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 Any information is appreciated. Thanks so much!
  2. This mentions parity, I agree. However, if the Parity drive is still Mechanical and the array drives are SSD, I only see a write hit if I am not mistaken. I am currently attempting to confirm that my drives support DZAT to be sure I will not run into issues in the future. I appreciate you putting me on this track so I can ensure I do not run into any issues.
  3. Well shoot. Now I am not certain which solution worked! I tried @Frank1940 's method and it didnt seem to work. But then I tried @Squid 's and that didnt work either. So I completely closed out of Chrome and terminal started working again! I should have tried closing out of chrome after setting site permissions as Frank suggested. Either way, Thank you to you both!
  4. That was a great idea! I checked that but that did not seem to resolve my issue. I am now trying squid's suggestion. Thanks so much Frank!
  5. @Squid Hey brother, Me again. I am actually having the same issue in chrome (I know, imagine that) I have found several ways of accessing the flash drive, but I cannot discover the super secret batman way of deleting the files out of said directories. Does the flash drive have to be mounted in terminal to do so? Am I missing something obvious? (I am sure I am) I just never tried to modify the OS files on the flash drive before. They seem "read only" in both the unraid webgui and Windows File explorer.
  6. Currently i've had no trouble that I can pinpoint to an actual configuration problem, But to clarify, nope, I have all SSD as the Array. A single 4 TB HDD Parity for now. The object is to update to full SSD eventually. The HDD/SSD mix was in the Array but I have recently upgraded all drives to SSD. Not a hundred percent clear on what the issue would be with that. (Besides performance limitations due to the parity drive but I plan on upgrading that as well) Where would the sync errors come from in an SSD prominent system? Is there a lack of TRIM in Unraid? I am not clear on what is being conveyed.
  7. @johnnie.black hmm. it almost sounds like from a rebuild standpoint, for redundancy and efficiently, dual parity would be a little more robust in data restoration. Unraid doesn't only reference parity drives though right? I can clearly see the read operations happening in tandem with all drives. Or am I misinterpreting this information?
  8. I'll admit. I kind of don't know what to do with this information.... lol I am kind of committed.
  9. I have not realized that. I thought I might have picked up that they are not supported as parity drives. I was thinking I might have been lucky that I just kept my parity drive a mechanical. It seems that having a cache option where everyone is bound to use them might spur a development in that area. Not to mention they are HUGELY prominent in the general PC building community as price continues to drop. Either way, so far my Unraid (without my own intervention gumming up the works) has been operating great. But thank you for making me aware!
  10. Well, If it were me, I would look at the settings in the web ui of the transcoder to start. There are some optimization settings there. You mention you are trying to do 5k, that's pretty intensive. I'd start my search here:
  11. @Antdonn I was actually able to find a HP Proliant DL380 G7 with 2 x Intel Xeon X5660 2.8 GHZ and 32 Gigs of RAM on ebay for a great price. it was something like 150 bucks if I remember correctly. By the time the item arrived, it was apparent that the reason it was so cheap is that it had been dropped. I do not think it was in shipment either. I ended up getting refund of half of that making my current investment around 70 bucks. To sweeten the deal I asked for drive caddies to save further money. No matter, it booted and the components worked. This thing had a nice 8 bays I could use. (Due to chassis warping I only could effectively use 7 of them though) I Started with a 32 Gig small Samsung USB and a hodgepodge of sata drives simply using the built in raid controller. I was forced to configure raid 0's on the controller before the OS would see them. I eventually purchased a 4 TB HDD for parity. (My logic here was that anything large enough to house parity for the future was going to be WAY too expensive in SSD's) Finally, one by one I started switching over all HDD's to SSD's. First 500's, and now I have 6 x 1 TB in SSD. The only mechanical I have is my Parity still. The Server comes with 4 network ports in it so I bonded these and purchased a switch. I was not too picky in SSD's the reason for this was the slowest SSD's are still going to out perform a lot of mechanical drives on the market if not all of them. I look for longevity in them. Crucial's MX Series seem to have a great life span and they offer up a nice robust warranty to go with them for a decent price (A bit more than the sandisk line but I believe the warranty is longer if I am not mistaken) In a perfect world I would have gone all Crucial MX series 1 TB and then move up. However, I pieced this thing together, I think I have 2 x WD Blues, 2 x Inlands, and 2 x Sandisks. All 1 TB. I haven't seen any issues outside of when I would try to upgrade or move around drives. this was just recently with Debris from dust building up getting into the sata ports giving me a world of hurt. (And other issues that were my own making which we will just chalk up to life lessons) I would say in hind sight, some research to do on a system you plan to install SSD's in. 1. Backplane - Be sure the backplane is not older in the server you purchase or you can upgrade it to a standard that will handle the speeds your SSD's put out. 2. Raid controller - A lot of people seem to be using LSI controllers I believe. They are flashed to "I.T. Mode" this allows a fluent passthrough to the Unraid OS without having to mess around with configuring the virtual disks in a controller BIOS before being able to see the disks in Unraid. 3. Consider how many disks you want to use and purchase a chassis that will compliment all of them. Even if you only start with 2 or 3, you want room to grow. I am currently considering PCIe expansion for my system as a possible parity solution and then utilizing my 7th slot on top of that but that is on the horizon. I think that is it! If you have any additional questions hit me up!
  12. Good Lort you guys! Talk about emasculating a guy! I currently only have 6 TB. I am happy to report it is all SSD (With the exception of Parity) As cost drops, I will be upgrading systematically. This is my first unraid server but seeing all of your builds has certainly sparked some ambitions in me!
  13. Final Update: I powered down the server systematically removing my SSD's. No HDD's left in my system. (With the exception of my parity drive) I have completely battled the jungle of dust bunnies. They have been exterminated. May they rest in peace. I carefully reseated all SATA drives back in their original homes. Prior to doing this, Disk 3 while attempting to view "Disk Log Information" on the "Main" tab, displayed cycling errors. Now, All drives file systems and Disk Log Info display green. Data is available again and I can start to rebuild. Thank you so much @Squid for always keeping the light on and lending a helping hand to us up and coming. I am sure I will be talking to you again in like 6 months or so when I inadvertently jack something else up! Until then, Happy Raiding! -RW33
  14. Update: Started in maintenance mode and checked all disk. Only disk 5 found with corruption. Repaired disk 5 with instructions using the -v switch. (or operator, I am not sure of the correct terminology) Ran a check after the repair using -n Everything is clean. Once I started the array again in normal mode, My shares seem to have data again. Probably not all of it due to disk 1 being formatted but it's a huge jump for linux newbie nerds across the world. Post repair diagnostics attached. tower-diagnostics-20190922-0256.zip