The next experiment we were going to try was to put in the slow spinners and then open the case up and see what kind of memory is in it, and if its upgradeable.Īnyway the things a pizza box sized useless paperweight to us anyway, so I thought I would share the outcome of our technical experiment.
So there must be some sort of DRM or special lock in or firmware on these Seagate Contellation.2 drives. If you hit some keys in the Putty session you can get it to repeat that line over and over, but it never actually starts the services.
However trying to boot the S170 results in the same thing.
Well I thought it worked great becasue this time it cloned the drives successfully without a single error message. If it can copy anything I figured this would work great. I've had great luck with this bootable HD cloning utility in the past, copying proprietary filesystems from Cable and Satellite DVR's from failing drives or smaller drives to newer larger drives. Next we tried Miray HDClone 4.2 Professional. It never really starts so we decided to try another cloning method. With a serial cable connected we watch as it simply states. We installed them in the proper order in the HD caddies and went to power on the S170. Chugging on we then copied the S170's bottom drive to another Samsung 256 GB Pro SSD. It took about 35 minutes in the doner system we used to do a copy, but we did get some strange errors at the end about the various partition sizes. We first tried the latest Clonezilla boot CD to copy the S170's Seagate Constellation.2 250 GB 7200 RPM spinner over to a Samsung 256 GB Pro SSD. So we shut it down cleanly with the shutdown command and labeled the top hard drive just so we would not reinstall them backwards. It wasn't always this slow, so maybe there's something wrong with the hard drives. So we have this S170 sitting here doing nothing and we decided to experement with it. It was updated to the latest Async OS (using putty ssh session) to ensure that its up to date.īecause we cannot manage it via the gui (It takes about 2 hours to get from the login screen to export the xml configuration for example), we rolled out a S300V and moved our WCCP firewall statements to the new virtual appliance.
All administration tasks must be done via Putty. We have an S170 that has become too slow for us to administer via the web gui.
0 kommentar(er)
