Grub Error Reading outside of disk

R

redmop

Well-Known Member
Feb 24, 2015
121
2
58
This is happening again. I have made no changes to the system, not even updates. I rebooted it because the cluster became out of sync (again) but that's not the problem I'm working on here.

Dell T130. Fully updated. Proxmox 4.4. This started before after the upgrade to 4.4. It's continued after a clean install. ZFS root raidz. 32 GB ram. Last updated about 2 weeks ago.

upload_2017-2-5_17-21-33.png

If I boot to Ubuntu 16.04.1-64 via ISO and assemble the zpool, all the data is there. It scrubs just fine.

This is unlikely to be a disk error as it happened before on all three servers, and I needed to rebuild them all to get them running again.

What can I do here?
 
redmop said:
This is happening again. I have made no changes to the system, not even updates. I rebooted it because the cluster became out of sync (again) but that's not the problem I'm working on here.

Dell T130. Fully updated. Proxmox 4.4. This started before after the upgrade to 4.4. It's continued after a clean install. ZFS root raidz. 32 GB ram. Last updated about 2 weeks ago.

View attachment 4716

If I boot to Ubuntu 16.04.1-64 via ISO and assemble the zpool, all the data is there. It scrubs just fine.

This is unlikely to be a disk error as it happened before on all three servers, and I needed to rebuild them all to get them running again.

What can I do here?
Click to expand...

maybe the BIOS does something strange with the disk order that gets Grub confused? could you post the output of "ls" in the rescue shell? you can also try "ls" on each of the reported disks/partitions, to see which device is detected under which name. the output of "set" shows you where Grub is attempting to boot from.
 
fabian said:
maybe the BIOS does something strange with the disk order that gets Grub confused? could you post the output of "ls" in the rescue shell? you can also try "ls" on each of the reported disks/partitions, to see which device is detected under which name. the output of "set" shows you where Grub is attempting to boot from.
Click to expand...

upload_2017-2-6_10-45-29.png
 

Attachments

  • upload_2017-2-6_10-44-48.png
    upload_2017-2-6_10-44-48.png
    12.1 KB · Views: 7
I reverted the bios to a version that it ran on for a while, and I get the same problem.
 
I can also get the directories and files listed in ls (hd0,gpt2)/ROOT/pve-1@/boot/grub.

"insmod normal" gives the read or write error.
 
Now that I've pondered it a bit, it is looking like it's the size of the drives. I'll backup, make a efi boot partition, and restore and see if that helps. If not, I'll make a /boot partition.
 
You must log in or register to reply here.
Top Bottom