teamhood

You all were spot on. I used a Molex to SATA power adapter and both drives powered right up! THANK YOU!

I know that the 14TB is shucked (I did it myself), but I don't know about the 10TB. I'm not familiar with the 3rd pin, but I will research to see what I learn. I didn't think it was a power issue as using the same power and sata cable for the working 14TB.

tower-diagnostics-20211202-1946.zipAll - I'm a bit perplexed at this one and I'm at the end of my rope as I can't figure it out. I'm going through a pretty big server upgrade, which began with adding larger hard drives to begin shrinking my array from 25 drives to 10. I upgraded both parities to 14TB and everything was going fine. I began doing some research as I was still on Reiser File system, 8+ year old mobo/cpu, marvel controllers, etc and made the decision to do an upgrade. My plan was to use my HP Micro NL40 and rsync all the data from my current array onto larger drives formatted to XFS, using unraid trial, while planning for new hardware, then migrate the hard drives from the NL40 over to new hardware and be happy that it was done. Something weird has happened with a 14TB drive and a 10TB drive. The 14TB drive was previously my 2nd parity drive, but I needed to use it as a data drive. Once I unassigned that drive from my original array I could not get it pop in the BIOS. I tried to switch it between onboard SATA from the Supermicro cards, but I couldn't get to work. I know the drive isn't bad as I put it into a USB and no issues. I also had a 10TB drive that was part of that system and the same thing happened. I figured this could because of the Supermirco cards, so I ordered the LSI cards, but couldn't get either to work on the new LSI cards. I ended up putting them both into my NL40 and no issues. I chalked it up to a bug, old hardware, who knows. Well, there is something more now going on as all my new hardware came in and I built the new server and these two drives won't be detected by the new motherboard nor the LSI cards. I checked all cables, power supply connectors, etc. I just popped them both back into the NL40 and again, no issues. I'm not sure what to do because this doesn't make sense. Why can't 2 mobo's detect these drives, but my old trusty NL40 has no problem? Anything I could post that might help? Anyone have any idea on what the heck could be happening? Any help would be much appreciated.

I'm setting up my first UniFi AP and Controller. I grabbed the LTS (latest stable) version. Used Bridge mode. Default IP's. I run pfSense as my router/firewall. Anything special I need to do? I'm stuck on adopting the AP. I ssh'd into the AP and reset it, but I can't seem to get it adopt. Any recommendations?

This looks great and is on my to-do list. Following!

Well, I think you're correct about it being 'Mover'd' I have /mnt/cache/apps directory create on my Cache drive. I never used the cache drive before... and I think it's moving all the shares. How do I make my 'apps' share remain on the cache drive and not get moved over via the Mover?

Hey all - I had Subsonic up and working and twice now I get the following error when heading to the loading page: HTTP ERROR: 404 /WEB-INF/jsp/login.jsp RequestURI=/WEB-INF/jsp/login.jsp Powered by Jetty:// Last time I had to remove everything, reboot, reinstall to get it back working. Log: *** Running /etc/my_init.d/config.sh... Current default time zone: 'America/Chicago' Local time is now: Tue May 19 21:32:20 CDT 2015. Universal Time is now: Wed May 20 02:32:20 UTC 2015. *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 29 May 19 21:32:22 unraid syslog-ng[37]: syslog-ng starting up; version='3.5.3' May 19 22:17:01 unraid /USR/SBIN/CRON[182]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 23:17:01 unraid /USR/SBIN/CRON[297]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 00:17:01 unraid /USR/SBIN/CRON[400]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 01:17:01 unraid /USR/SBIN/CRON[509]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 02:17:02 unraid /USR/SBIN/CRON[616]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 03:17:01 unraid /USR/SBIN/CRON[719]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 04:17:01 unraid /USR/SBIN/CRON[823]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 05:17:01 unraid /USR/SBIN/CRON[928]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 06:17:01 unraid /USR/SBIN/CRON[1035]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 20 06:25:01 unraid /USR/SBIN/CRON[1048]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))

The USA want's come rebates just like those guys across the pond. Sheesh...

So will HP hold a firesale on these?? I would pickup quite a few if they donlike the touchpad this weekend...

