Fireball3

As soon as the other manufacturers join the market with their products, prices will drop as usual. The development on the warranty area is indeed not very pleasant for soho. Since there are just 3 players left on the market the philosophy has dramatically changed. Not so long ago, almost all drives came with 5y warranty... To take this into account I decided to take the "RAID" literally: „Redundant Array of Inexpensive Disks“ With a fully redundant server as backup I should be safe enough even when I operate used disks. I'm acquiring used disks only for my arrays and I'm able to get the 3 and 4 TB drives for about 20€/TB on the market. If a drive dies I don't care, if it serves me one year or more (and probably most of them will do) I'm already satisfied. This may change when I'm running out of expansion slots&&memory but at the moment the sky is very high.

So, my fellow race car enthusiasts...let me have opinion. What are your bets on the results of this F1 season? World champion: 2'nd: 3'rd: Constructors championship: 2'nd:

I'm not yet finished expanding to 4TB... http://www.seagate.com/about/newsroom/press-releases/Seagate-ships-worlds-fastest-6TB-drive-enterprise-capacity-pr-master/

Yes, tested it and now it works also. Thanks for fixing it!

Coming back to report my findings. When accessing the wiki directly from the unRAID site it works, I'm able to edit the wiki. When accessing the wiki out of the forum through this link: http://www.lime-technology.com/wiki/index.php/UnRAID_Wiki I can't edit the wiki. This link appears in the News section on the main page of the forum (fades in after some time).

Just started the 2nd run with 5.0.5 and the x64 preclear script. readvz64v3.zip & LC_CTYPE=C /boot/preclear_disk15b.sh -f /dev/sdX Edit: Now I found out, that the x64 binary won't work on the x86 unraid... : (guess I was to eager on testing, so that I turned my brain off.../facepalm/) Should there be a check to avoid such?

Here we go, first run completed: ========================================================================1.15b == invoked as: ./preclear_disk15b.sh -A -f /dev/sdc == HitachiHDS5C4040ALE630 PL1311LAG38ZJH == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 12:18:50 (90 MB/s) == Last Cycle's Zeroing time : 10:55:48 (101 MB/s) == Last Cycle's Post Read Time : 14:21:13 (77 MB/s) == Last Cycle's Total Time : 37:37:02 == == Total Elapsed Time 37:37:02 == == Disk Start Temperature: 24C == == Current Disk Temperature: 26C, == ============================================================================ ========================================================================1.15b == invoked as: ./preclear_disk15b.sh -A -f /dev/sdb == HitachiHDS5C4040ALE630 PL1321LAG325VH == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 12:27:01 (89 MB/s) == Last Cycle's Zeroing time : 11:06:19 (100 MB/s) == Last Cycle's Post Read Time : 14:32:25 (76 MB/s) == Last Cycle's Total Time : 38:06:57 == == Total Elapsed Time 38:06:57 == == Disk Start Temperature: 24C == == Current Disk Temperature: 27C, == ============================================================================ ========================================================================1.15b == invoked as: ./preclear_disk15b.sh -A -f /dev/sdd == HitachiHDS5C4040ALE630 PL2331LAG8W1YJ == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 12:25:54 (89 MB/s) == Last Cycle's Zeroing time : 11:05:24 (100 MB/s) == Last Cycle's Post Read Time : 14:27:29 (76 MB/s) == Last Cycle's Total Time : 37:59:59 == == Total Elapsed Time 37:59:59 == == Disk Start Temperature: 24C == == Current Disk Temperature: 26C, == ============================================================================ The next run will be with the x64 edition. Is the updated version ready yet?

...all of a sudden it's working again ... ... witchcraft and wizardry

