adrianz

Hello! I've recently started purchasing parts for a long overdue update of my unRAID server and came across a pretty sweet deal on new, external Seagate 5TB Expansion Drives. I know, I know… it's better to buy dedicated NAS drives like WD Reds etc., but the price was just too good. However, before I start cracking their cases (and voiding their warranties) I'd like to test them somehow, to make sure I did't get some duds. They start up without any problems and are visible on all my computers. I've already moved few GBs to and from them, without any errors. I'm just wondering if there is something more I can do, short of doing a full on preclear (can I even do that while they're connected via USB?), to check those drives? I have access to both Mac OS X 10.11 and Windows 10 computers. Thanks for any tips!

I'm really sad to see this. I understand that you're not being paid to work on this and no one said you'll do this forever, but can we expect a compatibility update for version 6.2 in the future? Because it doesn't look like 6.2 will get a built-in NUT support, even though it was initially scheduled for that version. Anyway, thank you for all your hard work!

I'm really looking forward for the NUT support. Big +1

Thanks sgibbers17 for your help. Unfortunately, I can't order from newegg because I don't live in United States. So that's why I wanted to buy from ebay. I've read all about reflashing M1015 with the IT firmware and probably that's what I'm going to do once I actually buy this card. btw - what do you think about this seller? http://www.ebay.com/itm/IBM-SERVERAID-M1015-ADAPTER-PCI-E-2-0-X8-RAID-CONTROLLER-CARD-46M0861-LOW-P-/311010842573?pt=US_Internal_Network_Cards&hash=item4869b0d7cd - would you call them reputable? They are form States, not China and even with shipping to Poland it would still be a lot cheaper than anything I can buy locally from authorized dealers. I realise this is a refurbished item, but I don't mind.

Well, that's unfortunate :-( The cheapest card I can find locally is M1015 and it's twice the price of what I can find on ebay :-/ But I guess there is no point in buying a knockoff that's going to give me a headache and won't work properly. Thanks for the warning.

Hello, I need to buy a HBA card for my constantly growing server. Is this card a good choice? http://www.ebay.com/itm/New-LSI-MegaRAID-9240-8i-8ports-PCI-E-6Gb-RAID-Controller-IBM-M1015-46M0861-/291130540147?pt=US_Computer_Disk_Controllers_RAID_Cards&hash=item43c8bb8073 I've seen some mentions about it on the forum, and everything looks like it won't give me any problems with my unRAID, but I just want to make sure before I spend $100 on this card.

Never mind, once I've chilled a bit I figured it out. It looks like my unRAID tried to mount the old drives for a second time, but since they'd already been mouted (don't know why) it couldn't do that, so marked them as "Unformatted". I've rebooted my machine via CLI and everything seems to work as it should. I'm going to bed soon so I'll start parity check and we will know more in the morning (Central Europe Time Zone).

Now I can't even stop the array so I can try http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Check my signature for hardware and unRAID version syslog20140121ver2.zip

I was trying to expand my array with new precleared drive when very bad thing happend. My new disk is in the array but all previous disks are now unformatted :-( What should I do? syslog20140121.zip

Hey, lainie! Does your latest package from http://vbox.a1aina.com/ work with unRAID 5.0 final? And thanks for all your hard work on VirtualBox for unRAID! :-)

OK, thank you both for clarifying this to me. I also think that 48h shouldn't be such a strain for my disks, especially when they'll probably have their heads parked. I just wanted to be sure and was trying to avoid unnecessary power draw.

Quick question - if I stop my array, what makes all drives to spin up, will they later normally spin down after 1h of inactivity (in my case), just like when the array is started? Same question about a precleared drive - if I leave it after a preclear, but don't add it to an array, will it eventually spins down? I'm asking because for some reasons I have to stop the array and leave the machine powered on but don't want unnecessarily wear HDDs

via the phpVirtualBox interface you can set an RCP port and access it via your server IP:port. Go to your Virtual Machnie settings -> Display -> Remote Display tab -> Enable Server Choose appropriate port, authentication method etc. (chapter 7 "Remote virtual machines" from VirtualBox manual will clarify everything), then e.g. on Windows 7 look for Remote Desktop Connection programme and type [your.unRAID.IP.address]:[VMPortNumber] (look at the attached screenshot) and press Connect.

Yes, this motherboard causes HPA problems, so better avoid building an unRAID server based on it.

I’ve recently updated my unRAID from 4.7 to 5.0 RC8 and I’m generally very pleased with the new version but there’s one thing that still bugs me and I think it has something to do with file permissions and ownership. On 4.7 I could easily write, edit, delete, rename, etc. both files and directories right from Windows Explorer or Mac OS X Finder but now on 5.0 RC8 it’s quite complicated. For example I can copy a folder with files from my Mac or PC to unRAID but after that I can’t rename. When I’m browsing my Transmission’s downloads folder on a cache drive I can delete/rename files and directories, but when go inside one of the downloaded folders I can’t do anything except reading, otherwise Windows Explorer says I don’t have “permissions for TOWER\nobody”. It’s not a Transmission’s fault because I can manually place a file/folder on cache drive and everything is working in the same way. And that’s only few of the annoyances. After the upgrade I’ve run the “New Permissions” script. I’m using only SMB secure shares (no AFP or NFS) with 3 users: one with full read/write access (that's me) and two with read-only access (other family members). Is there a way to get back the 4.7-like behaviour on 5.0 RC8? I can do everything with the files through Midnight Commander directly on unRAID but for me that’s not very productive and it still doesn’t allow me to add single file to a folder on unRAID :-(

I installed new disk (WD20EARX) yesterday evening, started new screen session, then preclear script and then went to bed. In the morning I've noticed that all my drives (except parity) were spun up and my syslog was (and still constantly is) littered with these same lines: Oct 13 08:47:08 Tower kernel: smbd: page allocation failure: order:4, mode:0x4020 Oct 13 08:47:08 Tower kernel: Pid: 21703, comm: smbd Not tainted 3.4.11-unRAID #1 Oct 13 08:47:08 Tower kernel: Call Trace: Oct 13 08:47:08 Tower kernel: [] warn_alloc_failed+0xbd/0xcf Oct 13 08:47:08 Tower kernel: [] __alloc_pages_nodemask+0x47c/0x4a5 Oct 13 08:47:08 Tower kernel: [] __get_free_pages+0xf/0x21 Oct 13 08:47:08 Tower kernel: [] __kmalloc+0x2c/0xf0 Oct 13 08:47:08 Tower kernel: [] pskb_expand_head+0xc1/0x224 Oct 13 08:47:08 Tower kernel: [] ? timerqueue_del+0x49/0x56 Oct 13 08:47:08 Tower kernel: [] __pskb_pull_tail+0x41/0x21e Oct 13 08:47:08 Tower kernel: [] ? netif_skb_features+0x84/0x8e Oct 13 08:47:08 Tower kernel: [] dev_hard_start_xmit+0x213/0x31b Oct 13 08:47:08 Tower kernel: [] sch_direct_xmit+0x54/0x13f Oct 13 08:47:08 Tower kernel: [] dev_queue_xmit+0xfe/0x286 Oct 13 08:47:08 Tower kernel: [] neigh_resolve_output+0x135/0x15b Oct 13 08:47:08 Tower kernel: [] ? eth_rebuild_header+0x53/0x53 Oct 13 08:47:08 Tower kernel: [] ip_finish_output+0x22d/0x258 Oct 13 08:47:08 Tower kernel: [] ip_output+0x93/0x9a Oct 13 08:47:08 Tower kernel: [] ip_local_out+0x1b/0x1e Oct 13 08:47:08 Tower kernel: [] ip_queue_xmit+0x2ad/0x2ee Oct 13 08:47:08 Tower kernel: [] ? __skb_clone+0x22/0xbf Oct 13 08:47:08 Tower kernel: [] tcp_transmit_skb+0x4d3/0x508 Oct 13 08:47:08 Tower kernel: [] tcp_write_xmit+0x2f2/0x3ec Oct 13 08:47:08 Tower kernel: [] __tcp_push_pending_frames+0x18/0x6f Oct 13 08:47:08 Tower kernel: [] do_tcp_sendpages+0x463/0x490 Oct 13 08:47:08 Tower kernel: [] tcp_sendpage+0x51/0x66 Oct 13 08:47:08 Tower kernel: [] ? do_tcp_sendpages+0x490/0x490 Oct 13 08:47:08 Tower kernel: [] inet_sendpage+0x82/0x9c Oct 13 08:47:08 Tower kernel: [] ? inet_dgram_connect+0x5e/0x5e Oct 13 08:47:08 Tower kernel: [] kernel_sendpage+0x1a/0x2d Oct 13 08:47:08 Tower kernel: [] sock_sendpage+0x27/0x2c Oct 13 08:47:08 Tower kernel: [] pipe_to_sendpage+0x5a/0x6c Oct 13 08:47:08 Tower kernel: [] ? kernel_sendpage+0x2d/0x2d Oct 13 08:47:08 Tower kernel: [] splice_from_pipe_feed+0x54/0xc4 Oct 13 08:47:08 Tower kernel: [] ? splice_from_pipe_begin+0x10/0x10 Oct 13 08:47:08 Tower kernel: [] __splice_from_pipe+0x36/0x55 Oct 13 08:47:08 Tower kernel: [] ? splice_from_pipe_begin+0x10/0x10 Oct 13 08:47:08 Tower kernel: [] splice_from_pipe+0x51/0x64 Oct 13 08:47:08 Tower kernel: [] ? default_file_splice_write+0x2c/0x2c Oct 13 08:47:08 Tower kernel: [] generic_splice_sendpage+0x13/0x15 Oct 13 08:47:08 Tower kernel: [] ? splice_from_pipe_begin+0x10/0x10 Oct 13 08:47:08 Tower kernel: [] do_splice_from+0x57/0x61 Oct 13 08:47:08 Tower kernel: [] direct_splice_actor+0x17/0x1c Oct 13 08:47:08 Tower kernel: [] splice_direct_to_actor+0xbe/0x16a Oct 13 08:47:08 Tower kernel: [] ? do_splice_from+0x61/0x61 Oct 13 08:47:08 Tower kernel: [] do_splice_direct+0x4b/0x62 Oct 13 08:47:08 Tower kernel: [] do_sendfile+0x157/0x19f Oct 13 08:47:08 Tower kernel: [] sys_sendfile64+0x3c/0x7c Oct 13 08:47:08 Tower kernel: [] syscall_call+0x7/0xb Oct 13 08:47:08 Tower kernel: [] ? alloc_node_mem_map+0x70/0x8a Oct 13 08:47:08 Tower kernel: Mem-Info: Oct 13 08:47:08 Tower kernel: DMA per-cpu: Oct 13 08:47:08 Tower kernel: CPU 0: hi: 0, btch: 1 usd: 0 Oct 13 08:47:08 Tower kernel: CPU 1: hi: 0, btch: 1 usd: 0 Oct 13 08:47:08 Tower kernel: Normal per-cpu: Oct 13 08:47:08 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 0 Oct 13 08:47:08 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 162 Oct 13 08:47:08 Tower kernel: HighMem per-cpu: Oct 13 08:47:08 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 26 Oct 13 08:47:08 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 53 Oct 13 08:47:08 Tower kernel: active_anon:3771 inactive_anon:23 isolated_anon:0 Oct 13 08:47:08 Tower kernel: active_file:20377 inactive_file:732785 isolated_file:0 Oct 13 08:47:08 Tower kernel: unevictable:47966 dirty:4342 writeback:18956 unstable:0 Oct 13 08:47:08 Tower kernel: free:118064 slab_reclaimable:15655 slab_unreclaimable:6352 Oct 13 08:47:08 Tower kernel: mapped:2063 shmem:40 pagetables:163 bounce:0 Oct 13 08:47:08 Tower kernel: DMA free:3552kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:24kB inactive_file:11960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15788kB mlocked:0kB dirty:104kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:260kB slab_unreclaimable:92kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Oct 13 08:47:08 Tower kernel: lowmem_reserve[]: 0 867 3731 3731 Oct 13 08:47:08 Tower kernel: Normal free:5196kB min:3732kB low:4664kB high:5596kB active_anon:40kB inactive_anon:0kB active_file:45812kB inactive_file:671092kB unevictable:24kB isolated(anon):0kB isolated(file):0kB present:887960kB mlocked:0kB dirty:17364kB writeback:75824kB mapped:4kB shmem:0kB slab_reclaimable:62360kB slab_unreclaimable:25316kB kernel_stack:752kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Oct 13 08:47:08 Tower kernel: lowmem_reserve[]: 0 0 22913 22913 Oct 13 08:47:08 Tower kernel: HighMem free:463508kB min:512kB low:3592kB high:6676kB active_anon:15044kB inactive_anon:92kB active_file:35672kB inactive_file:2248156kB unevictable:191840kB isolated(anon):0kB isolated(file):0kB present:2932952kB mlocked:0kB dirty:0kB writeback:0kB mapped:8248kB shmem:160kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:652kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Oct 13 08:47:08 Tower kernel: lowmem_reserve[]: 0 0 0 0 Oct 13 08:47:08 Tower kernel: DMA: 24*4kB 16*8kB 10*16kB 9*32kB 9*64kB 2*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 3552kB Oct 13 08:47:08 Tower kernel: Normal: 1227*4kB 20*8kB 2*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 5196kB Oct 13 08:47:08 Tower kernel: HighMem: 13015*4kB 17161*8kB 10143*16kB 2930*32kB 229*64kB 5*128kB 1*256kB 1*512kB 0*1024kB 1*2048kB 0*4096kB = 463508kB Oct 13 08:47:08 Tower kernel: 801236 total pagecache pages Oct 13 08:47:08 Tower kernel: 0 pages in swap cache Oct 13 08:47:08 Tower kernel: Swap cache stats: add 0, delete 0, find 0/0 Oct 13 08:47:08 Tower kernel: Free swap = 0kB Oct 13 08:47:08 Tower kernel: Total swap = 0kB Oct 13 08:47:08 Tower kernel: 1172976 pages RAM Oct 13 08:47:08 Tower kernel: 944642 pages HighMem Oct 13 08:47:08 Tower kernel: 215223 pages reserved Oct 13 08:47:08 Tower kernel: 470571 pages shared Oct 13 08:47:08 Tower kernel: 373908 pages non-shared Full syslog here: http://cl.ly/3N2W2z3g0S0U. Manually spinning down disks helps for few minutes or few hours, but sooner or later this block of log reappears and disks spin up (all except parity). I've tried turning off spin-up groups (because I had problem with strange spin-ups before on 4.7 and that helped), changing chache_dirs settings (because it looks like there's something eating a lot of memory and cache_dirs was all I could think of) and restarting Samba by changing mover settings (because there is something about smbd failure in the first line). That can also be caused by preclear script (latest version 1.13), but it's still few hours until it ends or my screen installation (I've downloaded screen, aaa_terminfo and utempter packages and put them in flash/extra folder). But the funny thing is, not counting spin ups, everything is working fine - streming media from the array works, same as preclear script, WebGUI, I have telnet access, yet there is clearly something wrong going on :-( Please advise.

I'm thinking about buying new mobo ( http://www.asrock.com/mb/overview.asp?Model=B75%20Pro3&cat=Specifications ) but have some doubts about using primary PCIe x16 slot with something different than graphic card. I've written to ASRock support: And that's their response: So I should be OK, right? Does anyone of you have some expirience with using controller cards in primary PCIe x16 slot on motherboard from ASRock and/or with UEFI BIOS?

Thank you both, you've been really helpful and eased my nerves :-) Now I think during this weekend I'll finally pull the trigger. But there is one thing that i forgot about - screen (it's essential for preclear). It looks like there is already a plugin but it's no longer supported. Does any of you knows does it still works on the latest RC? Or maybe there is another way for installing screen?

Hello, I’m planning to upgrade from the version 4.7 to the latest RC and because I’ve installed some add-ons I would like your help to sort things out and prepare my unRAID for smooth sailing after upgrading to 5.0. Here’s the list of the installed add-ons and few questions: Preclear script – that shouldn’t be a problem, right? Cache_dirs – should I keep the script version from Joe L. or remove it and install a Simple Features plugin? Do I need to clean-up my go file before upgrading to 5.0 if I'm going to keep the original version? UnMenu – I know it works without a problem, but do I need it? Should I remove it before upgrading or can I keep it (and packages that I installed with UnMenu) on flash drive? I’ve installed it only because I needed these packages: - apcupsd-3.14.3 – can I install newer version in 5.0 or does it still cause some troubles? - unraid-mover-conditional-sync - unraid-mover-fix-logging - Clean Powerdown (powerdown-1.02) Are these packages still needed in 5.0? Can I install them without UnMenu, because I would like to switch to Simple Features. What is the best way to remove all that and start fresh (with UnMenu/packages only, I need my unRAID configuration, like shares, users, etc. to be intact) after upgrading to 5.0?

Thank you both! I'll watch this drive closely and as soon as get some money I'll buy replacement and preclear the old one at least 3 times to check if I can keep using it in my unRAID.

Hello! I've been doing some cleaning-up on my array moving/deleting files when this happened: Sep 12 08:22:19 Tower login[14171]: ROOT LOGIN on `pts/0' from `192.168.1.194' (Logins) Sep 12 08:33:42 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:42 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:42 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:42 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:42 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:42 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:45 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:45 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:45 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:47 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:47 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:47 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:50 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:50 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:50 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:53 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:53 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:53 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:56 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:56 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Unhandled sense code (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor] (Drive related) Sep 12 08:33:56 Tower kernel: Descriptor sense data with sense descriptors (in hex): Sep 12 08:33:56 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 12 08:33:56 Tower kernel: 00 00 9b 9f Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] ASC=0x11 ASCQ=0x4 (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 00 00 9b 8f 00 00 b8 00 (Drive related) Sep 12 08:33:56 Tower kernel: end_request: I/O error, dev sdf, sector 39839 (Errors) Sep 12 08:33:56 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39776/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39784/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39792/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39800/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39808/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39816/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39824/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39832/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39840/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39848/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39856/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39864/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39872/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39880/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39888/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39896/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39904/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39912/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39920/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39928/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39936/1, count: 1 (Errors) Should I be worried about this HDD? I've done short smart test with this result: smartctl -a -d ata /dev/sdf smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1279668 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Sep 12 09:22:28 2012 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (38160) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 171 167 021 Pre-fail Always - 6416 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1557 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 15541 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 56 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 197 197 000 Old_age Always - 11308 194 Temperature_Celsius 0x0022 114 109 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 2 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2 SMART Error Log Version: 1 ATA Error Count: 6 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6 occurred at disk power-on lifetime: 15540 hours (647 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 b8 8f 9b 00 e0 08 31d+16:09:43.324 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:43.324 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:43.320 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:43.320 SET FEATURES [set transfer mode] Error 5 occurred at disk power-on lifetime: 15540 hours (647 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 b8 8f 9b 00 e0 08 31d+16:09:40.567 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:40.567 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:40.563 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:40.563 SET FEATURES [set transfer mode] Error 4 occurred at disk power-on lifetime: 15540 hours (647 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 b8 8f 9b 00 e0 08 31d+16:09:37.809 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:37.809 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:37.805 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:37.805 SET FEATURES [set transfer mode] Error 3 occurred at disk power-on lifetime: 15540 hours (647 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 b8 8f 9b 00 e0 08 31d+16:09:35.052 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:35.052 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:35.048 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:35.048 SET FEATURES [set transfer mode] Error 2 occurred at disk power-on lifetime: 15540 hours (647 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 b8 8f 9b 00 e0 08 31d+16:09:32.295 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:32.295 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:32.291 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:32.291 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 15541 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. What do these errors mean? Is it OK to use this drive or should I replace it? Is my data safe? I'm not sure but I think "at disk power-on lifetime: 15540 hours (647 days + 12 hours)" I was deleting files from this HDD (don't know if that even matters). Please advise.

Hi msx! I'm thinking about buying the same mobo for my next upgrade, so if you don't mind I would like to ask you few questions: - does ASMedia ASM1061 SATA ports (I think those are the grey ones) work in unRAID without problems? - what unRAID version do you have - 4.7 or one of the 5.0 betas/RCs? - do you have a bigger than 2TB HDD in your system?

Nice! I've been looking for something like this, but been able to find it only with much higher total cost (price+shipping), so that's much appreciated. That's also a good card/controller, but: 1. AFAIK ASM1061 works only in 5.0, so that's no good for me 2. I'm thinking about upgrading my motherboard, and I'll probably do this with ASRock B75 Pro3. That mobo already has ASM1061 chip built-in, and I've read somewhere on this forum that having a second ASM1061 controller in your rig makes unRAID crash or something like that. I'm not sure about this, but I strongly belive that I've seen such warning around here. If you can buy one that doesn't silently corrupts your data (that's possible - not every single one controller card based on this chipset does that, but that's a gamble), it'll work OOTB, but what you're saying about max bandwidth is true, although if you're not using SSDs you probably won't notice the difference. Once again, thanks for your help, abjr!

Yes, that's exactly what I'm looking for. I already have that card (although with a different branding), but SiL3132 chipset is no longer recommended - check this out: http://lime-technology.com/forum/index.php?topic=18428.msg167122#msg167122 - that's why I'm looking for a new one. Plus Monoprice is not an option for me, because shipping to Europe would probably cost much more than this card itself, and I've found those "shady ebay sellers" to be quite reliable :-) Anyway, thanks for your input, Johnm!

What do you think about this controller card? http://www.ebay.com/itm/eSATA-SATA-II-IDE-3-5-RAID-to-PCI-E-PCI-Express-Converter-Adapter-Card-JMB363-/170896398891?pt=US_Drive_Cables_dapters&hash=item27ca381a2b I think it's the cheapest one available at the moment. Except for the minor inconvenience with the eSATA (there is a version with two internal SATA ports, but it's more expensive and with $32 shipping :-/ ) it should work well in unRAID 4.7 server, right?