Question: I've used this script many times and I'm perplexed. I cd /boot preclear_disk.sh -A /dev/sdm, but all it does is bring up this: Why won't this run the preclear script? root@unraid:/boot# preclear_disk.sh -A /dev/sdm Usage: ./preclear_disk.sh [-t] [-n] [-c count] /dev/??? where = hda, hdb, sda, sdb, etc... -n = Do NOT perform preread and postread of entire disk to allow SMART firmware to reallocate bad blocks in the clearing proce -c count = perform count preread/clear/postread cycles where count is a number from 1 through 20 If not specified, default is 1 cycle. For large disks, 1 cyc can take 10 or more hours -t = Test if disk has pre-clear signature. This option may NOT be combined with the -c or -n options. The test does not write the disk. It makes no changes to a disk at all. It only read the first 512 bytes of the disk to verify a pre-clear signatu exists. Note: "-t" does not read the entire disk to verify i it pre-cleared as that could take hours for a large disk. sin the pre-clear-signature is written *after* a disk is entirely filled with zeros, if it exists, we assume the disk is cleare -v = print version of ./preclear_disk.sh -m [email protected] = optional recipient address. If blank an option is used, it will default to default e-mail address of -M 1 = Will send an e-mail message at the end of the final results (default if -m is used, but no other -M option given) -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (i ple cycles are specified) -M 3 = Will send an e-mail same as 2 plus at the start and end of -read, zeroing, post-read -M 4 = Will send an e-mail same as 3 plus also at intervals of 25% during the long tests The -m, -M options requires that a valid working mail command is i d. One version that has worked (bashmail) is affilaited with the unra fy script. There are others that also will work. Any of these need to be configured to work with your mail server. The unraid_notify script will have instructions on how to configure this. See http://lime-technology.com/forum/index.php?top'>http://lime-technology.com/forum/index.php?top .0 for unraid_notify and http://lime-technology.com/forum/index.php?t 61.0 for the mail script. NOTE: The lastest verion of mail has to be arlier versions of the mail script affiliated with unraid_notify do not support the standard mail syntax needed. Unless the -n option is specified the disk will first have its ent set of blocks read, then, the entire disk will be cleared by writi zeros to it. Once that is done the disk will be partitioned with special signature that the unRAID software will recognize when the drive is added to the array. This special signature will allow th unraid software to recognize the disk has been pre-cleared and to an initial "clearing" step while the server remains off-line. The pre-read and post-read phases try their best to exercise the disk in a way to identify a drive prone to early failure. It perf reads of random blocks of data interspersed with reads of sequenti blocks on the disk in turn. This program also uses non-buffered r of the first and last cylinders on the disk, the goal is to perfor those reads in between the others, and to keep the disk head moving much more than if it just read each linear block in turn.

Well I just upgraded to the hacked BIOS and all went well. This is a fantastic little box! I'm using it for the data that I often access and let the big unRAID remain idle more of the time. I love this little guy!

Question for you all. I'm building an array for my buddy and he sent over 8x 2TB WD drives. I was starting to preclear these drives and I was wondering if there is any concern with SCREENing 8x instances of the script? Thoughts?

Thank you, a lot of time and effort has gone into them, and the whole set-up. Only one runs 24/7, the other three are powered as needed for data access or backup schedules. Do you need another Supermicro 933? I have one complete... just in case you wanted to add a 5th! Did you replace all the stock fans? If not that must be one loud rack!

So I bought one... I love this little thing! I added a 2GB RAM module and threw in 2x 2TB drives to start. So what is the esata > sata cable you'll recommend? I haven't hacked the BOIS just yet...

OS at time of building: unRAID 4.7 Final CPU: 1 x 2.8GHZ / 2M Cache XEON CPU – LV Motherboard: X6DHE-XG2 Motherboard RAM: 4GB ECC REG PC3200 DDR2 Memory Case: SuperMicro CSE-933T-R760B 3U Chassis Drive Cage(s): 3x SuperMicro 5-in-3 Power Supply: 3 x HOT PLUG Power Supplies 760W? SATA Expansion Card(s): 2 x 8 Port SATA Controllers AOC-SAT2-MV8 Fans: 4x 120m Cooler Master Blademaster & 2x 80m Cooler Master Blademaster (non-stock) Total # of Drives: 15 Total # of ‘Green’ Drives : 10x WD EARS Total Drive Capacity: 24.5TB Boot (peak): 280 W Idle – drive spun down(avg): 173 W Parity Check(avg): 315 W Light use (avg): 200 W

