Host unreachable after resizing partition
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have VPS in OVH which I recently upgraded. The upgrade came with additional 10GB of storage but I had to resize partition by myself.
I did it like that:
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 20971519 20969472 10G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-41943039, default 2048):
Last sector, +sectors or +sizeK,M,G,T,P (2048-41943039, default 41943039):
Created a new partition 1 of type 'Linux' and of size 20 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
And I rebooted the server. But ping is saying Destination Host Unreachable and I cannot login through ssh. I also don't have access via KVM from OVH manager. There is no problem to log in in rescue mode, the resized partition mounts correctly and I see all my data.
Is it something with booting? How can I fix it or what should I check to get more information on what is the problem?
EDIT:
This is the current state of the partition
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 41943039 41940992 20G 83 Linux
I still have the output of the partition state before the change if it can help.
EDIT2:
The output from the KVM (the console from OVH control panel):
SeaBIOS (...)
Machine UUID (...)
iPXE (...)
Booting from Hard Disk...
MBR
SYSLINUX 6.03 (...)
Dots in brackets indicate some version or copyright information which I think is irrelevant
partition fdisk vps ovh
asked Oct 28 '17 at 17:06
Szymon Sadło
12
 |Â
show 2 more comments
up vote
0
down vote
favorite
I have VPS in OVH which I recently upgraded. The upgrade came with additional 10GB of storage but I had to resize partition by myself.
I did it like that:
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 20971519 20969472 10G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-41943039, default 2048):
Last sector, +sectors or +sizeK,M,G,T,P (2048-41943039, default 41943039):
Created a new partition 1 of type 'Linux' and of size 20 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
And I rebooted the server. But ping is saying Destination Host Unreachable and I cannot login through ssh. I also don't have access via KVM from OVH manager. There is no problem to log in in rescue mode, the resized partition mounts correctly and I see all my data.
Is it something with booting? How can I fix it or what should I check to get more information on what is the problem?
EDIT:
This is the current state of the partition
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 41943039 41940992 20G 83 Linux
I still have the output of the partition state before the change if it can help.
EDIT2:
The output from the KVM (the console from OVH control panel):
SeaBIOS (...)
Machine UUID (...)
iPXE (...)
Booting from Hard Disk...
MBR
SYSLINUX 6.03 (...)
Dots in brackets indicate some version or copyright information which I think is irrelevant
partition fdisk vps ovh
asked Oct 28 '17 at 17:06
Szymon Sadło
12
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
I did. Used commandaand thenw. But this changed nothing and the problem is still the same
– Szymon Sadło
Oct 28 '17 at 18:59
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51
 |Â
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have VPS in OVH which I recently upgraded. The upgrade came with additional 10GB of storage but I had to resize partition by myself.
I did it like that:
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 20971519 20969472 10G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-41943039, default 2048):
Last sector, +sectors or +sizeK,M,G,T,P (2048-41943039, default 41943039):
Created a new partition 1 of type 'Linux' and of size 20 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
And I rebooted the server. But ping is saying Destination Host Unreachable and I cannot login through ssh. I also don't have access via KVM from OVH manager. There is no problem to log in in rescue mode, the resized partition mounts correctly and I see all my data.
Is it something with booting? How can I fix it or what should I check to get more information on what is the problem?
EDIT:
This is the current state of the partition
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 41943039 41940992 20G 83 Linux
I still have the output of the partition state before the change if it can help.
EDIT2:
The output from the KVM (the console from OVH control panel):
SeaBIOS (...)
Machine UUID (...)
iPXE (...)
Booting from Hard Disk...
MBR
SYSLINUX 6.03 (...)
Dots in brackets indicate some version or copyright information which I think is irrelevant
partition fdisk vps ovh
asked Oct 28 '17 at 17:06
Szymon Sadło
12
I have VPS in OVH which I recently upgraded. The upgrade came with additional 10GB of storage but I had to resize partition by myself.
I did it like that:
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 20971519 20969472 10G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-41943039, default 2048):
Last sector, +sectors or +sizeK,M,G,T,P (2048-41943039, default 41943039):
Created a new partition 1 of type 'Linux' and of size 20 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
And I rebooted the server. But ping is saying Destination Host Unreachable and I cannot login through ssh. I also don't have access via KVM from OVH manager. There is no problem to log in in rescue mode, the resized partition mounts correctly and I see all my data.
Is it something with booting? How can I fix it or what should I check to get more information on what is the problem?
EDIT:
This is the current state of the partition
root@rescue-pro:~# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 41943039 41940992 20G 83 Linux
I still have the output of the partition state before the change if it can help.
EDIT2:
The output from the KVM (the console from OVH control panel):
SeaBIOS (...)
Machine UUID (...)
iPXE (...)
Booting from Hard Disk...
MBR
SYSLINUX 6.03 (...)
Dots in brackets indicate some version or copyright information which I think is irrelevant
partition fdisk vps ovh
asked Oct 28 '17 at 17:06
Szymon Sadło
12
edited Oct 29 '17 at 6:24
asked Oct 28 '17 at 17:06
Szymon Sadło
12
asked Oct 28 '17 at 17:06
Szymon Sadło
12
asked Oct 28 '17 at 17:06
Szymon Sadło
12
12
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
I did. Used commandaand thenw. But this changed nothing and the problem is still the same
– Szymon Sadło
Oct 28 '17 at 18:59
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51
 |Â
show 2 more comments
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
I did. Used commandaand thenw. But this changed nothing and the problem is still the same
– Szymon Sadło
Oct 28 '17 at 18:59
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
I did. Used command
a and then w. But this changed nothing and the problem is still the same– Szymon Sadło
Oct 28 '17 at 18:59
I did. Used command
a and then w. But this changed nothing and the problem is still the same– Szymon Sadło
Oct 28 '17 at 18:59
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51
 |Â
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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%2funix.stackexchange.com%2fquestions%2f401099%2fhost-unreachable-after-resizing-partition%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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');
);
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');
);
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
You haven't add the boot flag to the partition.
– Ipor Sircer
Oct 28 '17 at 17:49
I did. Used command
aand thenw. But this changed nothing and the problem is still the same– Szymon Sadło
Oct 28 '17 at 18:59
Can you check the consol physically? What is the status? Did you wait "long enough"? - because maybe a forced fsck slows down the boot process (to sometimes hours - but 20G should not take too long).
– V-Mark
Oct 28 '17 at 21:38
What do you mean by "check the consol physically"? I think I didn't wait "long enough", maybe around 15 minutes. If you say forced fsck may take few hours then I'll wait till tomorrow morning and see what happen.
– Szymon Sadło
Oct 28 '17 at 21:54
He means that instead of pinging the server you should try to see the actual booting "screen" to check for errors logged there. You usually have access to the VM console through your host control panel.
– Zip
Oct 28 '17 at 23:51