tr0910

Re number of files per directory. Most of mine would be less than a thousand. But who can guarantee there isn't a stupid folder somewhere with 10000 tiny files. It would be interesting to run some statistics on our unRaid servers to see what those numbers really are.

Quick throw away the iPhone, and it will be good again. The Apple Gods are trying to trick you into buying a macbook. Given the complexity of today's technology, it's amazing anything works.

No. Raptor's used to be fast but compared to ssd they are slow. Doubt you could tell the difference.

Yes I do. We need to host it somewhere permanently. I'm away from my unRaid boxes at the moment. Hope someone else has it.

The reason the middle screws are missing is because with 6 platters there wasn't room for them. You would be drilling into the platters. (No guarantee how that would turn out.)

6 platter design with 1tb platters. Note the reviews bemoaning the missing middle screw holes for mounting.

Mine are all connected to the 3 - mv8 cards. Didn't even realize there was on board sata ports. That might be your issue.

I have Intel and amd 24 bay Tam boxes used lightly in a backup capacity. One has 9 drives one 10. I'm getting 100mbit parity checks on both. If dynamix is running on one I get way slower parity on that one. Not sure why you are seeing slow performance.

There is a known issue with Win7 and the explorer ribbon of death, where directory listing randomly take a long time to come up. What version of unRaid / osx?

I have an Asus board that changes the boot order any time anything changes. It's a Royal pain. Solution: Change the motherboard. Sent from my Nexus 5 using Tapatalk

unmenu crashplan apc-ups / powerdown

I am still using the same one that he compiled for me. It's working fine with latest v5, but I've not tested it with v6. I'm not where I can access it right now, but PM me next week and I should have it.

Gary I'm sure you are right, but we need to define what hot means. In this forum "hot" is thrown around quite loosely. Some drives run hot at the best of times, and this is normal. Other drives normally run cool. It's only if you have some data to support abnormal temperature's that I would worry, and the first thing I would look for is fans seized up. Sent from my Nexus 5 using Tapatalk

And I did the 2nd 750gb that failed to preclear. It too works... Output for Joe L below. root@TowerXen:/boot# dd if=/dev/sdc count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0255745 s, 3.9 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdc Disk /dev/sdc: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1465149167 732574552 0 Empty root@TowerXen:/boot#

Just re-ran the script on one of the 750's that failed before using your "LC_CTYPE=C preclear_disk.sh /dev/sdX" . I now get a successful response from the -t option and the output JoeL asked for is below. (using v6b4 and latest 1.14 preclear) root@TowerXen:/boot# dd if=/dev/sdd count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0254061 s, 3.9 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdd Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 64 1465149167 732574552 0 Empty root@TowerXen:/boot#

Hmmm. Interesting. Wonder why its only an issue sometimes? My 1tb drive worked but my 2 750gb ones didn't. Sent from my Nexus 7 using Tapatalk

Here is the output from 3 disks, none of which have been touched since preclearing : ******* First the drive that precleared fine a 1tb ******** root@TowerXen:/boot# dd if=/dev/sda count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0187064 s, 5.3 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 / e p t \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sda Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 1953523054 976761495+ 0 Empty ******* Second the drive that didn't preclear a 750tb ******** * (This drive is selected as disk1, but hasn't been formatted yet) * root@TowerXen:/boot# dd if=/dev/sdc count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 11.2735 s, 8.9 kB/s * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdc Disk /dev/sdc: 750.2 GB, 750156374016 bytes 1 heads, 63 sectors/track, 23256336 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1465149167 732574552 83 Linux root@TowerXen:/boot# ******* Third the drive that didn't preclear a 750tb ******** root@TowerXen:/boot# dd if=/dev/sdd count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0189313 s, 5.3 MB/s * 0000448 \0 \0 \0 \0 \0 \0 ? \0 \0 \0 302 261 f T \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdd Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty root@TowerXen:/boot#