OS at time of building: unRAID 5.0 beta2 CPU: Intel Celeron E1200 @ 1.6GHz Motherboard: ABIT AB9 Pro RAM: OCZ Platinum 2x 1GB DDR2 PC6400 Case: Cooler Master Stacker Drive Cage(s): 1x SuperMicro 5-in-3, 2x Athena Power 5-in-3 Power Supply: PC Power and Cooling S61EPS 610W SATA Expansion Card(s): 1x SuperMicro AOC-SASLP-MV8 Fans: 1x Cooler Master exhaust fan Total # of Drives: 7 Total # of ‘Green’ Drives : 4x WD Total Drive Capacity: 6.5TB Boot (peak): 135 W Idle – drive spun down(avg): 70 W Parity Check(avg): 124 W Light use (avg): 85 W

Hey all, As I am in the process of specifying new hardware for a 24 drive system and with purchasing my first Kill-a-watt meter, I was hoping that we could all post some figures to get an idea what current hardware/hard drives are producing in terms of power consumption. I want to build the lowest power 24 drive system I can... Yes, 24 drive and low power sounds like an oxymoron, but I don't want my windmill and solar panels to 'blow a fuse' I figured we ought to create an outline like all good threads on this forum use: [b]OS at time of building:[/b] [b]CPU:[/b] [b]Motherboard:[/b] [b]RAM:[/b] [b]Case:[/b] [b]Drive Cage(s):[/b] [b]Power Supply:[/b] [b]SATA Expansion Card(s):[/b] [b]Fans:[/b] [b]Total # of Drives:[/b] [b]Total # of ‘Green’ Drives :[/b] [b]Total Drive Capacity:[/b] [b]Boot (peak):[/b] [b]Idle – drive spun down(avg):[/b] [b]Parity Check(avg):[/b] [b]Light use (avg):[/b]

Excellent blog post! I honestly have ZERO need for this little guy as I have a 15 drive and a 6 drive unRAID server built, but I love how small and little power this bugger uses. I wish we could get a good price on this here in the States...

Raj, Do you always build withe PSU fan upwards? I ran into this issue the other day when I was putting together a new build and the PSU placement was on the bottom of the case. I wasn't sure which way the fan should go....

Question: Here is 1 of my 5 pre-cleared drives that completed. I'm looking through this data and I'm not sure what I should be looking for that would cause concern.... Can anyone help explain what I should be looking for that would cause a concern? How should I paste this so it isn't all fubar??? [pre]=========================================================================== = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 26C, Elapsed Time: 31:59:43 ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 9460 --- > 1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 55767436 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 15 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 331500 64c64 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 66,67c66,67 < 190 Airflow_Temperature_Cel 0x0022 077 072 045 Old_age Always - 23 (Lifetime Min/Max 23/23) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 074 072 045 Old_age Always - 26 (Lifetime Min/Max 23/27) > 195 Hardware_ECC_Recovered 0x001a 052 049 000 Old_age Always 70,73c70,73 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 209895051755530 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1600 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 196228465819690 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4174963960 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1036252430[/pre]

I figure I would join in the fun on my two drives that I cleared! Anything that I should be concerned about with these two drives? ============================================================================ == == Disk /dev/sdj has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 68c68 < 190 Unknown_Attribute 0x0022 078 070 000 Old_age Always - 370540566 --- > 190 Unknown_Attribute 0x0022 076 070 000 Old_age Always - 420872216 75c75 < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 --- > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 ============================================================================ ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 21 --- > 1 Raw_Read_Error_Rate 0x000f 100 099 051 Pre-fail Always - 10 63c63 < 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 21 --- > 13 Read_Soft_Error_Rate 0x000e 100 099 000 Old_age Always - 10 68c68 < 190 Unknown_Attribute 0x0022 078 074 000 Old_age Always - 370540566 --- > 190 Unknown_Attribute 0x0022 075 074 000 Old_age Always - 437649433 75c75 < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 --- > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 ============================================================================