keyvan

Members
  • Posts

    44
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

keyvan's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Interesting. Can you select one single drive to have unRAID keep spinning? Yes, you can. With unRAID you can give each individual disk a different spin-down timer, ranging from 15 minutes to never. I prefer to leave all of mine at the default 1 hour, but in keyvan's case I can see an argument for setting a few to 4 hours or never. Thank you for your kind suggestions regarding the spin-up issue with instant playback on sonos / airplay. There are a number of reasons why I run WHS alongside unRaid. They are (in order of priority): 1. MyMovies central database manager for clients 2. iTunes server - this is accomplished by running itunes as a process in WHS so that with home-sharing enabled it can serve media to Apple TV's / airport express / other airplay enabled devices - apple lossless is the format of music files. 3. Music files for sonos 4. Back-up of lan connected pc's 5. photos & home movies (videos) which are accessed via WMC front end. Other reasons are that the WHS Acer box I got was fairly cheap (£200 for 2x 1TB Acer with 2 bays free) - I can somewhat manage power consumption in WHS (which would be the justification to keep data on spun down disks) by using a combination of Lights Out (a utility for making WHS go to sleep) and WOL from clients to wake up the server. It is not the most elegant solution but it works...
  2. I use it stream to 4x Win7 HTPC's running WMC and MyMovies. I also use a SFF WHS V1 to manage the database for MyMovies and the store music for Apple devices and Sonos multi-room music system. The reason for keeping music on WHS is the spin-up delay, whilst acceptable for movies, it is a little too slow for Sonos and Apple TV's and sometimes they time out... So my unRaid box is purely a storage appliance for serving up DVD and BD titles and archive storage for other data. The media is about 500 DVD's, 200 BD's and 800 episodes of TV shows. The DVD's are ripped to video_ts folders and BD's are ripped to .iso images. The clients are SFF pc's (Acer & ASRock Atom CPU with ION GPU) with Bluray drives and arcsoft TMT 3. I started out with WHS as the network storage device, but Disk Extender & Migrate (now dropped in the new WHS) made bluray streaming virtually unusable.
  3. I just noticed the keyboard!!! It was only there while memtest was running... It is now closed up with 4 drives (seagate & Hitachi 2tb 5900rpm) running preclear script. Only the top 4x 5.25" bays can take drive cages. The middle has a 4x 3.5" drive bays (not showing in my photos as it is has been temporarily removed) this can be turned 90 degrees drives can face sideways or front facing. I removed the top (180mm) fan - it was in the way of the M/B power cable and I am not sure if it would be that useful in a case with no hot high end graphics cards. I considered the Antec 900 or 1200 with Norco 5 in 3 drive cages, but went for the FD XL as it gives me 16 drives (1 more than the 900) and drive trays make adding / removing very easy. With 4 drives inside so far the box is virtually silent. It is also a nice looking box with the door closed.
  4. This is my 3rd unRaid build. The last one was a 20bay Norco build. The FD XL build is for a friend who does not have a wiring closet to house a rack-mount unit. His layout is such that the server has to reside in a closet near his living room so noise is an issue. I settled on the Define XL as it would give 15/16 drives capacity with relatively low noise and if he ever wanted to go to the 20 disk system then 4 additional drives could be added using an external enclosure and a esata port multiplier. Although I have yet to test how that works with unraid. OS at time of building: unRAID 4.7 Pro CPU: Intel i3 540 3.0 Ghz Motherboard: Super Micro X8SIL-F-O RAM: 2x Kingston 2GB DDR3-1333 ECC CL9 THERMAL SENSOR - 4Gb total Case: Fractal Designs Define XL http://www.fractal-design.com/?view=product&category=2∏=54 Drive Cage(s): None so far - might use 2x 3in2 Icy Docks for 6 drives in 4x 5.25 drive USB Memory drive: Kingston DataTraveller 102 2Gb Power Supply: Corsair 650w Professional Series modular PSU SATA Expansion Card(s): Super Micro SASLP-MV8 Cables: 6x SATA (supplied with M/B) 2x 30cm 8087 forward break-out cable Fans: 2x 140mm front-1 supplied with case and a Corsair fan from an old case. 1x 140mm rear. 1x 180mm top of case -removed this fan. Parity Drive: Hitachi Deskstar 2TB Hard Drive SATAII 7200rpm 32MB Cache - OEM Data Drives:3x Hitachi 2TB 3.5" Deskstar Coolspin SATA-III 6GB/s 5900rpm 32MB 3x Seagate ST2000 DL003 5900rpm SATA III Cache Drive: None Total Drive Capacity: 30Tb capacity - 12Tb current size Primary Use: Storage for DVD's and BD ISO's for MyMovies clients Likes: Low noise, good looks, good value (compared to buying hot-plug caddies.) Dislikes: Heavy, bulky Add Ons Used: unMenu, PreClear Future Plans: Boot (peak): Idle (avg): Active (avg): Light use (avg): This is a build in progress, right now I have 3 disks pre clearing in my other unraid box and this one is running memtest - as the photo shows will keep updating as the build progresses future edits
  5. Yes I did. They will ship one with the case (no charge) if you ask for it in the comment section of your online order.
  6. I thought I would give the new version a try to see if the issues I was having when trying to preclear a drive connected to the SASLP-MV8 card would be resolved with the latest release. I hooked up an empty drive which had aleady been precleared using an Adaptec 1430 - see report below: ========================================================================1.7 == invoked as: ./preclear_disk.sh -A /dev/sdj == ST2000DL003-9VT166 5YD1BNYS == Disk /dev/sdj has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:05:35 (91 MB/s) == Last Cycle's Zeroing time : 5:23:41 (103 MB/s) == Last Cycle's Post Read Time : 16:26:32 (33 MB/s) == Last Cycle's Total Time : 27:56:54 == == Total Elapsed Time 27:56:54 == == Disk Start Temperature: 26C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 105 117 6 ok 10484760 Seek_Error_Rate = 60 100 30 ok 1013495 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 70 74 45 near_thresh 30 Temperature_Celsius = 30 26 0 ok 30 Hardware_ECC_Recovered = 37 27 0 ok 10484760 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Preclear is now working with this drive on the SASLP port I think... But I also got the same messages in the sys log: Mar 14 21:10:39 Tower2 login[4408]: ROOT LOGIN on `pts/0' from `192.168.1.101' (Logins) Mar 14 21:11:59 Tower2 ata_id[5149]: HDIO_GET_IDENTITY failed for '/dev/block/8:112' (Minor Issues) Mar 14 21:11:59 Tower2 kernel: sdh: sdh1 (Drive related) Mar 14 21:12:39 Tower2 kernel: ------------[ cut here ]------------ Mar 14 21:12:39 Tower2 kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Mar 14 21:12:39 Tower2 kernel: Hardware name: System Product Name Mar 14 21:12:39 Tower2 kernel: Modules linked in: md_mod xor i2c_i801 i2c_core r8169 pata_jmicron jmicron ahci sata_mv mvsas libsas scst scsi_transport_sas (Drive related) Mar 14 21:12:39 Tower2 kernel: Pid: 5600, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Mar 14 21:12:39 Tower2 kernel: Call Trace: (Errors) Mar 14 21:12:39 Tower2 kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Mar 14 21:12:39 Tower2 kernel: [<f842869a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Mar 14 21:12:39 Tower2 kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Mar 14 21:12:39 Tower2 kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Mar 14 21:12:39 Tower2 kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Mar 14 21:12:39 Tower2 kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Mar 14 21:12:39 Tower2 kernel: ---[ end trace 2a0acd6c3ce8f845 ]--- I assume these do NOT effect the preclear process and/or unraid operation? Thanks
  7. There is no issue (as far as I can tell..) with using the AOC-SASLP-MV8 in unraid. Even though preclear will not run on a drive attatched to this card, unraid formatted the drive - added it to the array - it reports temp and has no problem with spin down/up. The problem only shows up with preclear. I can only conclude that preclear needs / access's smart commands/data which unraid does not... ? My problem (I think spencer785 too) was preclearing ANY disk on this port. I can not say for sure if the failure to execute preclear problem was the port or the drive (I am using the new seagate DL2000) - I can test for this later - I have a new hitachi being shipped now, I shall try to to run preclear on this drive from the same port and see what happens..
  8. I normally run 3 cycles (each cycle is run once, power-down, run next cycle). Here are the results from the cycle 1 & 2: ========================================================================1.7 == invoked as: ./preclear_disk.sh -A /dev/sdb == ST2000DL003-9VT166 5YD1BNYS == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:04:38 (91 MB/s) == Last Cycle's Zeroing time : 5:21:52 (103 MB/s) == Last Cycle's Post Read Time : 13:06:10 (42 MB/s) == Last Cycle's Total Time : 24:33:47 == == Total Elapsed Time 24:33:47 == == Disk Start Temperature: 30C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 76458848 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 73 70 45 ok 27 Temperature_Celsius = 27 30 0 ok 27 Hardware_ECC_Recovered = 37 100 0 ok 76458848 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ========================================================================1.7 == invoked as: ./preclear_disk.sh -A /dev/sdi == ST2000DL003-9VT166 5YD1BNYS == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:04:25 (91 MB/s) == Last Cycle's Zeroing time : 5:23:45 (102 MB/s) == Last Cycle's Post Read Time : 13:17:49 (41 MB/s) == Last Cycle's Total Time : 24:47:05 == == Total Elapsed Time 24:47:05 == == Disk Start Temperature: 28C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 114 6 ok 165117904 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 72 45 ok 29 Temperature_Celsius = 29 28 0 ok 29 Hardware_ECC_Recovered = 36 27 0 ok 165117904 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
  9. Reading post here I gather the problem is more prevalent with drives which have the old (c32) firmware. The latest firmware (C35) is available for download on the Seagate site. The LP ST3200054AS is now an End of Line item and no longer manufactured -replaced by the ST2000DL003. They are selling in the UK for less than their predecessor (GBP 60 ~ $90 including 20% sales tax). I have been using 7200rpm Hitachi's with no issues at all, but I wanted to try some low power drives and given these are cheaper than the WD EURS (replacement for EARS) I bought 2 to try. I am preclearing 2 of these now. The first cycle should be done soon and I can post the results (here or the preclear results thread) if anyone is interested.
  10. There is only one that I have seen which compares on price / spec. That's the Highpoint 2684: http://www.highpoint-tech.com/USA_new/series_rr2600.htm http://www.newegg.com/Product/Product.aspx?Item=N82E16816115057 Searching this forum indicates that there are serious issues with this adapter and unraid in normal use (i.e. not just preclear). I think supermicro card should not be discounted just because of the preclear issues. I ihave just read a post from another user I think due to the fact that preclear relies on smart data and commands does not mean that the host card which does not fully provide this; can not perform its functions in unraid. Unless I am wrong, in which case it would be great if someone can correct me...
  11. Only if you have already tried to run preclear on a disk attatched to your SASLP card and got the same error as spencer785 or I got.
  12. No... the disk is precleared, BEFORE adding it to the array. It's just that the port that is used to preclear has to be an unused port that is not on the SASLP-MV8 - in my case that would be a free port on the adaptec or the 2port JMB363 card in my new build:http://lime-technology.com/forum/index.php?topic=11202.0 Once a disk has been formatted and added to the array, the array will not start without that disk.
  13. Did you preclear any of the drives attatched to these ports? Another user and I are having an issue where preclear does not work when used on drives attatched to this card:http://lime-technology.com/forum/index.php?topic=11357.msg109545#new I presume given that you have 2 cards, the blue (graphics / 16x) slot has one of the cards installed? Thanks
  14. I don't think anyone is suggesting that the card is not compatible with unraid. It clearly works..! As you mentioned, dozens, if not hundreds, of users have installed and used these cards without problems. It is about the only card out there with 8 ports on PCIe at a reasonable price. The others are much more expensive with raid functions which will never be used by unraid (3ware, adaptec, etc.). Like spencer785, I have it "working" with unraid in so far as the disk attacted has been formatted and added to the array. The issue is the functionality of this card with preclear. It seems to be more common on non-supermicro motherboards. Having looked around the forum, it seems users who have it installed on supermicro motherboards have none of the issues mentioned above and yet there are a number of posts about their behaviour when installed in ASUS or Gigabyte boards. Again the issues are more to do with SMART commands/operations than drive errors or performance. I have swapped drives to other ports on the system and only those connected to the card refuse to do preclear. The adaptec 4port card has none of these issues and works well in all motherboards. Ultimately this is not a huge problem if you can do preclear on another port and then use the ports on the SASLP-MV8, it is more a peace of mind issue to believe that these minor issues related to preclear will not manifest into serious problems in long term operation. So if the problem can be diagnosed, it can be determined if it can lead to problems in everyday usage.
  15. I have an identical drive (Seagate LP ST2000DL003) being precleared on the same box with no issues - but that one is connected to an adaptec 1430. I added the drive to the array to see if unraid had any issues with. It formatted OK and shows up but then on the devices page I get: disk1 device: pci-0000:00:1f.2-scsi-1:0:0:0 host7 (sdd) Hitachi_HDS722020ALA330_JK11A4B8HX764W disk2 device: pci-0000:00:1f.2-scsi-2:0:0:0 host8 (sde) Hitachi_HDS722020ALA330_JK11A4B8HX7PMW disk3 device: pci-0000:00:1f.2-scsi-3:0:0:0 host9 (sdf) Hitachi_HDS722020ALA330_JK11A4B8HXAS7W disk4 device: pci-0000:00:1f.2-scsi-4:0:0:0 host10 (sdh) Hitachi_HDS722020ALA330_JK11A4B8HX7PDW disk5 device: pci-0000:00:1f.2-scsi-5:0:0:0 host11 (sdi) Hitachi_HDS722020ALA330_JK11A4B8HY20JW disk6 device: pci-0000:01:00.0-sas-phy1:1-0x0100000000000000:1-lun0 host0 (sdg) ST2000DL003-9VT166_5YD1PQX5 disk7 device: unassigned Disk6 is obviously connected to the AOC-SASLP.