Oh, well if it's that way, I would recommend you use some used parts and get a better understanding of how a computer looks like from the inside. There are so many (trivial) things you can mess up and probably nobody can think of all and write them down for you. Start by disassembling an existing but working (scrap) computer and put it together a couple of days later. When holding the mainboard in your hands try to figure out what interfaces you have there. Use the manual as reference, google and ask questions in the forum. If it boots up again after your surgery, you already learned a lot. Learning by doing - it's probably the best approach before you get yourself pricey equipment and break it while learning. You will most likely end up with two unRAID servers after all - my experience . So it's probably OK if you start your first build with used parts. Anyway you will have to spend a nice amount for 5x 4TB hard drives to accommodate your existing data. Therefore, your enclosure should have space for 5+ 3.5" slots and your board should bring 5+ sata ports also. For later expansion you will want to have many PCIe slots (x4 and x8) to plug in sata cards. If this first build is running as expected, you will pretty soon want to backup it somewhere. By that time you're more experienced and will probably know for yourself what kind of hardware you want to use for your second build. Perhaps your needs will have altered also. See the hardware section in the wiki for unRAID compatible hardware. I remember having seen some reference builds from limetech somewhere. I will try to find that for you. Here you go - gives you an idea of what you should look for. Also good to know.

Figured out, the problem lies within my browser. At home it works and when using IE on this machine it also does. I wonder what changed because it worked once...

Ctrl+C

I'd recommend this: http://www.silverstonetek.com/product.php?pid=184 Almost hotplugging - don't need to extract the whole enclosure to swap a drive.

OK, switching to pc15b Is this also valid for x64 or for x86 only? Edit: Also noticed, that without the -A it reports that the drive won't be aligned although it is a 4TB drive. Is this correct?

I'm going to start the preclear of 3x 4TB Hitachi now. I will start with 5.0.5 and the pc15b2.zip Stop me if I'm wrong.

Strange, when I'm opening the wiki, I see the "log in" button in the top right corner. When clicking it, I enter my credentials but I still can't edit. Have to contact Tom.

As you already found out, for some reason your emhttp is not starting. Something must be wrong with your config. Do you have a backup of your thumbdrive? Save your actual content of your thumbdrive and then narrow the issue down by deleting the config files. Start with the samba config. Then remove the secrets.db But I have to admit, that your console problems are somewhat strange! You could try a different thumbdrive with a stock install of unRAID. Just to check if that one boots up the GUI. If so, it's probably "only" a config issue.

Good to hear you made it! But be careful with v6!!! It is still beta!

Don't remember if it's called exactly "safe mode". When unRAID boots from your thumbdrive you can select to boot "normal" or "safe/backup" or do memory testing. It boots without plugins then. (you need a monitor and a keyboard to see/select it) But I'm not sure if it's OK to modify the array in that mode - I assume it is.

Probably one of those plugins is interfering... Gary, can the changes be done in safe mode? (boot to safe mode and change the parity drive etc.)

Gary, obviously the array is still OK.

I've been rethinking this. Parity swap would work, but adds additional effort with the "replaced drive". The procedure is more suitable if you want to replace a failed data drive with a bigger drive than your parity. (It means you have to effectively change 2 drives in your array at the same time. To be able to do so, you have to cause a data drive to red-ball. See the link in my prior post.) In your case, what you did in your post here is recommended and should work. Did you check "Yes I want to do this"? If you can't "start" (button greyed out) then I'm a bit concerned. The same might occur on any other action (parity swap) - then you have even more issues to deal with. At this point I suggest you contact limetech and let Tom have a look at this.

If you "play" with the GUI, you "play" with your data! Have you done a parity check with your initial setup? What does the screenshot look like when all drives are green? I suppose 1,5TB parity? (please post a screenshot) You have 3 options then: 1. like gary already described replace the parity drive, let parity rebuild (have the old parity drive as backup) add the rest of the drives in a next step (if they have been precleared it's a matter of minutes) Did you check "Yes I want to do this"? 3. via "parity swap" - array is protected adds additional effort with the "replaced drive" 2. via "new config" - array has no parity protection until the parity is rebuilt but: you can add all drives in one step WARNING: TRIPLE CHECK, THAT YOU DON'T ASSIGN AN EXISTING DATA DRIVE AS NEW PARITY DRIVE!!! (not possible in your case but others may read this too) What action do you prefer? Edit: have been rethinking my proposal...

Can somebody confirm this? Usually the wiki was editable while I was logged in the forum. Something is wrong.

Can you tell us if it supports spindown and drive temperatures in unRAID? I will include it in the wiki.

Following this discussion it should work since it supports passthrough. According to spec it is the LSISAS1068 chip that is supported by unRAID OS. This is confusing because I learned that the 1068 is not supporting big drives... Perhaps this is different? Please report back if you find out! Does it support spindown in unRAID and does it support drive temps?