Grobalt

Hello Did someone try the Seagate Pipeline HD disks ? The power consumption is below 5w - and in germany we have about twice the power costs then in US So i ordered a low power xeon etc and now looking for good harddiscs AFR 0.55%, up to 75°C, 24x7 support - http://www.seagate.com/docs/pdf/datasheet/disc/Pipeline-Data-sheet-en-us.pdf

i can check next week when i replace all hdd in it for the exact model

i replaced the original fan with another one a bit stronger and removed the bezel in front of the optical slot -> enough cooling for 6 drive NL

i have one for my evga htpx mainboard ... dual socket 1366 - only fits into 4 or 5 cases available worldwide. Case is heavy, but great material and good concept for cables etc - worth that money

change to cable connection, 5-8mb/s is very nice with wifi !

i didnt change anything of the standard configuration and the logfile was in default place - so i dont think i have logfile in memory

ok, i will try next time - but smb shares disappeared too ... so there went something wrong

Hello, now it happened the third or fourth time - so i create this topic. System: HP Microserver, 2x4GB ECC memory, bios mod + esata - 6 drives - unraid beta 12.a I watched some himym via network and after about 2 hours the connection dropped suddenly. Webinterface failed, unmenu failed, smb failed, ssh&telnet failed. -> I went to bed . 8 hours later i plugged in my monitor to check what happened. I'm no linux guru, so i searched this forum for some scripts etc, i tried restarting unmenu first. /boot/unmenu/uu unmenu webinterface appeared - without graphics - and crashes in under 1 minute - again unresponsive. then i tried restarting samba /etc/rc.d/rc.samba restart Starting Samba: /usr/sbin/nmbd -D /usr/sbin/smbd -D did not change anything. I still can ping my unraid server and ping back to any other computer in my network. Now my knowledge is stopping me ... i copied logfile to /boot/ and plugged in the usb stick to my computer to get the logfile. What do i have to do now to get my unraid server safe rebooting without parity check ? Thanks in advance ! syslog.zip

I'm using the "6-drive Version" - hardware runs great, no issues. optical drive + esata + bios mod = 6 drives.

nobody interested or are prices needed ? memory 399 eur incl. shipping to europe, ibm br10i 69 eur each, intel xeon cpu 299 eur

Hello, selling in Germany / Europe: - SAMSUNG 32GB (2x16GB Module) DDR3 1066 Mhz ECC REG M393B2K70BM1-CF8 - IBM ServeRAID BR10i, PCIe (44E8689) Raid Controller 8 Port LSI SAS3082E-R (green layout) - INTEL XEON L5638 2,0GHZ 12M SIX-CORE Low Power (Socket 1333) *edit* everything sold

i'm from germany, too ... 125 Euros is typical price today for the 5k3000 i wouldnt pick the WD drives anymore after reading this article: http://blog.backblaze.com/2011/07/20/petabytes-on-a-budget-v2-0revealing-more-secrets/#more-337

is this the correct link ? please check, i cannot find your article* *edit* found some nice article: http://www.easycom.com.ua/cpu/intel_celeron_g530/?id=1533〈=ru&id_result_compare_1=781&id_result_compare_2=719&id_result_compare_3=449&id_result_compare_4=763#graphics - translate in your language and modify charts ... very nice cpu for people that dont need VT-D the new dual core celeron.

hi and thanks for feedback. last night i bought SAMSUNG 32GB DDR3 1066 Mhz ECC REG M393B2K70BM1-CF8 BEST PRICE, WARRANTY , PC3 8500, 2x 16GB, KIT for 355 usd incl. shipping - maybe i sell them for much more, dont know yet if i want to keep ecc. esxi data will be stored on my old x25-g2 intel ssd - not best, but much better as any mechanical disk *edit* damn... thought there are only standard udimm and registered rdimm on the market ... nice learnings ;-)

Hello all, after 2 weeks i'm happy with unraid and my licence Now all runs and i plan the big storage one - but including more services etc -> esxi. What would you prefer ? X8SIL-F + L3406 or X9SCM-F + E3-1220L Both combinations cost here in germany 320 euro ... same price, both support VT-D, etc, am i missing something ? Or .. should i go for socket 775 ? In my eyes, i need 3 pcie slots for controller - VT-D, spin down on all drives for power saving Planned is a norco 4224, 3x ibm br10i controller already here, 2TB Disks, but starting at about 10 disks 2TB. Today, i do not plan to transcode (all BD ISO), no database on the server, just a few file services, torrent, xbmc library etc. thanks for helping!

