aiden

All the logs look like this... Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory

Hello, I am trying to preclear 4 new 16TB Seagate EXOS x16 drives. The read speeds averaged 100 MB/s, but the write speed is a horrible 6 MB/s. I have verified that write-caching is enabled for all drives. Ideas?

I find myself in the position of needing to upgrade my hardware to a new chassis. I have been looking hard at 45 Drives, but they are spendy. I've always loved the look of the XServe design, and it's possible to purchase SEVERAL of them for the price of one empty Storinator case. I realize that it would take 10U (3 XServe RAIDS + 1 XServe) to equal the capacity of a 4U Storinator. But the aesthetics are are a different story. I notice cooling is a concern, but that seems to depend on fan placement and channeling. But my question is, is it worth spending the time + money to buy some of these old girls and rip her guts out? Do all the status indicators still work for those of you who have embarked on this journey? Any other gotchas I should consider? Thanks!

Yes, a few of us contributed to a script over the years. Started with Starcat, then me, then dstroot, then Guzzi. Don't know where that falls in line with this one, time wise. Thread is here, and in my signature.

Out of all of my pics, I really didn't want you to use the inside pic of my build. It's so sloppy. I just posted that to answer Peter's question about why I put the enclosures "upside down". I would much prefer you use the first pic I posted.

Errr... aren't those drive cages upside down? The drives don't care. Also, I needed the fans in the rear to be up above the motherboard after I added a shroud increasing the size of the fans from 70 to 80mm, so this was the only solution that worked geometrically. It has the added benefit of keeping the exhaust air from the drives above the motherboard and CPU, and inline with the exhaust fan in the case.

Since the inside of my server isn't gorgeous, I elected to use only outside pics:

Well, first of all, CONGRATULATIONS! Those little bundles of joy really change your life and your perspective. I don't have the experience to compile it from scratch, so I hobbled together what I could get from the internet. I used one of Alien's packages, and sourced the other dependencies through tracing errors. But it does work on 5.0 rc3. I used the following code to get it working. I know I could build a .plg file and dump it in the extra directory, but I just haven't taken the time to do it. Plus, since this version still doesn't do what I need, I'm not finished yet. wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/patches/packages/freetype-2.4.8-i486-1_slack13.1.txz wget http://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-13.1/slackware/x/fontconfig-2.8.0-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libogg-1.1.4-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libsamplerate-0.1.7-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libtheora-1.1.1-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libvorbis-1.2.3-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/l/zlib-1.2.5-i486-4.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/glib-1.2.10-i486-3.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/d/gcc-g++-4.5.2-i486-2.txz wget http://www.slackware.com/~alien/slackbuilds/handbrake/pkg/13.37/handbrake-0.9.6-i486-1alien.tgz upgradepkg --install-new freetype-2.4.8-i486-1_slack13.1.txz upgradepkg --install-new fontconfig-2.8.0-i486-1.txz upgradepkg --install-new libogg-1.1.4-i486-1.txz upgradepkg --install-new libsamplerate-0.1.7-i486-1.txz upgradepkg --install-new libtheora-1.1.1-i486-1.txz upgradepkg --install-new libvorbis-1.2.3-i486-1.txz upgradepkg --install-new zlib-1.2.5-i486-4.txz upgradepkg --install-new glib-1.2.10-i486-3.txz upgradepkg --install-new gcc-g++-4.5.2-i486-2.txz upgradepkg --install-new handbrake-0.9.6-i486-1alien.tgz

Through a lot of trial and error I do have HandBrakeCLI 0.9.6 running. However, I discovered that ripping PGS subtitles from Blu-Ray sources doesn't work unless running one of the recent nightly builds.

I know this is an old thread, but I was curious if anyone had compiled the newest HandbrakeCLI 0.9.6 for unRAID? If not, I could try to compile it myself following the directions in the beginning of this thread, unless one of the Linux gurus has a different approach. I'm having trouble with 0.9.5 not reading embedded subtitles in mounted blu-ray .iso files, and thought 0.9.6 might fix the issue. EDIT: Well, I just realized I would need another machine to use as a build platform, and I don't have access to such resources. Is there anyone who has a 5.x series build environment running to compile unRAID packages?

I have used 1.12 to preclear 5 3TB drives and have had no problems. Is it safe to assume that even if 1.12 was not correct, that unRAID properly formatted the drives anyway? Not sure - but it may have just been fixing this ... http://lime-technology.com/forum/index.php?topic=4068.msg140029#msg140029 Yeah I read that post, but wasn't sure if it was the same issue. I encountered the same error with -t, but assumed it was just a glitch since I had just finished preclearing.

