inertius

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

inertius's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Nope, I never found a root cause. I ended up getting a USB 3.0 card (from Anker I think - 2 port PCIe one) that seems to work much better than the onboard USB 2.0. I have my boot flash connected to that card and I haven't had the problem since. You might give it a shot if you have a spare PCIe slot; adapter cards are pretty cheap.
  2. These are all very welcome features! Being able to easily add applications with Docker will make me that much happier having moved from WHS to unraid. I have 10 disks in my server. The biggest benefit I see from having them spin down is heat. I live in a tiny condo, so the server has to be in my room. A room with more than one computer running is absolutely killer in the summer.
  3. Ran a parity sync over night, and when I checked the syslog this evening, I saw several lines reading: Tower kernel: FAT-fs (sdi1): Directory bread(block 32768) failed This is using 6.0 beta 3. It looks like the USB with the unraid software got disconnected and did not get remounted. I'm wondering what I should do to remount the drive so it can save the array configuration, since it took a day to do a complete parity sync. Additionally, is there anything in my syslog that points to the cause of the disconnect? Could it be a bad flash drive? I've been spending several days trying to get my new unraid server going, and this is just the latest hurdle to conquer. Thanks for any assistance! UPDATE 3/26/2014 Not sure what the root cause is, but my workaround for now is to manually remount the flash to /boot when this occurs: mount -o noatime,nodiratime,umask=0,shortname=mixed -t vfat /dev/sdX# /boot I had to run fsck on the flash to clear the dirty bit, but otherwise, all seems good with the flash. Just in case anyone else stumbles upon this through Google, I'm using a new ASRock C2550D4I motherboard with the 1.40 BIOS. No USB devices other than the flash drive are connected. There may still be bugs with this board's firmware, or the USB driver. It did not seem to make a difference when I used a different USB port. unraid_syslog_disconnected_boot_flash.txt
  4. I've also been struggling with getting my server upgraded with a new C2550D4I motherboard, and it sounds like I'm having similar issues. I had several disks redball, and I noticed a lot of ata resets, and other read errors with disks attached to the Marvel 9230 controller. It looks like the SATA ports coming from the Atom chip work fine though. I'm going to try a BIOS update and change some SATA settings for the Marvell controller, and see what happens. This is a big upgrade in terms of performance and features from my old Atom 330-based NAS, so I really hope I can get it working!