I have the same problem, yesterday i tested to copy files internally from one disk to another - between 6 and 10mb/s. The night after i run memtest 3 cycles 11 hours - all perfect. HP Microserver, Bios mod, 8GB ECC Parity: 1 EARX 2TB Storage drives: 3x WD 2TB (1x EARS, 2x EARX) 2x Samsung 750GB JD753LJ

hi, thanks for your reply - i found some other postings now and the reason why the preclear script was developed - we can close this and i will post in the preclear thread, thanks.

*update* after some forum search i did: killall emhttp nohup /usr/local/sbin/emhttp & webinterface back - but no new drives in the array and i dont see anything formatting etc. then i checked unmenu - create reiserfs on sde -> unmenu dies, standard webinterface works

Hello together, first - i am new to unraid, so please dont hurt me for bad questions I started friday buying the licence and 2x2TB and 2x750GB. I copied over some files from my existing 2x2tb drives, after that i wanted to add these 2 drives. I'm using hp microserver with bios mod, esata to internal -> 6 drives. Unraid Version 12a Today i added the 2 new drives, marked the checkbox to make sure i know it will format the 2 new disks and clicked start. Since that - i cannot reach the server via webinterface. I installed unmenu, this menu is reachable. How can i restart the gui to check when the 2 new drives are ready ? Yesterday i tried the same, but now about 20 hours later ... i rebooted and tried again. Sep 12 14:04:29 Tower emhttp_event: driver_loaded Sep 12 14:04:32 Tower emhttp: shcmd (15): rmmod md-mod |& logger Sep 12 14:04:32 Tower emhttp: shcmd (16): udevadm settle Sep 12 14:04:32 Tower kernel: md: unRAID driver removed Sep 12 14:04:32 Tower emhttp: Device inventory: Sep 12 14:04:32 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5298759 (sda) 1953514584 Sep 12 14:04:32 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5008477 (sdb) 1953514584 Sep 12 14:04:32 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 (sdf) 1953514584 Sep 12 14:04:32 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1BQ723880 (sdc) 732574584 Sep 12 14:04:32 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2780134 (sde) 1953514584 Sep 12 14:04:32 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1CQ711214 (sdd) 732574584 Sep 12 14:04:32 Tower emhttp: shcmd (17): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Sep 12 14:04:32 Tower kernel: md: unRAID driver 2.1.3 installed Sep 12 14:04:32 Tower kernel: mdcmd (1): import 0 8,0 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5298759 Sep 12 14:04:32 Tower kernel: md: import disk0: [8,0] (sda) WDC_WD20EARX-00PASB0_WD-WMAZA5298759 size: 1953514552 Sep 12 14:04:32 Tower kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5008477 Sep 12 14:04:32 Tower kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WMAZA5008477 size: 1953514552 Sep 12 14:04:32 Tower kernel: mdcmd (3): import 2 8,32 732574552 SAMSUNG_HD753LJ_S13UJ1BQ723880 Sep 12 14:04:32 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD753LJ_S13UJ1BQ723880 size: 732574552 Sep 12 14:04:32 Tower kernel: mdcmd (4): import 3 8,48 732574552 SAMSUNG_HD753LJ_S13UJ1CQ711214 Sep 12 14:04:32 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG_HD753LJ_S13UJ1CQ711214 size: 732574552 Sep 12 14:04:32 Tower kernel: mdcmd (5): import 4 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (6): import 5 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (7): import 6 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (: import 7 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (9): import 8 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (10): import 9 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (11): import 10 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (12): import 11 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (13): import 12 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (14): import 13 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (15): import 14 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (16): import 15 0,0 Sep 12 14:04:32 Tower emhttp: shcmd (18): /usr/local/sbin/emhttp_event driver_loaded Sep 12 14:04:32 Tower emhttp_event: driver_loaded Sep 12 14:04:32 Tower kernel: mdcmd (17): import 16 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (18): import 17 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (19): import 18 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (20): import 19 0,0 Sep 12 14:04:32 Tower kernel: mdcmd (21): import 20 0,0 Sep 12 14:04:35 Tower emhttp: shcmd (19): rmmod md-mod |& logger Sep 12 14:04:35 Tower emhttp: shcmd (20): udevadm settle Sep 12 14:04:35 Tower emhttp: Device inventory: Sep 12 14:04:35 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5298759 (sda) 1953514584 Sep 12 14:04:35 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5008477 (sdb) 1953514584 Sep 12 14:04:35 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 (sdf) 1953514584 Sep 12 14:04:35 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1BQ723880 (sdc) 732574584 Sep 12 14:04:35 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2780134 (sde) 1953514584 Sep 12 14:04:35 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1CQ711214 (sdd) 732574584 Sep 12 14:04:35 Tower emhttp: shcmd (21): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Sep 12 14:04:35 Tower kernel: md: unRAID driver removed Sep 12 14:04:35 Tower emhttp: shcmd (22): /usr/local/sbin/emhttp_event driver_loaded Sep 12 14:04:35 Tower kernel: md: unRAID driver 2.1.3 installed Sep 12 14:04:35 Tower kernel: mdcmd (1): import 0 8,0 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5298759 Sep 12 14:04:35 Tower kernel: md: import disk0: [8,0] (sda) WDC_WD20EARX-00PASB0_WD-WMAZA5298759 size: 1953514552 Sep 12 14:04:35 Tower kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5008477 Sep 12 14:04:35 Tower kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WMAZA5008477 size: 1953514552 Sep 12 14:04:35 Tower kernel: mdcmd (3): import 2 8,32 732574552 SAMSUNG_HD753LJ_S13UJ1BQ723880 Sep 12 14:04:35 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD753LJ_S13UJ1BQ723880 size: 732574552 Sep 12 14:04:35 Tower kernel: mdcmd (4): import 3 8,48 732574552 SAMSUNG_HD753LJ_S13UJ1CQ711214 Sep 12 14:04:35 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG_HD753LJ_S13UJ1CQ711214 size: 732574552 Sep 12 14:04:35 Tower kernel: mdcmd (5): import 4 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 Sep 12 14:04:35 Tower kernel: md: import disk4: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 size: 1953514552 Sep 12 14:04:35 Tower kernel: md: disk4 new disk Sep 12 14:04:35 Tower kernel: mdcmd (6): import 5 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (7): import 6 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (: import 7 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (9): import 8 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (10): import 9 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (11): import 10 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (12): import 11 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (13): import 12 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (14): import 13 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (15): import 14 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (16): import 15 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (17): import 16 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (18): import 17 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (19): import 18 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (20): import 19 0,0 Sep 12 14:04:35 Tower kernel: mdcmd (21): import 20 0,0 Sep 12 14:04:35 Tower emhttp_event: driver_loaded Sep 12 14:04:37 Tower emhttp: shcmd (23): rmmod md-mod |& logger Sep 12 14:04:37 Tower emhttp: shcmd (24): udevadm settle Sep 12 14:04:37 Tower kernel: md: unRAID driver removed Sep 12 14:04:37 Tower emhttp: Device inventory: Sep 12 14:04:37 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5298759 (sda) 1953514584 Sep 12 14:04:37 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5008477 (sdb) 1953514584 Sep 12 14:04:37 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 (sdf) 1953514584 Sep 12 14:04:37 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1BQ723880 (sdc) 732574584 Sep 12 14:04:37 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2780134 (sde) 1953514584 Sep 12 14:04:37 Tower emhttp: SAMSUNG_HD753LJ_S13UJ1CQ711214 (sdd) 732574584 Sep 12 14:04:37 Tower emhttp: shcmd (25): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Sep 12 14:04:37 Tower kernel: md: unRAID driver 2.1.3 installed Sep 12 14:04:37 Tower kernel: mdcmd (1): import 0 8,0 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5298759 Sep 12 14:04:37 Tower kernel: md: import disk0: [8,0] (sda) WDC_WD20EARX-00PASB0_WD-WMAZA5298759 size: 1953514552 Sep 12 14:04:37 Tower kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5008477 Sep 12 14:04:37 Tower kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WMAZA5008477 size: 1953514552 Sep 12 14:04:37 Tower emhttp: shcmd (26): /usr/local/sbin/emhttp_event driver_loaded Sep 12 14:04:37 Tower emhttp_event: driver_loaded Sep 12 14:04:37 Tower kernel: mdcmd (3): import 2 8,32 732574552 SAMSUNG_HD753LJ_S13UJ1BQ723880 Sep 12 14:04:37 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD753LJ_S13UJ1BQ723880 size: 732574552 Sep 12 14:04:37 Tower kernel: mdcmd (4): import 3 8,48 732574552 SAMSUNG_HD753LJ_S13UJ1CQ711214 Sep 12 14:04:37 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG_HD753LJ_S13UJ1CQ711214 size: 732574552 Sep 12 14:04:37 Tower kernel: mdcmd (5): import 4 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 Sep 12 14:04:37 Tower kernel: md: import disk4: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA3334400 size: 1953514552 Sep 12 14:04:37 Tower kernel: md: disk4 new disk Sep 12 14:04:37 Tower kernel: mdcmd (6): import 5 8,64 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA2780134 Sep 12 14:04:37 Tower kernel: md: import disk5: [8,64] (sde) WDC_WD20EARS-00MVWB0_WD-WMAZA2780134 size: 1953514552 Sep 12 14:04:37 Tower kernel: md: disk5 new disk Sep 12 14:04:37 Tower kernel: mdcmd (7): import 6 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (: import 7 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (9): import 8 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (10): import 9 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (11): import 10 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (12): import 11 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (13): import 12 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (14): import 13 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (15): import 14 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (16): import 15 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (17): import 16 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (18): import 17 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (19): import 18 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (20): import 19 0,0 Sep 12 14:04:37 Tower kernel: mdcmd (21): import 20 0,0 Sep 12 14:04:45 Tower emhttp: Spinning up all drives... Sep 12 14:04:45 Tower emhttp: shcmd (27): /usr/local/sbin/set_ncq sda 1 &> /dev/null Sep 12 14:04:45 Tower emhttp: shcmd (28): /usr/local/sbin/set_ncq sdb 1 &> /dev/null Sep 12 14:04:45 Tower kernel: mdcmd (22): set md_num_stripes 1280 Sep 12 14:04:45 Tower kernel: mdcmd (23): set md_write_limit 768 Sep 12 14:04:45 Tower kernel: mdcmd (24): set md_sync_window 384 Sep 12 14:04:45 Tower kernel: mdcmd (25): set spinup_group 0 0 Sep 12 14:04:45 Tower kernel: mdcmd (26): set spinup_group 1 0 Sep 12 14:04:45 Tower kernel: mdcmd (27): set spinup_group 2 0 Sep 12 14:04:45 Tower kernel: mdcmd (28): set spinup_group 3 0 Sep 12 14:04:45 Tower kernel: mdcmd (29): set spinup_group 4 0 Sep 12 14:04:45 Tower kernel: mdcmd (30): set spinup_group 5 0 Sep 12 14:04:45 Tower kernel: mdcmd (31): spinup 0 Sep 12 14:04:45 Tower kernel: mdcmd (32): spinup 1 Sep 12 14:04:45 Tower kernel: mdcmd (33): spinup 2 Sep 12 14:04:45 Tower kernel: mdcmd (34): spinup 3 Sep 12 14:04:45 Tower kernel: mdcmd (35): spinup 4 Sep 12 14:04:45 Tower kernel: mdcmd (36): spinup 5 Sep 12 14:04:45 Tower emhttp: shcmd (29): /usr/local/sbin/set_ncq sdc 1 &> /dev/null Sep 12 14:04:45 Tower emhttp: shcmd (30): /usr/local/sbin/set_ncq sdd 1 &> /dev/null Sep 12 14:04:45 Tower emhttp: shcmd (31): /usr/local/sbin/set_ncq sdf 1 &> /dev/null Sep 12 14:04:45 Tower emhttp: shcmd (32): /usr/local/sbin/set_ncq sde 1 &> /dev/null Sep 12 14:04:45 Tower emhttp: clearing disk4 disk5... Sep 12 14:07:35 Tower in.telnetd[1518]: connect from 192.168.178.31 (192.168.178.31) Sep 12 14:07:37 Tower login[1519]: ROOT LOGIN on '/dev/pts/0' from 'Fridgemaster-PC.fritz.box' Sep 12 14:16:15 Tower unmenu-status: Starting unmenu web-server

