Failing to boot Ubuntu 18.04 - “attempt to read or write outside of 'hd0'”
Clash Royale CLAN TAG#URR8PPP
2
I am having issues booting and end up in a grub rescue shell.
error: attempt to read or write outside of disk 'hd0'.
Entering rescue mode...
grub rescue>
Searching around the web, i have found some commands to get a bit more information about my system.
Running sudo fdisk -l gives
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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
Disk /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 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
Disk /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 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
Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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
Disk /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 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
Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 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
Disk /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 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
Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 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
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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: 0x99811f5b
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 488396799 488394752 232.9G 8e Linux LVM
Disk /dev/sdb: 14.5 GiB, 15524167680 bytes, 30320640 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: 0x32234161
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 30320639 30312576 14.5G c W95 FAT32 (LBA)
Disk /dev/mapper/ubuntu--vg-root: 231.9 GiB, 249028411392 bytes, 486383616 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
Disk /dev/mapper/ubuntu--vg-swap_1: 980 MiB, 1027604480 bytes, 2007040 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
From which we can see my main drive is /dev/sda and the root and swap use lvm.
The /dev/sda and /dev/sda1 have the boot flag. It is pretty much a standard unbuntu installation. The /dev/sdb is the usb drive i am using right now to run my computer.
To me, all seems fine and i am out of idea on how to get my desktop back. How should one approch this problem to solve it?
Thanks,
linux ubuntu boot lvm grub
edited Dec 29 '18 at 17:15
valiano
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
This question has an open bounty worth +50
reputation from Routhinator ending ending at 2019-01-17 04:15:08Z">in 6 days.
This question has not received enough attention.
add a comment |
2
I am having issues booting and end up in a grub rescue shell.
error: attempt to read or write outside of disk 'hd0'.
Entering rescue mode...
grub rescue>
Searching around the web, i have found some commands to get a bit more information about my system.
Running sudo fdisk -l gives
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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
Disk /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 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
Disk /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 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
Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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
Disk /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 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
Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 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
Disk /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 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
Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 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
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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: 0x99811f5b
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 488396799 488394752 232.9G 8e Linux LVM
Disk /dev/sdb: 14.5 GiB, 15524167680 bytes, 30320640 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: 0x32234161
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 30320639 30312576 14.5G c W95 FAT32 (LBA)
Disk /dev/mapper/ubuntu--vg-root: 231.9 GiB, 249028411392 bytes, 486383616 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
Disk /dev/mapper/ubuntu--vg-swap_1: 980 MiB, 1027604480 bytes, 2007040 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
From which we can see my main drive is /dev/sda and the root and swap use lvm.
The /dev/sda and /dev/sda1 have the boot flag. It is pretty much a standard unbuntu installation. The /dev/sdb is the usb drive i am using right now to run my computer.
To me, all seems fine and i am out of idea on how to get my desktop back. How should one approch this problem to solve it?
Thanks,
linux ubuntu boot lvm grub
edited Dec 29 '18 at 17:15
valiano
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
This question has an open bounty worth +50
reputation from Routhinator ending ending at 2019-01-17 04:15:08Z">in 6 days.
This question has not received enough attention.
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday
add a comment |
2
2
2
1
I am having issues booting and end up in a grub rescue shell.
error: attempt to read or write outside of disk 'hd0'.
Entering rescue mode...
grub rescue>
Searching around the web, i have found some commands to get a bit more information about my system.
Running sudo fdisk -l gives
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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
Disk /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 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
Disk /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 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
Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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
Disk /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 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
Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 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
Disk /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 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
Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 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
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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: 0x99811f5b
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 488396799 488394752 232.9G 8e Linux LVM
Disk /dev/sdb: 14.5 GiB, 15524167680 bytes, 30320640 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: 0x32234161
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 30320639 30312576 14.5G c W95 FAT32 (LBA)
Disk /dev/mapper/ubuntu--vg-root: 231.9 GiB, 249028411392 bytes, 486383616 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
Disk /dev/mapper/ubuntu--vg-swap_1: 980 MiB, 1027604480 bytes, 2007040 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
From which we can see my main drive is /dev/sda and the root and swap use lvm.
The /dev/sda and /dev/sda1 have the boot flag. It is pretty much a standard unbuntu installation. The /dev/sdb is the usb drive i am using right now to run my computer.
To me, all seems fine and i am out of idea on how to get my desktop back. How should one approch this problem to solve it?
Thanks,
linux ubuntu boot lvm grub
edited Dec 29 '18 at 17:15
valiano
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
I am having issues booting and end up in a grub rescue shell.
error: attempt to read or write outside of disk 'hd0'.
Entering rescue mode...
grub rescue>
Searching around the web, i have found some commands to get a bit more information about my system.
Running sudo fdisk -l gives
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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
Disk /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 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
Disk /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 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
Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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
Disk /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 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
Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 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
Disk /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 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
Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 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
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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: 0x99811f5b
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 488396799 488394752 232.9G 8e Linux LVM
Disk /dev/sdb: 14.5 GiB, 15524167680 bytes, 30320640 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: 0x32234161
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 30320639 30312576 14.5G c W95 FAT32 (LBA)
Disk /dev/mapper/ubuntu--vg-root: 231.9 GiB, 249028411392 bytes, 486383616 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
Disk /dev/mapper/ubuntu--vg-swap_1: 980 MiB, 1027604480 bytes, 2007040 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
From which we can see my main drive is /dev/sda and the root and swap use lvm.
The /dev/sda and /dev/sda1 have the boot flag. It is pretty much a standard unbuntu installation. The /dev/sdb is the usb drive i am using right now to run my computer.
To me, all seems fine and i am out of idea on how to get my desktop back. How should one approch this problem to solve it?
Thanks,
linux ubuntu boot lvm grub
linux ubuntu boot lvm grub
edited Dec 29 '18 at 17:15
valiano
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
edited Dec 29 '18 at 17:15
valiano
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
edited Dec 29 '18 at 17:15
valiano
202111
edited Dec 29 '18 at 17:15
valiano
202111
edited Dec 29 '18 at 17:15
valiano
202111
202111
asked Dec 29 '18 at 4:30
JonathanJonathan
112
asked Dec 29 '18 at 4:30
JonathanJonathan
112
asked Dec 29 '18 at 4:30
JonathanJonathan
112
112
This question has an open bounty worth +50
reputation from Routhinator ending ending at 2019-01-17 04:15:08Z">in 6 days.
This question has not received enough attention.
This question has an open bounty worth +50
reputation from Routhinator ending ending at 2019-01-17 04:15:08Z">in 6 days.
This question has not received enough attention.
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday
add a comment |
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491411%2ffailing-to-boot-ubuntu-18-04-attempt-to-read-or-write-outside-of-hd0%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491411%2ffailing-to-boot-ubuntu-18-04-attempt-to-read-or-write-outside-of-hd0%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Dropping a bounty on this. I have this happening on a server with an HP Enterprise SSD in it. It happens very frequently when rebooting. I have the luxury of wiping the install and reprovisioning the disk with ansible afterwards as this is just the root disk, but this keeps reoccurring. It's not a one off problem. And it's 18.04 specific. I would like a way to recover without a wipe.
– Routhinator
yesterday
Just found this, looks like this issue is a mixed bag: askubuntu.com/questions/229715/…
– Routhinator
yesterday