So tonight I decided to try and configure the virtual machine manager on top of my normal network bond. To cut the story short as soon as I enabled the virtual switch on the bond I lost connectivity even after a reboot. I then did a reinstall option during boot and chose to migrate my data, all was good with the find.synology.com piece but after a reboot it didn't come up and now a further reinstall isn't establishing standard DHCP networking to the unit. So i'm concerned that the migrate option may have pulled down the new 6.2.x release and borked the entire thing
I've had xpenology running for 6 months or so, but generally without issue. I'm now concerned I may have just made my system unrecoverable? This is on a HP Microserver Gen8 bare metal
Not sure what to do next, so would appreciate any advice you can offer to help me remedy the situation!
Question
Matty123
So tonight I decided to try and configure the virtual machine manager on top of my normal network bond. To cut the story short as soon as I enabled the virtual switch on the bond I lost connectivity even after a reboot. I then did a reinstall option during boot and chose to migrate my data, all was good with the find.synology.com piece but after a reboot it didn't come up and now a further reinstall isn't establishing standard DHCP networking to the unit. So i'm concerned that the migrate option may have pulled down the new 6.2.x release and borked the entire thing
I've had xpenology running for 6 months or so, but generally without issue. I'm now concerned I may have just made my system unrecoverable? This is on a HP Microserver Gen8 bare metal
Not sure what to do next, so would appreciate any advice you can offer to help me remedy the situation!
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.