Wan Optimization Support
Technical => Troubleshooting => : Spiffster January 16, 2015, 05:02:19 PM
-
I wrote the wanos boot image from wanos-1.4.1.img using Win32diskimager and everything seemed to go well, but when I boot from the SSD on the RS140 system things seem to initialize until I get the error:
[Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 1
That error just repeats every minute or so, boot never completes and I cannot get into the system
Even got the same error when I used clonezilla to image a VM to SSD.
Any ideas? I would like to run wanos on dedicated hardware vs ESXi + VM. Thanks.
To clarify, the system is a new Lenovo RS140 with an E3-1245 processor with 128GB SSD. (AHCI Mode)
-
Hi,
Edit for the archive: Please use version 2.0.0 which already contains the update
The HP DL320e G8 produces almost identical symptoms and to resolve it AHCI mode is needed with Raid disabled due to the specific HP drivers. Seems your setup is similar.
-
Great! I will give this a try later today and report back. Thanks!
-
OK, I downloaded the two files to the appropriate location using another linux box and the system boots to the login prompt. So thats progress! Strange thing is that I cannot ping any systems on the LAN after running wanos-cfg just as can I do successfully with the VM. Tried both ports and no dice. That may just require more investigation on my part, but this is just where I am stuck now.
For testing I will just load ESXi and run the VM for now. Let me know if I missed anything obvious on the networking. Thanks!
-
Edit for the archive: Please use version 2.0.0 which already contains the update
-
Awesome. Will test this upcoming weekend. Running on ESXi now and the improvement in WAN performance so far is impressive. :)
-
I got bored and went into the office late last night. Your suggested fix works perfectly. I now have a fully functional RS140 wanos box in production! Thanks for your help!
I will say that I dont see a perceivable improvement in performance running without the hypervisor though. I may go back to running this atop of ESXi for the increased utility. Snapshots, Veeam backups, etc.
-
Awesome, great to hear that. Was the 80 Mbps benchtest on the VM running on ESXi?
-
Yes that was on ESXi. I did run the same test without the hypervisor and throughput appeared to be the same. BTW, is there some more standard test I can use to benchmark? This would insure that myself, and others have some kind of similar point of reference when comparing performance for different hardware / configurations.
-
Ok, got it, that's quite impressive. We didn't notice a perceivable difference between running directly on the hardware and ESXi VM in the < 20 Mbps range, but its good to know this seems to hold true at the top end as well.
iperf seems to be a good standard test utility that fits the bill. By default it uses highly compressible data that can skew tests results. With the '-F' option it can be configured to use a specific file:
e.g: Updated: Silesia Corpus (http://wanos.co/docs/docs/frequently-asked-questions/silesia-corpus/)