Re-imaging Prox4.0 to Prox4.1 RPOOL issue

MikeC

Renowned Member
Jan 11, 2016
72
0
71
Bay Area, California
Hello all,

I had a task to upgrade a recently created prox4.0 server to 4.1. I decided to use the USB stick approach, which I had done initially to create the first server.

We booted up and got almost all the way through the re-install when we received several different errors. I configured the server with 2 2TB drives using ZFS RAID 1. Both drives were reporting OK to the pool before I started the wipe and re-install.

The errors are on a screenshot, which didn't get the wntire screen, but here are some of the errors:

Setting up pve-firewall (2.0-14) ...
invoke-rc.d: policy-rc.d denied execution of start. [rest cut off]
invoke-rc.d: policy-rc.d denied execution of start. [rest cut off]
Setting up libpve-storage-perl (4.0-38) ...
Setting up qemu-server (4.0-41) ...
Setting up pve-ha-manager (1.0-14) ...
Setting up pve-container (1.0-32) ...
Setting up pve-manager (4.1-1) ...
Update failed - see /var/log/pveam.log for details
Running in chroot, ignoring request.
Setting up proxmox-ve (4.1-26) ...
Installing proxmox release key: OK
Processing triggers for libc-bin (2.19-18+deb8u1) ...
Processing triggers for systemd (215-17+deb8u2) ...
Processing triggers for ca-certificates (20141019)
Updating certificates in /etc/ca-certificates/update.d....
Processing triggers for python-support (1.0.15) ...
Created symlink from /etc/systemd/syste/sysinit.ta[rest cut off]
.service.
Removing 'diversion of /usr/sbin/update-grub to /us[rest cut off]
Removing 'diversion of /usr/sbin/update-initramfs t[rest got cut off]
update-initramfs: Generating /boot/initrd.img-4.2.6
Installing for i386-pc platform.
error: cannot read `/dev/dsb': Input/output error.
error: cannot read `/dev/dsb': Input/output error.
error: cannot read `/dev/dsb': Input/output error.
error: cannot read `/dev/dsb': Input/output error.
error: cannot read `/dev/dsb': Input/output error.
/usr/sbin/grub-install: error: cannot find a GRUB d[rest cut off]
unable to install the i386-pc boot loader on '/dev/[rest cut off]
umount: /rpool/ROOT/pve-1/var/lib/vz: not mounted
umount: /rpool/ROOT/pve-1: target busy
cannot unmount '/rpool/ROOT/pve-1': umount failed

So it looks like the second drive is having problems, but up until I shur the server down and installed the USB stick, it was working fine. I'm not convinced the second drive would have just gone south like that.

Any ideas?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!