Jump to content

sourCream

Members
  • Content Count

    57
  • Joined

  • Last visited

Community Reputation

1 Neutral

About sourCream

  • Rank
    Advanced Member

Recent Profile Visitors

236 profile views
  1. Just updated to the new Plex Beta 1.16.3.1402 and I'm no longer getting the errors.
  2. Same here. Version 1.16.2.1297. Happens only when I scan the music library.
  3. My previous banner really clashed with the 6.6 update so i decided to make some new banners and lost track of time.
  4. Im using: 8 x 8TB Segate's Crucial MX500 500GB SSD (VM's and Dockers) and a LSI 9211-8i My SSD is plugged into the motherboard 6Gb. My dockers are functioning fine. I was using the VM just fine before parity check began. Any idea why the VM is crawling? I force stopped and my parity speeds came back however upon restart of the VM it was still crawling and it tanked my speeds again. Things i have tried: Rebooting I deleted the vdisk and restored from a recent backup (while putting the vdisk back on the cache drive it transferred at 200MBps and parity speeds stayed the same) that didnt work. I used to run dual cache for over a year not one issue. I recently swapped for a single 500gb ssd and i also added another 8tb this month. past that everything was fine up until now. Im really not sure why im seeing the parity check speeds drop when trying to run the VM(and yes everything is on the cache drive nothing is on the array for the VM) Thanks for the help. atlantis-diagnostics-20180630-2046.zip More things i have tried: I undid any changes i could think of this past month, I restarted the server and kept my dockers off. I started parity check and then turned on the VM. Windows was doing the troubleshoot on boot and i noticed my parity speeds were fine. As soon as i tell windows to start normally my parity speeds drop and my VM comes to a crawl. One last thing. I notice on the smart status of the cache drive Attribute 202 says 1. From what i can tell it is data address mark errors with is the number of errors encountered when a read head searches for a requested sector. I did try an even older VM backup and that had no effect also tried creating a whole new VM and that didnt work either. Even set the VM disk to a different drive still nothing. Im just going to have to keep the VM while parity checks happen for now. Im not sure what is causing the VM to lock up. I scrapped the VM i was using and delete libvert and turned off vm manager. Reinstalled the VM and still no luck.
  5. I just got two more notifications last night about pending sectors
  6. Its been almost two days and I haven't received a false notification yet, I think we are good.
  7. I just updated mine. Last time mine gave the error every 12 hours or so although it only happened twice. Ill report in a day or two. I had mine for a week no issues so not sure what caused it to randomly start giving those errors.
  8. I swear you have an answer for everything, glad to see its nothing with the drive. Just did some quick googling and seems they released a firmware update on the 19th. Thanks for the Info. http://www.crucial.com/usa/en/support-ssd?cm_re=us-support-_-main-_-firmware-update-link Firmware M3CR022 has been tested and qualified for immediate release in the Crucial factory, including 2.5-inch and M.2 models of the MX500 SSD. The update from M3CR010 to M3CR022 is an optional update for SSDs in the field, but is recommended if the MX500 is experiencing any of the following issues: Improved ready time from DEVSLP low-power state. Improved TRIM and Wear Leveling performance. Improved SATA error handing. Improved compatibility with some TCG Opal 2.0 third-party encryption utilities (this change does not affect MS BitLocker).
  9. http://www.crucial.com/usa/en/support-ssd?cm_re=us-support-_-main-_-firmware-update-link Firmware M3CR022 has been tested and qualified for immediate release in the Crucial factory, including 2.5-inch and M.2 models of the MX500 SSD. The update from M3CR010 to M3CR022 is an optional update for SSDs in the field, but is recommended if the MX500 is experiencing any of the following issues: Improved ready time from DEVSLP low-power state. Improved TRIM and Wear Leveling performance. Improved SATA error handing. Improved compatibility with some TCG Opal 2.0 third-party encryption utilities (this change does not affect MS BitLocker).
  10. I was running dual 256GB cache drives for over 2 years and not a hickup from them and recently bought a Crucial MX500 500GB to gain a sata port back and now i seem to be running into this issue Today out of nowhere I received a pushbullet notification that my cache drive had pending sectors. I ran a short smart test and it passed and then while running an extended smart test i recieved a notification that everything returned to normal. Both smart test passed. Here is a screen shot of the cache drive attributes https://imgur.com/a/koc6utm the only thing that seems off is Attribute 173 before all this happened it was at 0 after the extended smart test it changed to 6. Currently it is at 7. From what i found on this website http://www.cropel.com/library/smart-attribute-list.aspx, 173 is Wear Leveller Erase Count. This drive is about a week old. Still not sure why i got notified of a pending sector and then it said everything was normal again. Can someone shine some light on what i may be dealing with? Thanks for the help
  11. If i remove the 8i card from the x16 slot and leave the 4i card in the x4 slot bios does NOT see the card and if i boot to ubuntu it doesnt see it either but if i drop the 4i card into the x16 slot it reads just fine. SO its not the card is not unraid nor the bios(i dont think) leaving the only thing i can think of either firmware issue or its something my motherboard doesnt like.
  12. And i know the 5 bay external is fine because i unraid sees the drive when i bypass the second lsi card and plug straight into the board with sata cable worst case i return the lsi card and plug the four remaining sata ports from my motherboard into the bay and ill just have one bay that wont work
  13. Revently i posted this on reddit. I installed everything today and its not detecting the second lsi card.. so in my pci e 16x slot i have a 9211-8i running version 19 in the pci e 4x slot i have a 9211-4i running version 20 (it came that way) Now when i boot up the server and go into the LSI card config i only see the 9211-8i Here is what i have done I verified the lsi card works by pulling the one 8i and putting in place of the 4i I double checked the jumpers on the board(see reddit post for board model) I put a pci e 1x wifi card into the pci e x4 slot and booted linux if found the adapter just fine. leaving the only thing i can think of is the firmware versions need to match. Got any ideas? edit: the 9211-4i is running version 20.00.07.00 on bios 7.39.02.00 the 9211-8i is running version 19.00.00.00 on bios 7.37.00.00 Could this be the cause of the 9211-4i not showing up?
  14. That makes sense, thanks for taking the time to explain it.