• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
SJ_UnderWater

Moving To A 2-Drive Dell Optiplex Gx755 Usff

2 posts in this topic

So, after getting really tired of my custom mini-ITX Atom WHS with its horribly loud fans that required auto-shutoff and auto-on for quiet, I seized on a gearxs.com deal for Core2 Duo GX755's ultra-small form factor at $139. It took me quite a while to get it working (a day), but it turned out to be mostly Dell stupidity and a couple issues I hadn't realized.

My old WHS had two drives, one 3.5" and one 2.5" (with the system partition, don't ask). With the new-ish Optiplex (which technically has only one SATA port), I was able to fit in both drives by using a D-type Modular Bay enclosure for SATA drives (this part I had figured out in advance, and both items arrived about the same time). So the idea was to put the secondary (3.5") drive in place of the 80GB the GX755 shipped with, and to take the cheap optical drive out of the modular bay and replace it with the 2.5" drive, while also taking the 1GB RAM from the old machine and putting it alongside the 1GB already in the GX755. The enclosure I got was partially corroded (!!), but managed to canabalize parts from the optical drive.

The facts: Dell missed several drivers though I searched by service tag, ATA/Legacy mode only allows booting from the primary/3.5" drive, and in AHCI mode it booted very slowly, suggesting some kind of SATA conflict, possibly caused by the SATA/IDE bridge in the bay enclosure. I managed to track down the Gigabit, video, Intel AMT SOL and HECI drivers, and finally got the most up-to-date SATA Controller driver directly from Intel, but AHCI still wouldnt boot successfully with both drives attached.

I have hopes that I will get AHCI to work, and at least the AHCI controller driver itself is in place if I need it. If anyone is curious, you can force an AHCI driver to install on an existing operating system by selecting the existing controller and "updating" the driver to AHCI by picking the specific INF file provided, just ok any warnings. Reboot immediately and Windows will use the right driver, preventing a blue screen.

The only issue left is that the BIOS won't let me choose the modular bay as the primary drive in ATA or Legacy mode, which means that I had to unhook the primary drive, wait for the error, then reattach it while the BIOS switched to the bay.

Does anyone know a relatively safe way to make a WHS's secondary drives bootable? If I can place a boot folder and use bootsect on the second drive, then I should be ok: the 3.5" will take control from the BIOS, then simply pass it on to the 2.5" drive with the system partition on it. Otherwise I'll buy one of those low-profile flash drives, put the boot files there, then configure it to pass boot to the 2.5" drive. I'd rather have a self-contained solution, but if it will keep me from opening the case every time I boot, I'll spend the $5.

Thanks in advance for any suggestions!

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

so after much aggravation trying to get NTLDR to operate off of a flash drive, I found a very simple solution which works very well: syslinux. Basically, after downloading syslinux.exe, and running "syslinux -m -a <drive>:", I create a simple configuration file, syslinux.cfg, and copied the chainloader module, chain.c32 on to the drive. The configuration is:


DEFAULT WindowsHomeServer

LABEL WindowsHomeServer

SAY Loading Windows Home Server...

COM32 chain.c32

APPEND hd2 swap

Now I'm just looking for a cheap low-profile flash drive

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I am running WSE2012 R2 and I only ever see red, yellow or green. I have never seen blue even when backing up. I can't explain what could be happening here, but maybe some feedback from other users may help us pin it down. What OS are your client PC's? Mine are all Win 10. Not sure if that may have a bearing.   
    • I made the leap from WHSv1 to WSE2012R2.  I like the new system but one thing seems to be missing.  In WHS v1, the tray icon would change colors to indicate various things blue - backing up now green - everything is healthy yellow - warnings detected (e.g. haven't backed up in a while) red - critical issues (e.g. recent backup failed) In WSE 2012 R2, however, I only get the blue and green indicators, even when there are critical errors on my home network.  For example, a server hard drive had failed for several weeks, but the connector icon in my system tray remained green.  I only discovered the issue when I happened to login to the dashboard for something else. Does anyone know if this feature has been removed in the latest WSE versions?  Or have I just mis-configured something?
    • I am building a new home server: I really want to use StableBit DrivePool and Scanner - am used to them and like the relative ease of use. Hardware = PC running Windows 7 Pro has SSD for OS and 5 additional 2TB HDDs + SansDigital Towerraid (model TR5M6G) connected by eSATA controller (pCie) with 5 2TB HDDs of varying age (2 brand new WD Red and the remaining 3 a combo of Hiatachi and Seagate of varying age - all test out fine for now). Towerraid is currently configured as JBOD, so I can't really see individual drives, and neither does StableBit drive pool - so I get a pool consisting 5 1.82 TB drives (the ones on the PC) and 1 giant 9.1TB drive. I have about 10 TB of data ready to go into this new build.  Will be adding more over time.  Not sure when but certain I'll have HDDs go bad on me, of course. My question(s): 1)  Is there a RAID configuration that will let StableBit do its thing watching individual drives and letting me identify sick drives that need to be removed/replaced?                           2)  If I decide to give up the RAID and just let DrivePool handle duplication, how do I configure the SansDig?                           3)  Am I just getting it all wrong from the get-go? Would appreciate any advice - thanks   
    • I have almost 10 TB in the storage pool so I was not surprised when my first server backup took a very long time (22 hrs.).  Lately the incremental server backups have been fast (15 - 18 min.)  Two days ago the server apparently initiated a full backup that failed twice but completed successfully this morning after about 23 hours.  An hour later the regular daily backup is back to a normal incremental backup times (18 min.) So why did the previous backup take so long, as long as a full backup would take? Does the server occasionally make a fresh start with a full backup to reduce the time a full incremental recovery takes?  (fewer increments, less processing time) I don't see a setting in the server backup options for specifying a number of increments between full backups, for example.    
    • I just posted a similar question elsewhere.  By Shadow Copies are you referring to the Windows 10 File History backups that periodically use shadow copy to backup open files? I too discovered that a huge amount of backup space was consumed by File History backups, no doubt because I was moving some large Blu-Ray files around.  That I fixed by moving the temporary and final file folders to the server, where they are backed up as part of the daily server backup.  That too, of course, uses Shadow Copies but that is another story. Has anyone done the math?  What is the equivalence .. or lack thereof ... between the traditional WS2012r2 (WHS v1 et al.) daily incremental backup :: and a Win7 System Image backup + File History backups? Restore time comparison? Which do you feel is best?
  • Popular Contributors