So I think I've looked everywhere for a more thorough explanation, but I can't seem to find it. What does version 1.13 fix about the GPT partitions? The notes just say... I have used 1.12 to preclear 5 3TB drives and have had no problems. Is it safe to assume that even if 1.12 was not correct, that unRAID properly formatted the drives anyway?

So, what was the verdict on this? What did your drive temps look like?

!!! +!

+1 It is configurable within the BIOS if you want to change it to something less insecure. Resources for IPMI can be found here, and the Username/Password information can be found in section 2-6 on page 16 under Note 2 of the IPMI manual.

The trick would be the MIR would have to go through a UK proxy. I would imagine shipping a group of them in some kind of bulk shipment would help eliminate some of the cost. Maybe save $75 - $100 after it's all said and done?

This is huge, and makes me wish I had built one for myself when I built my dad's.

So after hours of trying to figure this out, it (of course) came down to a very simple thing. I was submitting a series of commands as a cut and paste operation: /boot/scripts/preclear_disk.sh -a -c 3 -M 2 /dev/sdb diff /tmp/smart_start_sdb /tmp/smart_finish_sdb Since preclear is looking for user input ('Yes' or anything except), the second stacked command diff /tmp/smart_start_sdb /tmp/smart_finish_sdb was screwing up the input, and of course it simply aborted since the input was not Yes but rather diff /tmp/smart_start_sdb /tmp/smart_finish_sdbYes. As usual, the simple stuff kills your time, frustrates you during debugging, and then embarrasses you when you figure out the problem.

I thought it was something simple like that too, so I tried it several times, making extra sure there was nothing being input other than the "Yes". I wish it was something as exotic as that, but no, it's a standard keyboard. I am using Screen to do this, just like have for dozens of drives before with no issue. I should note this happened in 1.8 first, then I updated to 1.9 to make sure I was current and it still failed.

Okay, I'm not new to preclearing, but this has me baffled. I have a 160GB drive connected to an AOC-SASLP-MV8, and according to ls -l /dev/disk/by-id it is detected as /dev/sdb: total 0 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTA8UP -> ../../sdd lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTA8UP-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTD4TP -> ../../sdh lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTD4TP-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTLNUP -> ../../sdf lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1170YAHTLNUP-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1171YAGZ131S -> ../../sdg lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1171YAGZ131S-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1171YAH3SVTS -> ../../sde lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK1171YAH3SVTS-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK11A8B9J6TV8F -> ../../sdi lrwxrwxrwx 1 root root 10 2011-04-06 23:43 ata-Hitachi_HDS722020ALA330_JK11A8B9J6TV8F-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 ata-VB0160EAVEQ_9VY9SWE3 -> ../../sdb lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTA8UP -> ../../sdd lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTA8UP-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTD4TP -> ../../sdh lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTD4TP-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTLNUP -> ../../sdf lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1170YAHTLNUP-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1171YAGZ131S -> ../../sdg lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1171YAGZ131S-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1171YAH3SVTS -> ../../sde lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK1171YAH3SVTS-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK11A8B9J6TV8F -> ../../sdi lrwxrwxrwx 1 root root 10 2011-04-06 23:43 scsi-SATA_Hitachi_HDS7220_JK11A8B9J6TV8F-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-04-06 23:43 scsi-SATA_VB0160EAVEQ_9VY9SWE3 -> ../../sdb However, I can't get past this "Clearing will NOT be performed" error: Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.9 Device Model: VB0160EAVEQ Serial Number: 9VY9SWE3 Firmware Version: HPG0 User Capacity: 160,041,885,696 bytes Disk /dev/sdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table ######################################################################## invoked as /boot/scripts/preclear_disk.sh -a -c 3 -M 2 /dev/sdb ######################################################################## (-a option elected, partition will start on sector 63) (it will not be 4k-aligned) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes Clearing will NOT be performed Using unRAID 4.7 and preclear 1.9.

http://www.newegg.com/Product/Product.aspx?Item=N82E16859105954&cm_re=microserver-_-59-105-954-_-Product

This is the thread that started it all. Lots of good info there as well.

It really is one of the sexiest OEM designs I've seen for this niche.

I can confirm a Lexar FireFly fits perfectly in there. Regardless, the point is that the USB port works as advertised for booting unRAID.

Huh? unRAID can only be installed on a USB flash drive, and yes, it's on the internal USB port. Maybe he just can't see it in the picture. I too used a USB flash drive and stuck it directly on the board. That's one of the great features of this pre-fab rig.