Jump to content

mbryanr

Members
  • Posts

    1,294
  • Joined

  • Last visited

Posts posted by mbryanr

  1. I didn't find a specific reference to the Areca 1300...but it uses the mvsas driver (same as the Supermicro MV8 that many use) and others are using the Areca 1200 in unRAID

    http://lime-technology.com/forum/index.php?topic=7150.msg69515#msg69515

    Your syslog looks good.

     

    Edit: Don't know what improvements you would get, but looks like it uses another driver as well.  Don't know if it is included in the unRAID kernel

    http://www.areca.com.tw/support/s_linux/nonraid_linux.htm

  2. Strange..works on my setup <see below> Should probably go in the SImpleFeatures thread to get more attention.

     

    Simple Features....

    Line 61: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	cache_dirs process ID 857 started, To terminate it, type: cache_dirs -q
    Line 62: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	----------------------------------------------
    Line 63: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	movies
    Line 64: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	---------- caching directories ---------------
    Line 65: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	version=1.6.6
    Line 66: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	command=find -noleaf
    Line 67: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	max_depth=9999
    Line 68: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	max_seconds=10, min_seconds=1
    Line 69: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	vfs_cache_pressure=10
    Line 69: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	vfs_cache_pressure=10
    Line 70: 2012-07-01	19:43:40	notice	192.168.1.108	user	cache_dirs	command-args=-w -B -m1 -M10 -d9999 -eAutumn -e Documents -e music -imovies

     

    Earlier unMENU install

    Line 536: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	cache_dirs process ID 3755 started, To terminate it, type: cache_dirs -q
    Line 537: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	----------------------------------------------
    Line 538: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	music
    Line 539: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	movies
    Line 540: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	Documents
    Line 541: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	Autumn
    Line 542: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	---------- caching directories ---------------
    Line 543: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	version=1.6.5
    Line 544: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	command=find -noleaf
    Line 545: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	max_depth=9999
    Line 546: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	max_seconds=10, min_seconds=1
    Line 547: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	vfs_cache_pressure=10
    Line 547: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	vfs_cache_pressure=10
    Line 548: 2012-06-24	12:39:03	notice	192.168.1.108	user	cache_dirs	command-args=-w -m 1 -M 10 -d 9999 -a -noleaf
    

  3. I just setup my unRAID box this weekend. I plan on using it for MKV rips of my hundreds of HD DVD titles. I already use  a 56TB WHS for my hundreds of BD titles in the ISO format. I would do the same with my HD DVD titles if the media players could play HD DVD ISOs.

     

    Do you have any pics of that 56tb server you could post in pimp my rig?

     

    cc.

     

    unRAID

    http://lime-technology.com/forum/index.php?topic=2031.msg139143#msg139143

    WHS

    http://www.avsforum.com/avs-vb/showthread.php?p=20870157#post20870157

  4. Looks like you had a drive with previous errors (607 sectors reallocated, 52 sectors pending re-allocation)

     

    Those  52 sectors pending re-allocation were successfully rewritten after zeroing the disk.

    Raw Value = 0

     

    Looks like a Samsung drive.  If I guessed I'd say a HD154UI?

    Anyways, the Reported_Uncorrect were (read) errors that could not be corrected with ECC (lower number better)

     

     

    Although "OK" - I would run another preclear cycle.

     

  5. I'm interested in your build as a second/test server for myself. :)  Primarily to learn Ubuntu and run Crashplan. unRAID was my first foray into the Linux OS world and I've been impressed with the performance.

     

    I like the Helios, but will probably choose something different for improved cable management.

     

    You may find the fans dB to be excessive for the bedroom.  A fan controller helps some. A possibility is disconnecting the large 230mm fan. I was tempted to do that when I had 3 drives installed. Replacement of the stock fans is another option you mentioned.

     

    btw, I like your choice in power supplies, although it may not run as efficiently as a smaller PSU, Seasonics are solid, modular is a plus for cable management, and I will bet that your build grows to 10-12 drives! ;D

     

    One valuable addition to your build - UPS.  I found mine to be invaluable in protecting the server, and avoiding those long parity checks - especially when they occur <1 day after completing a scheduled check.

     

    Welcome to the forum and enjoy!

     

    Edit:  Remember to check the serial number on your Samsung drives and update the fw if necessary.

     

  6. 1 disk is a new WD20EARS (they all will be when I'm doing this for realz) and I did the -a flag to toggle advanced format. This went through with no problems. However, my friend told me that I did it wrong, and that it should have been -A (in caps) and not -a in lowecase.

     

    1.) Is this true, and what did I mess up - something about the partition?

    2.) What's the best way to fix this? Do I need to preclear again?

    What version of pre-clear were you using?

    IIRC the pre-clear dialog states:

    -a option elected, partition will start on sector 63)

    (it will not be 4k-aligned)

    Are you absolutely sure you want to clear this drive?

    (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes

    Clearing will NOT be performed

     

     

    http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246

    1.  True.

    -a = force MBR-unaligned.

    -A = force starting sector to be on sector 64 for 4k alignment.

     

     

     

    2. Note:  The -A is not required if you have the "MBR-4K Aligned" set as default in your device settings.  Any drive can be formatted to start on sector 64

    Also, there is no performance or storage loss in

    starting Partition 1 in sector 64 for ALL drives, not just AF drives.

    http://lime-technology.com/forum/index.php?topic=10198.0

     

    I believe you can: (verify with more experienced users)

    1.  Set "MBR-4K Align" in the unRAID management page

     

    2. Run this command from telnet-

    dd if=/dev/zero of=/dev/sdX count=2

    where sdX = the device for the disk being cleared.

     

    This will clear the MBR of your disk.

     

    Edit:

    Found Joe created the preclear -z option to accomplish the same.  Can someone verify this is the correct procedure?  Thanks.

    http://lime-technology.com/forum/index.php?topic=2817.msg102326#msg102326

     

  7.  

    Just trying to have some fun. In the end its probably exactly what I'm going to do since my requirements would require the opening size anyways. LOL

     

    I just saw things like this and thought man that is cool as well I found a lot that was well NOT COOL.

     

     

    tie-fighter-pc-case-mod.jpg

     

    What is not cool about a tie-fighter?? ;D

     

    how about an arcade game??

    Paradise-Lost-Game.jpg

  8. Very nice and clean.  I dig your project link too.  What SATA cables are you using?

     

    Thanks. The SATA Cables are from www.monoprice.com (another great site I learned about from this forum). They are KGear GC18AKM SATA3 cables. I ordered them color-coded.

     

    Red = Data

    Blue = Parity

    Black = Cache

    Dang! That's a nice idea. Next time when I need more cables, I'll see if I can order a rainbow set.  :)

     

    They have Limetech green as well.

    Mine is setup as

    Limetech Green - Parity

    Blue = Data.

  9. Getting a 15 bay unit with 3TB disks = 42tb roughly usable storage right? That would be able to handle replacing both of these monster machines, in a single 15 bay unit.

     

    (I want to know more about this 20 bay unit mentioned earlier in the year!)

     

    unRAID currently does not support 3TB disks. The max array width is 22 (1 parity, 1 cache, 20 data drives)

     

    20x2TB = 40TB max.

     

    Check out the "Pimp Your Rig" thread as a start, then the Recommended Builds Wiki entry

  10. Joe, I noticed the Load Cycle Count increase <pre-->post>.  It got me thinking about the WD high LCC issue.  I found a decent summary in the Syno forum (I have a 210j), but nothing yet in the unRAID wiki.  Is it something that should be notated or a non-issue?

     

    http://lime-technology.com/forum/index.php?topic=5086.msg53803#msg53803

     

    http://forum.synology.com/enu/viewtopic.php?f=124&t=11682#p49067

  11. Finally, my first disk is done pre-clearing. Are my results any good? Can someone please look at the syslog. I have no idea whether it's good or bad. Sorry still learning...

     

    Joe can confirm, but it looks good.

     

    Here are (2) quick starter instructions for interpreting results

    http://lime-technology.com/forum/index.php?topic=2817.msg53337#msg53337

     

    http://lime-technology.com/forum/index.php?topic=8278.msg81032#msg81032

     

    @somewhatlost That value is a RAW value, which change frequently and are used by manufacturers.

     

    Each Attribute has a six-byte raw value (RAW_VALUE) and a one-byte normalized value (VALUE)... The format of the raw data is vendor-specific and not specified by any standard. To track disk reliability, the disk's firmware converts the raw value to a normalized value ranging from 1 to 253. If this normalized value is less than or equal to the threshold (THRESH), the Attribute is said to have failed, as indicated in the WHEN_FAILED column. The column is empty because none of these Attributes has failed. The lowest (WORST) normalized value also is shown; it is the smallest value attained since SMART was enabled on the disk. The TYPE of the Attribute indicates if Attribute failure means the device has reached the end of its design life (Old_age) or it's an impending disk failure (Pre-fail). For example, disk spin-up time (ID #3) is a prefailure Attribute. If this (or any other prefail Attribute) fails, disk failure is predicted in less than 24 hours.

    Reference

    http://xpt.sourceforge.net/techdocs/nix/disk/general/disk18-DiskTestHealthMonitoring/ar01s06.html

     

×
×
  • Create New...