aiden

+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.

Yes, it would continue to operate as-is. The problem comes from the advancements and changes made to hardware over time. The 2.2TB issue is a prime example.

Having the foresight to put the code into escrow is absolutely better than nothing.

Yes, but software escrows do not house the experience and knowledge gained during product development. They usually only hold the last snapshot of development, and without historical context, future developers can end up running backwards to rediscover why older solutions were abandoned in favor of the current methods. Cross-training within a development team is much more robust against this kind of knowledge loss.

And not to add a morbid tone to this discussion, but I'm sure many of us are keenly sensitive to the idea of a single developer project that loses its developer.

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.

The Kingwin I used didn't have any way to make such adjustments. Oh well.

In my build I could never get the hot swap bay to seat snugly in the ODD because the mounting mechanism is squirrelly. Did you have any problems?

I can confirm the package.conf file works perfectly for installing handbrake. I installed it, set it for reinstall on reboot, and rebooted, and it came up as installed with the correct checksum. As far as confirming handbrake works, I don't know that yet.

Basically because not enough people have confirmed that it works as desired and that is a good candidate to be included as currently defined. Have you used the package.conf file? Did it work as expected? Does it need any changes/improvements? Joe L. No, I have not. I was about to embark on an experiment since I have not used handbrake before, and thought I would check its level of integration with the package manager before I installed it manually.

Hm... why is this not in the list of packages within unMENU?

Wouldn't something like a Memtest approach be more appropriate for SSDs?

Very nice and clean. I dig your project link too. What SATA cables are you using?

Hm... TB maybe? LOVE the look of that case. That all drive look is very sexy.

You can't read anything into the RAW values at the end of the lines. What you want to see is any changes in the initial 2 values versus the final two values for a given parameter. In this case, it looks like your drive is fine. 252 basically means "virgin" drive, 100 usually means initialized. Btw, this really should be posted in the results thread.

Yes, my unraid was on the same system and was up during the preclear cycles. In fact, I was writing over 100 GB of data to the array at one point, and only using the onboard SATA ports for all of it. This is all on a D510 Atom system. I would venture a guess that processor speed has little to do with preclearing the drive, and that it is most likely RAM and bus related.