Jump to content

dmc72

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by dmc72

  1. I found I had a backup copy of 6b15 on one of my other flash drives that updated from the GUI(Nice feature Lime-tech!). I tested it out and it worked no USB resets on ESXI 5.5 or 6.0. From the change logs the kernel 4.0.x started in 6RC3 -which is giving me the resets. I cant find a copy of 6RC1 or 2 in the announcement threads, not sure if they were released to public or just in-house. If someone does have a copy of 6RC2 I would like to test it even though i'm 99% sure its something in the 4.0. kerenl that is wrong. I hope someone that knows the kernel config can come up with a change that will fix the 4.0.x trouble we're seeing. Is there an EASY way to overide the 6RCx usb driver with the one from the beta15? Thanks.
  2. I went to "vmkernel.log file: https://"IPAddressOfESXiHost"/host" and it does show the resets also for 6rc6, but not with 6b12. Thanks for the info that its happening on you X10 MB's, at least i know its not tied to just the X9SCM. That should make a larger pool of people that may see this trbl and narrow down the cause. uldise - thanks for verifying 6b15 on the X9SCM. Have you tried any of the 6RC series on either board yet? I also found an old(2009) thread http://lime-technology.com/forum/index.php?topic=4877.msg45327#msg45327 which recommended: echo 64 >/sys/block/sdX/device/max_sectors but that did nothing for me. I do think its just a simple setting like that causing it, but I just don't know enough about it. -Dave
  3. I am looking for some help on a trouble I am getting since going from 6-beta-12 to 6rc4. I've also tried rc5+rc6 with same results. from syslog: Jun 12 18:53:44 Tower kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Jun 12 18:53:44 Tower kernel: sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) this keeps repeating every 30-60seconds and doesnt stop. I was running ESXI 5.5, and have also tried on ESXI 6.0 with same results. I want to point the finger at UnRaid RC's(new 4.0.x kernel) but if I boot Unraid to bare metal(Supermicro X9SCM-IIF) I dont see the resets. I have seen this mentioned in a couple of threads but did not see any definite fix. 1 person changed their flash drives and it went away. I have 3 sandisk cruzer blades with pro keys and all three do it. just for a test i also tried a Sandisk fit with trial key and same results. I am getting this before the array is even started. I can go back and get a syslog for 6b12 if that helps. Is there a place to download all the different versions to test b14-15+rc1-3? To narrow this down, can anyone with an X9SCM MB + ESXI let me know if they see this trouble or not. If not what type of setup do you have? Thanks -Dave EDIT: A workaround for this trouble is to use a USB card reader instead of a USB Flash drive. syslog-6-12-15_ESXI-flash_reset_error.txt
  4. Just wanted to close this out now that my speeds are back to the 100MBs range. I'm happy its working but don't understand what was causing the trouble. My disk #5 was only running at 5.3MB/s no matter if it was on the AOC-SASLP-MV8 or the AOC-SAS2LP-MV8. There was also no change if I swapped ports with another drive that was at full speed. I ended up changing out both MV8 cards for a M1015 + RES2SV240 expander and is working great now. I wish I had done this from the start. I have a Norco 4224 and want to give a reminder to anyone that gets a Norco case to double check all the backplane screws. While I had my case open, I was cleaning out the dust and cobwebs and found about half of the backplane screws were loose. I don't know if I missed tightening them when originally built or if they loosened over time. So if you open your case for anything, take a few seconds to check the screws. -Dave
  5. Thanks, I have been thinking of switching 1 of the cards to a M1015 to see if it fixes some random slowdowns that I have seen. What i am seeing now is different. there is no change at all in the speed, it stays right at 5.3MB for 2 days now. Its so frustrating to watch! I added an updated screenshot. It just shows how much of a difference there is between drives. -Dave
  6. Unraid 6b15 in an ESXI VM, 4Gb,1 CPU, 2 Supermicro controllers passed thru to Unraid, Norco 4224. I've been getting beat up by some hardware troubles for the last few weeks. All started with a power failure while UPS was not tied in. Hard drives randomly showing as missing, flash drive not bootable, parity errors during rebuild from hard drive dropping out. Anyway, I seem to have the hardware troubles cleared, but still getting an odd behavior. I am rebuilding parity (after doing a 'New Config') onto a new 4tb drive(all data drives are 3tb). Speeds are running about 5 MB/s where i usually see about 100MB/s. Disk 5 is a 7200rpm HGST NAS and is showing only about 5% of the reads as all the other drives, but is showing no errors on smart reports. The parity rebuild says it will take about 8 days, which is terrible. If parity rebuilds successfully I plan on swapping the drive to another slot. If that doesn't fix it, I will try a new drive. I am curious if anyone has seen this big difference in reads and what can cause it. If it is the drive, do I need to prove errors to RMA it. Is there anything I can do to get its speed back? Any suggestions on other stuff to check are welcome. Thanks! -Dave syslog-5-20-15_slow_parity_sync_-5MB-sec.zip disk_5_SMART.txt
  7. WD 4x 3TB Network Internal Hard Drive Retail Kit (Red Drives) :WDBMMA0030HNC-NRSN Price: $389.96 Was: $519.96 http://www.frys.com/product/8351387
  8. Just curious if anyone knows why the realtek kernel drivers would need to be replaced in rc15(3.9.6) since they seemed to work in rc13(3.9.3) ? FROM CHANGELOG: " Changes from 5.0-rc14 to 5.0-rc15 --------------------------------- - linux: use kernel 3.9.6-patched (patched with reiserfs sync superblock fix) - linux: replace stock r8169 driver with Realtek r8168-8.036.00 "
  9. Shouldn't this just be corrected to allow Upper_case letters? An error message should also be displayed when the system can not complete a task(including the reason why).
×
×
  • Create New...