Upgrading a headless server to 17.10.1
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have a headless server running Ubuntu 17.04 Server that is normally controlled by SSH from a Mac. The nags to upgrade to 17.10 led me to a "not recommended to perform a upgrade over ssh" dialog.
So to accomplish the upgrade directly, I hooked up a monitor and keyboard and found nothing would display. Reboots produce a brief "Ubuntu 17.04" at screen middle thereafter nothing but a blinking cursor in the upper left corner. But the SSH connection continues to work as it did before.
What do I need to do or what is missing to control the server directly using keyboard and display?
Next I created a bootable flash drive containing a Ubuntu 17.10.1 Server thinking that would be another way to install an upgrade.
The flash drive boots and prompts display normally on the monitor. The installation process for the hardware did not seem to have an option to upgrade an existing installation (17.04 in my case). I got very nervous about what settings and previous package installations might be destroyed, so the process was aborted.
Is this booting from a flash drive a reasonable way to upgrade?
Thanks for answers and any suggestions.
boot server upgrade headless
asked Feb 5 at 20:20
D. L. Fuller
11
add a comment |Â
up vote
0
down vote
favorite
I have a headless server running Ubuntu 17.04 Server that is normally controlled by SSH from a Mac. The nags to upgrade to 17.10 led me to a "not recommended to perform a upgrade over ssh" dialog.
So to accomplish the upgrade directly, I hooked up a monitor and keyboard and found nothing would display. Reboots produce a brief "Ubuntu 17.04" at screen middle thereafter nothing but a blinking cursor in the upper left corner. But the SSH connection continues to work as it did before.
What do I need to do or what is missing to control the server directly using keyboard and display?
Next I created a bootable flash drive containing a Ubuntu 17.10.1 Server thinking that would be another way to install an upgrade.
The flash drive boots and prompts display normally on the monitor. The installation process for the hardware did not seem to have an option to upgrade an existing installation (17.04 in my case). I got very nervous about what settings and previous package installations might be destroyed, so the process was aborted.
Is this booting from a flash drive a reasonable way to upgrade?
Thanks for answers and any suggestions.
boot server upgrade headless
asked Feb 5 at 20:20
D. L. Fuller
11
1
Run the upgrade inscreenif running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within ascreensession and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then doscreen -rto reattach to the session)
– Thomas Ward♦
Feb 5 at 20:42
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
@DLFuller I wasn't clear, I meantscreenon the server. SSH to the server, then runscreen, then run the upgrade command...
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a headless server running Ubuntu 17.04 Server that is normally controlled by SSH from a Mac. The nags to upgrade to 17.10 led me to a "not recommended to perform a upgrade over ssh" dialog.
So to accomplish the upgrade directly, I hooked up a monitor and keyboard and found nothing would display. Reboots produce a brief "Ubuntu 17.04" at screen middle thereafter nothing but a blinking cursor in the upper left corner. But the SSH connection continues to work as it did before.
What do I need to do or what is missing to control the server directly using keyboard and display?
Next I created a bootable flash drive containing a Ubuntu 17.10.1 Server thinking that would be another way to install an upgrade.
The flash drive boots and prompts display normally on the monitor. The installation process for the hardware did not seem to have an option to upgrade an existing installation (17.04 in my case). I got very nervous about what settings and previous package installations might be destroyed, so the process was aborted.
Is this booting from a flash drive a reasonable way to upgrade?
Thanks for answers and any suggestions.
boot server upgrade headless
asked Feb 5 at 20:20
D. L. Fuller
11
I have a headless server running Ubuntu 17.04 Server that is normally controlled by SSH from a Mac. The nags to upgrade to 17.10 led me to a "not recommended to perform a upgrade over ssh" dialog.
So to accomplish the upgrade directly, I hooked up a monitor and keyboard and found nothing would display. Reboots produce a brief "Ubuntu 17.04" at screen middle thereafter nothing but a blinking cursor in the upper left corner. But the SSH connection continues to work as it did before.
What do I need to do or what is missing to control the server directly using keyboard and display?
Next I created a bootable flash drive containing a Ubuntu 17.10.1 Server thinking that would be another way to install an upgrade.
The flash drive boots and prompts display normally on the monitor. The installation process for the hardware did not seem to have an option to upgrade an existing installation (17.04 in my case). I got very nervous about what settings and previous package installations might be destroyed, so the process was aborted.
Is this booting from a flash drive a reasonable way to upgrade?
Thanks for answers and any suggestions.
boot server upgrade headless
boot server upgrade headless
asked Feb 5 at 20:20
D. L. Fuller
11
asked Feb 5 at 20:20
D. L. Fuller
11
asked Feb 5 at 20:20
D. L. Fuller
11
asked Feb 5 at 20:20
D. L. Fuller
11
asked Feb 5 at 20:20
D. L. Fuller
11
11
1
Run the upgrade inscreenif running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within ascreensession and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then doscreen -rto reattach to the session)
– Thomas Ward♦
Feb 5 at 20:42
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
@DLFuller I wasn't clear, I meantscreenon the server. SSH to the server, then runscreen, then run the upgrade command...
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
1
Run the upgrade inscreenif running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within ascreensession and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then doscreen -rto reattach to the session)
– Thomas Ward♦
Feb 5 at 20:42
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
@DLFuller I wasn't clear, I meantscreenon the server. SSH to the server, then runscreen, then run the upgrade command...
– Thomas Ward♦
Feb 6 at 14:29
1
1
Run the upgrade in
screen if running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within a screen session and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then do screen -r to reattach to the session)– Thomas Ward♦
Feb 5 at 20:42
Run the upgrade in
screen if running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within a screen session and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then do screen -r to reattach to the session)– Thomas Ward♦
Feb 5 at 20:42
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
@DLFuller I wasn't clear, I meant
screen on the server. SSH to the server, then run screen, then run the upgrade command...– Thomas Ward♦
Feb 6 at 14:29
@DLFuller I wasn't clear, I meant
screen on the server. SSH to the server, then run screen, then run the upgrade command...– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Apology! I've answered my own question after a break and second look. And, learned a little about Virtual Terminals in Linux.
Me simply keying CTRL+AUX+F1 at the blank screen immediately got the login dialog on a virtual terminal. After that my upgrade simply required a sudo do-release-upgrade and following prompts.
I am still curious about what would happen with booting 17.10.1 from a flash drive and then trying to upgrade the server itself.
answered Feb 5 at 23:45
D. L. Fuller
11
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Apology! I've answered my own question after a break and second look. And, learned a little about Virtual Terminals in Linux.
Me simply keying CTRL+AUX+F1 at the blank screen immediately got the login dialog on a virtual terminal. After that my upgrade simply required a sudo do-release-upgrade and following prompts.
I am still curious about what would happen with booting 17.10.1 from a flash drive and then trying to upgrade the server itself.
answered Feb 5 at 23:45
D. L. Fuller
11
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
up vote
0
down vote
Apology! I've answered my own question after a break and second look. And, learned a little about Virtual Terminals in Linux.
Me simply keying CTRL+AUX+F1 at the blank screen immediately got the login dialog on a virtual terminal. After that my upgrade simply required a sudo do-release-upgrade and following prompts.
I am still curious about what would happen with booting 17.10.1 from a flash drive and then trying to upgrade the server itself.
answered Feb 5 at 23:45
D. L. Fuller
11
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Apology! I've answered my own question after a break and second look. And, learned a little about Virtual Terminals in Linux.
Me simply keying CTRL+AUX+F1 at the blank screen immediately got the login dialog on a virtual terminal. After that my upgrade simply required a sudo do-release-upgrade and following prompts.
I am still curious about what would happen with booting 17.10.1 from a flash drive and then trying to upgrade the server itself.
answered Feb 5 at 23:45
D. L. Fuller
11
Apology! I've answered my own question after a break and second look. And, learned a little about Virtual Terminals in Linux.
Me simply keying CTRL+AUX+F1 at the blank screen immediately got the login dialog on a virtual terminal. After that my upgrade simply required a sudo do-release-upgrade and following prompts.
I am still curious about what would happen with booting 17.10.1 from a flash drive and then trying to upgrade the server itself.
answered Feb 5 at 23:45
D. L. Fuller
11
answered Feb 5 at 23:45
D. L. Fuller
11
answered Feb 5 at 23:45
D. L. Fuller
11
answered Feb 5 at 23:45
D. L. Fuller
11
11
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
If you are curious, then backup your server and try it. Such tinkering and experimenting is the fun part. Worst case: You reinstall and then restore from the backup. Either way you learn something and have a fun afternoon. There is a great sense of accomplishment in breaking it, and then putting it back together again.
– user535733
Feb 6 at 4:01
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
@DLFuller you'd have to do a lot more manual steps to use the flash drive to upgrade a server edition. It's not designed that way, that installer.
– Thomas Ward♦
Feb 6 at 14:29
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003355%2fupgrading-a-headless-server-to-17-10-1%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Run the upgrade in
screenif running over SSH. That way it doesn't terminate automatically when you lose yuor SSH connection. That risk of SSH disconnect is why they don't recommend it, but you can do the upgrade process within ascreensession and that should protect the upgrade progress even if you disconnect from SSH (you just need to login then doscreen -rto reattach to the session)– Thomas Ward♦
Feb 5 at 20:42
Thanks Thomas Ward. But this noob knows little about screen. I assume you mean screen on the Mac using the cli. I now use the Terminal app for SSH connections to the Ubuntu Server. That app is also how I would also access screen. I don't get the advantage of screen. Terminal seems to reattach SSH sessions easily.
– D. L. Fuller
Feb 6 at 0:00
@DLFuller I wasn't clear, I meant
screenon the server. SSH to the server, then runscreen, then run the upgrade command...– Thomas Ward♦
Feb 6 at 14:29