Very easy answer ... but i am new as i told, mabye an error in my brain Today we can use 20 drives as storage, 1 cache, 1 parity. 20x3TB= 60TB usable. Lets think about ... 4 Drives Raid 5 = 6 TB usable, if visible as a single drive to unraid -> 20x raidset 6TB = 120TB usable. Sure - you have to create 4x3TB Raid 5 parity too ... If one drive fails - raid 5 "hardware" recovery, unraid will not notice it. 2 drives of same raidset failure -> raidset rebuild, calculating new parity via unraid. Where is my error ? Performance shouldnt be bad as well ... the "single" drive will have much more io and transfer speed.

okay .. i will try some scenarios when i receive my new drives but website is offline, mysql error ... cannot buy license

Hello i'm new to the forum and searched a while for a media storage & cheap solution with a bit of secure data storage -> voila unraid. I'm reading since about 2 weeks many threads due to planning, cases, hdd types etc in order to exchange or upgrade my hp microserver. Because i have one xeon x5660 more than needed i built a new system, in the future virtuallized. now the question: I see some people create for the cache drive or parity drive a 2 disk raid 1 because unraid counts that as 1 drive. How will unraid count several raid 1 or raid 5 for storage ? Each raidset as 1 drive ? I hope i didn't miss the answer in this great forum! Patrick