That would make sense and lower my concern, but it doesn't explain why the image shows that unRaid thinks the other 2 were precleared successfully. This is contrary to what the -t test shows for one of these 2 drives. Now why one was successful and the other 2 weren't is the final puzzle. I haven't even formatted disk1 yet just in case somebody needs more info about the current state of these drives.

So I did another preclear pass with 1.14 on R6b4 with Xen loaded just as it was 2 days ago when I last did these 3 drives. The results this time are as follows: (last time I ran it, one of the 750's precleared successfully and was added without delay and the GUI screen showed that the other drives had also precleared successfully. This must be new to R6?? ) 750 GB is not precleared (precleared with the -W flag) 750 GB is not precleared (precleared with the -W flag) 1 TB is precleared (precleared with the -n flag) Results of the -t test screen below.... But look at this first??? For the first drive unRaid is going to add it without clearing it??? root@TowerXen:/boot# preclear_disk.sh -t /dev/sda Pre-Clear unRAID Disk /dev/sda ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721010KLA330 Serial Number: GTF000PBH2VZHF LU WWN Device Id: 5 000cca 21ecf658a Firmware Version: GKAOAB0A User Capacity: 1,000,203,804,160 bytes [1.00 TB] Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 1953523054 976761495+ 0 Empty ######################################################################## ========================================================================1.14 == == DISK /dev/sda IS PRECLEARED with a starting sector of 64 == ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdd Pre-Clear unRAID Disk /dev/sdd ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGB6EF LU WWN Device Id: 5 000cca 215c68744 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdd is NOT precleared == 63 1416016322 1465149105 ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdc Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGGMXF LU WWN Device Id: 5 000cca 215c69429 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdc: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1416016129 708008033 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdc is NOT precleared == 64 1416016066 1465149104 ============================================================================

Guess I spoke too soon. The first of the 3 drives was added to the array as disk1 without delay. Yesterday second drive was added as parity and it kicked off a parity check??? It's been so long that I've added a precleared parity disk that I don't remember if this is expected behavior. Just now, however adding the 3rd disk as disk2 resulted in it wanting to clear the disk again. I guess this is what you are referring to?? Its only been 12 hours since the batch were all precleared, and disk2 was never touched otherwise. I then precleared disk2 again with v1.14 and it still wasn't precleared when checked with a -t option with preclear_disk.sh v1.14 ? ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGB6EF LU WWN Device Id: 5 000cca 215c68744 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdd is NOT precleared == 63 1416016322 1465149105 ============================================================================

Just precleared 3 older 750 and 1tb drives to create an v6 test bed. Using 1.13 on v6b4, all 3 got the correct preclear signature. Not sure what you guys are seeing??? Sent from my Nexus 7 using Tapatalk

Will this port to Android too at some point? Sent from my Nexus 7 using Tapatalk

Since both servers are hooked up to the same router, normal mounts are possible too. Never played with sshfs before. Are there other reasons to look at it? Sent from my mobile

Now this script won't be running on the backup server just the main server. Is there even any way to access another servers ( the backup servers ) syslog. Is there a way to tell another server (the backup server) to launch a script on it? Then they would need to pass results back and forth. Stuck on this one... Sent from my mobile

I have an unRaid server that uses IPMI to wake another backup server and start an rsync backup to it. At present I only check that it is live by pinging its IP address, but need a much more comprehensive test of its readiness to accept an rsync backup. These questions could be such as: 1. Hey BACKUP server, Are you awake? 2. Is your array started? 3. Are you doing a parity sync? (important because I kill the backup server once the rsync is complete) 4. Is there enough room on all disks to do the backup? 5. Are there any errors in your syslog? 6. Do you feel like doing a lot of really boring and painful work right now.... Now I could start hacking away and building some of the above with my very limited bash level scripting skills. But I would hate to develop something that has already been invented. Has anybody got a code base that does some of the above? ****** Here is code to - Check to see if Backup Server has come to life ******** HOSTS="192.168.1.85" for myHost in $HOSTS do ping -c 1 "$myHost" > /dev/null if [ "$?" -eq 0 ] ; then echo "Hosts up" else echo "Host down 192.168.1.85" fi done