taflemer

Drive might still be usable - sometimes you get lucky and the bad sectors don't breed, and if so chkdsk /r will at least mark those sectors to not be used by the file system - but if you don't want the risk that you'll end up with more and more bad sectors then yeah wipe and bin/rma the drive.

....  I'm not 100% sure of this ... but given what I'm seeing, I think your system is corrupted.
 
I'm seeing a bunch of .NET related errors.   Some that affect remote functionality, as well as other ... low level .NET stuff.  
 
Unfortunately, depending on what OS you're running ... it may be simpler to reinstall than to repair .NET Framework, because of how integrated it is into the system.  
 
 
 
As for resetting StableBit Scanner, there is no way to do so from within the UI. It's entirely manual.
http://wiki.covecube.com/StableBit_Scanner_Q4200749

Well, the UI just connects to the service. So if that isn't running ... yeah.
 
That said, the service should automatically restart if it crashes.
 
 
And I'm not seeing Troubleshooter logs.  If you could, try sending them again (use "3013" for the contact request/ID field).
 
Also, as above, try resetting the settings.
 
 
If that doesn't help, try uninstalling and reinstalling the software and see if that helps.

If you remove the old disk via DrivePool, it moves out all of the pooled files as part of the removal process.  
 
There isn't anything else you need to do other than removing the disk and re-adding it.
The software will take care of everything else.
 
 
 
That said, if everything on the disk is duplicated data... you can use the "Duplicate data later" option. This skips the duplicated data, leaving it on the disk. It then runs a duplication pass after the disk is removed, reduplicating the data, as needed. 
 
Also, if the disk is bad, the "Force Damaged Disk Removal" option may be a good idea. Normally, the removal process stops when it runs into an error.  This option skips problem files and continues to remove the disk. 

If this is a new drive and it already has 2 reallocated sectors ... I'd personally go ahead and RMA the drive, as this indicates that there is already an issue with the drive. 
 
 
However, if StableBit Scanner is able to run a full surface scan without any issues, you may be fine.  Worst case, you could see about running "chkdsk /b" on the disk, as this is a very in depth and rigorous test of the drive. If that passes without any issues, you should definitely be fine.

That's very odd.
 
The SHA-1 hash should be "EF287BAE442E906CD7694FE595C920171964F816" and the MD5 hash should be "F406036DA6581D5782979098193EDB6F"
 
You can verify this with stuff such as HashTab: http://implbits.com/products/hashtab/
 
However, chances are that this is an issue with your root certificates. 
You should be able to fix that by doing this:
http://wiki.covecube.com/StableBit_DrivePool_Q6246716

Well, I use a domain, instead of a workgroup, so all of my computers show up as "COMPUTER_NAME.LANDSRAAD.local" (landraad.local being the domain).  So, this depends on the DNS server and/or master browser.  So your router is definitely acting as a DNS server.
 
As for the router stuff, if it's not a combo modem/router, you could replace it (something like pfsense or sophos UTM may be a good idea). 

Well, the "Computer_name.fios-router.local" shouldn't make a difference really.  This is more of a display issue (though you can disable the dns suffixes in the IPv4 config).
 
Aside from that, yeah, it may be issues with the hardware.
 
 
As for he software, yeah, the service runs in the background, even when not logged in. All the UI does is connect to the service (even for remote control, as it's routed though the service, basically). 

Unfortunately, we don't support StableBit DrivePool on Windows Home Server v1, at all. 
 
Specifically, there is no Windows XP or Server 2003 driver for the pool, so it just won't work (assuming that you can get it to install, as the installation should be outright blocked on the OS). 

To be blunt here:
 
This is something that you may need to talk to Verizon about (or whomever makes the router in question), as this is a hardware/firmware related issue on the router, and most likely the wireless stuff. 
 
 
We do allow you to change the multicast settings for the software:
http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
But I don't think this will really help out here, as I believe that we are using the multicast API for .NET Framework. 
 
 
Aside from contacting Verizon, or installing your own wireless AP, the best solution for you is the RemoteControl.xml file. 
However, you could create a single copy, with all the systems in the network, and place this on each system. That should definitely fix the issue.
http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#RemoteControl.xml

Microsoft makes the support lifecycle stuff overly complicated. 
So don't feel bad if it makes you feel confused.
 
https://support.microsoft.com/gp/lifepolicy
 
Specifically, "extended support phase" means that no features are added, and that the product will ONLY receive security updates.
If you get the "Extended Hotfix Support through Premier Support" (paid), you will continue to receive non-security updates.
Additionally, there is no free support.
 
 
What does this mean for us? 
 
Well, for WHSv1, which is based on Server 2003 (not R2):
https://support.microsoft.com/lifecycle/?p1=3198
That you will still receive SECURITY updates until July 14, of this year.
For WHS2011, that is based on Server 2008R2:
https://support.microsoft.com/lifecycle/?p1=14134
 
 
And I can absolutely confirm this, as my WHSv1 VM is still receiving new updates. They're all security updates though.

WHS 2011 actually goes end of support on 4/12/2016, not 2020.
http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=Windows%20Home%20Server
 
Windows Server 2008 R2 has already gone EOS for mainstream, 1/13/2015. I don't think many home users will purchase extended support, it's very expensive.

We don't really have a minimum requirement.
 
Both products are designed to be VERY light on resources, in most every circumstance.
 
Neither product is doing anything that is very CPU or memory intensive in most cases.
The driver for the pool uses only kb of memory IIRC, and we run at a lower priority when possible.
 
The read striping feature leverages the cache for NTFS IIRC, so even that should be lightweight.
In fact, the only feature that I can think of that really uses a lot of resources is the "Network IO Boost", as it prioritizes traffic, and it is off by default.

You should get Security Updates on V1 for a few more months, it's based on server 2003 and Windows Server 2003 support is ending July 14, 2015.  You should be good on Security updates through January 2020 on WHS 2011, it's based on Server 2008.   As far as minimum requirements, most of folks started running it on WHS 2011 on an HP Micro Server N36l,  AMD Athlon II NEO N36L 1.3 GHz, this was dual core proc,  passmark of 809,  it came stock with 2GB's ram, but most upgraded to 4GB min,   I'm still running DP and Scaner on a HP Micorserver N40l, system performance is slow when you RDP, but overall it's still a capable file server. 
 
this made me laugh, a Intel Xeon Processor 3.0 GHz processor from the DL380 G4, has a pass mark of 398, much lower than I expected, the 3.6 has a passmark of 500.  makes the micro server look like a beast.
 
As far as confirmed minimal requirements,  I'll leave that for some one else.
 
Edit,  added "security updates", which is the most important for any server touching the internet.