July 26, 201213 yr Hi, My apologies if these has been asked before somewhere and I missed it. I have read a lot of good posts/questions/answers written by many of you here about the cache drive and the mover script and how it works, but I still had a few specific questions/needed confirmations regarding my situation, so here goes: My current tower build is with 6 * 3TB drives (1 parity and 5 data) running on unRAID 5.0-RC5 with a plus license, so I am at the max in both number of array drives I can use and also SATA ports on my MoBo (only 6). Now I am planning on adding a 2TB cache drive (been very sparingly used in an HTPC) with a PCI-e 2 Port SATA card, so: 1) I read somewhere that the cache and parity drives must be connected to MoBo SATA ports directly and not to the addon cards - is that true? 2) If it is true then I would unplug a array drive from the MoBo and connect the cache drive to the MoBo port and then plug in the array drive to the PCI-e card. The drive I'm planning on unplugging and reconnecting is an empty drive in the array, it has not been used yet. Here is what I am planning on: Power-down the server. Add the SATA port card and the drive. Unplug the empty drive from the M/B and connect it to the SATA port on the add on card. Connect the cache drive to the M/B. Power-up and select the cache drive on the main page of the Web GUI. Enable cache in the user shares that I want. That's it and I'm done. Is this right? 3) Question about powering up the server - my array starts automatically when I power up the server (reboot), is this a setting I can change? Where can I change it from? 4) Should I pre-clear the cache drive? If I don't would it take a long time to enable it? 5) Would switching SATA ports for an existing array drive cause the drive from being not recognized immediately by the array? Would I have to run a parity check after doing this? Just to confirm I am running the drives inside the case and not using the hot-swap bays or drive cages. That is all for now. Thanks for all your help in advance. Thanks - Abhi
July 27, 201213 yr Hi, My apologies if these has been asked before somewhere and I missed it. I have read a lot of good posts/questions/answers written by many of you here about the cache drive and the mover script and how it works, but I still had a few specific questions/needed confirmations regarding my situation, so here goes: My current tower build is with 6 * 3TB drives (1 parity and 5 data) running on unRAID 5.0-RC5 with a plus license, so I am at the max in both number of array drives I can use and also SATA ports on my MoBo (only 6). Now I am planning on adding a 2TB cache drive (been very sparingly used in an HTPC) with a PCI-e 2 Port SATA card, so: 1) I read somewhere that the cache and parity drives must be connected to MoBo SATA ports directly and not to the addon cards - is that true? No it is not. Though you could expect the motherboard connectors to be your fastests ones, since cache and parity get a lot of use it would be wise to have them on your fastest ports. But the unraid system will work without a problem with those drives on expansion cards. 2) If it is true then I would unplug a array drive from the MoBo and connect the cache drive to the MoBo port and then plug in the array drive to the PCI-e card. The drive I'm planning on unplugging and reconnecting is an empty drive in the array, it has not been used yet. Here is what I am planning on: Power-down the server. Add the SATA port card and the drive. Unplug the empty drive from the M/B and connect it to the SATA port on the add on card. Connect the cache drive to the M/B. Power-up and select the cache drive on the main page of the Web GUI. Enable cache in the user shares that I want. That's it and I'm done. Is this right? If you are running Unraid V5 then you can just stop the array, power down the server and change your SATA cabling, unraid will figure out at what location your drives are by itself (though personally I would just note down for myself what I change to be extra safe) 3) Question about powering up the server - my array starts automatically when I power up the server (reboot), is this a setting I can change? Where can I change it from? Yes this is a setting, it is in the "disk settings" under "settings"and is called "enable auto start" 4) Should I pre-clear the cache drive? If I don't would it take a long time to enable it? Preclearing is not necessary for the system to work (if you do not do it then unraid will do a limited version of it by itself, during that time your array will not be up). It is however a VERY wise idea to preclear any drive you add to the system and give it 3 preclear cycles: Multiple pre-clearing cycles are good, 3 is a good number. They will however take a lot of time. Note that if you start preclear by telnetting into the server from your pc the preclearing is dependent on your pc continuing to work (a reboot of your windows box will stop the preclear, this can be prevented by using "SCREEN" (it will make sure the preclear will continue even with your windows box shut down) The following commands will have you covered on both (3 cycles with screen and sending reports on progress by email): cd /boot screen ./preclear_disk.sh -M 3 -c 3 /dev/sd? 5) Would switching SATA ports for an existing array drive cause the drive from being not recognized immediately by the array? Would I have to run a parity check after doing this? Just to confirm I am running the drives inside the case and not using the hot-swap bays or drive cages. No on both cases.. On Unraid V5 the system takes care of this by itself. That is all for now. Thanks for all your help in advance. Thanks - Abhi
July 27, 201213 yr Hi, My apologies if these has been asked before somewhere and I missed it. I have read a lot of good posts/questions/answers written by many of you here about the cache drive and the mover script and how it works, but I still had a few specific questions/needed confirmations regarding my situation, so here goes: My current tower build is with 6 * 3TB drives (1 parity and 5 data) running on unRAID 5.0-RC5 with a plus license, so I am at the max in both number of array drives I can use and also SATA ports on my MoBo (only 6). Now I am planning on adding a 2TB cache drive (been very sparingly used in an HTPC) with a PCI-e 2 Port SATA card, so: 1) I read somewhere that the cache and parity drives must be connected to MoBo SATA ports directly and not to the addon cards - is that true? No, not true. 3) Question about powering up the server - my array starts automatically when I power up the server (reboot), is this a setting I can change? Where can I change it from? Depends on the version of unRAID. It is in the unRAID settings in the current 5.0 beta release. 4) Should I pre-clear the cache drive?Only if you care about your data. Otherwise, the first time you'll learn of disk issues is when you access your files after copying them to the array. If I don't would it take a long time to enable it?The "cache" drive is enabled/disabled in seconds. You just have to stop the array, assign it, and then start the array. (I think you'll then get a format button, but it might do that on its own... I really don't remember) 5) Would switching SATA ports for an existing array drive cause the drive from being not recognized immediately by the array?Depends on the version of unRAID. Current "rc" and latter"beta" releases use disk model/serial number to figure out which port a drive is attached to. Older releases will need YOU to use the disk assignment page to re-assign the disk to its appropriate slot in the array. since you are on a newer "rc5" release, unRAID will figure it out regardless of which port a disk is connected to. Would I have to run a parity check after doing this?[/quot]No. That is all for now. Thanks for all your help in advance. Thanks - Abhi You are welcome.
July 27, 201213 yr Author Thank you both...! I have added it on, and started pre-clear yesterday night before your replies and the array drive is now connected to the expansion card and the cache drive to the MoBo. I am currently running pre-clear on the disk since yesterday night - it should be almost done by now, did not get a chance to check it before I left for work today. @ Helmonder - thanks for this info, did not know that till now: Note that if you start preclear by telnetting into the server from your pc the preclearing is dependent on your pc continuing to work (a reboot of your windows box will stop the preclear, this can be prevented by using "SCREEN" (it will make sure the preclear will continue even with your windows box shut down) The following commands will have you covered on both (3 cycles with screen and sending reports on progress by email): cd /boot screen ./preclear_disk.sh -M 3 -c 3 /dev/sd? Though I started the pre-clear before your reply, will keep this in mind for the next time I add a drive. I am telnetting into the server to run pre-clear, but not using screen, hopefully my windows machine will not shutdown or crash. @Joe L - I am using the "-A" option to run pre-clear on all my drives is that well advised, this drive as NTFS formatted as it was in a windows machine prior to this would that make a difference. This is the command I used: cd /boot ./preclear_disk.sh -A /dev/sdf My array is started without the cache disk, while the pre-clear is running and as you guys said unRAID did identify the disk that was plugged into a different slot and added it on the right location. Only one question remains now, I did not see an option to enable cache in the user shares now, would that appear by itself after the cache drive is enabled and array is restarted? Thank You Again!
July 27, 201213 yr For the last question: Yes ;-) As soon as you add a cache drive (assign it at the bottom of the drive list with an array that has been stopped). You will be able to use/not use it per share.
July 27, 201213 yr Author Thank you! That probably seals all the questions I had, will check once I get back home and report again! @Helmonder - Unrelated question - noticed you had a 3TB WD Red in your mix, how is that drive working for you. I might be buying this in the near future if I decide to expand my array - I read great reviews about the WD Reds, IMO the TLER feature is great to have without a lot of other features that enterprise drives have but is unnecessary in the SOHO environment and the price difference is bearable. My problem is the speed - Intellipower, in other words 5xxx RPM. How is that working for you? The question is open for anyone else who have had experiences with the REDs...!
July 28, 201213 yr I will let you know, the drive is brandnew and just finished its first preclear cycle: ========================================================================1.13 == == Disk /dev/sda has successfully finished a preclear cycle == == Finished Cycle 1 of 3 cycles == == Using read block size = 8,225,280 Bytes == Last Cycle's Pre Read Time : 8:43:23 (95 MB/s) == Last Cycle's Zeroing time : 7:26:57 (111 MB/s) == Last Cycle's Post Read Time : 18:36:03 (44 MB/s) == Last Cycle's Total Time : 34:47:25 == == Total Elapsed Time 34:47:25 == == Disk Start Temperature: 33C == == Current Disk Temperature: 39C, == == Starting next cycle == ========================================================================1.13 Sent from my iPad using Tapatalk HD
July 30, 201213 yr Preclear just finished and I am now rebuilding my drive: == invoked as: ./preclear_disk.sh -M 3 -c 3 /dev/sda == WDC WD30EFRX-68AX9N0 WD-WMC1T0076253 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:43:23 (95 MB/s) == Last Cycle's Zeroing time : 7:26:44 (111 MB/s) == Last Cycle's Post Read Time : 18:56:37 (43 MB/s) == Last Cycle's Total Time : 26:24:22 == == Total Elapsed Time 87:24:08 == == Disk Start Temperature: 33C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 114 117 0 ok 36 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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. ============================================================================ All looks fine ! Rebuild is currently running at 26 MB/sec ..
Archived
This topic is now archived and is closed to further replies.