BTW, the instructions I found on the proxmox forums:
use the Proxmox VE ISO (or USB) and start the installation in debug
mode.
on the first stop, press CTRL-D to continue and the installer
switches to graphic mode - not abort the installation, as you do not
want to format your server!
the "abort" will give you a shell and access to the zfs root file system
> zpool import -a
Do not work for me as the keyboard does not work when booting in debug mode!
On 23/09/2017 12:40 AM, Lindsay Mathieson wrote:
I have a 4.x Proxmox node that is failing to boot today, get past the
bios etc, then blank screen with a blinking cursor - no console output
from the boot process at all.
- vs 4 + latest updates from no-sub repo
- Have explicitly picked the boot drive at start to ensure it using
the right disk
- Boot disk is a 240MB Kingston SSD (no raid)
Fortunately I was about to boot the system using the rescue mode from
the Proxmox ISO, and it running fine now, but still won't boot without
the rescue iso. But I can access the disks and they seem ok.
I presume its some sort of grub error but I have no idea how to repair
a zfs boot drive.
zpool status rpool
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 0h6m with 0 errors on Sat Sep 23 00:36:20
2017
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sdj2 ONLINE 0 0 0
errors: No known data errors
zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 83.4G 132G 96K /rpool
rpool/ROOT 1.79G 132G 96K /rpool/ROOT
rpool/ROOT/pve-1 1.79G 132G 1.79G /
rpool/data 96K 132G 96K /rpool/data
rpool/lizardfs 73.0G 132G 73.0G /lizardfs
rpool/swap 8.50G 133G 7.49G -
--
Lindsay Mathieson
_______________________________________________
pve-user mailing list
[email protected]
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
