I have an issue where fsck fails on startup with the following error:
fsck died with exit status 8
failed (code 8)
file system check failed. A log is being saved in var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue): hub 1-1:1.0 unable to enumerate USB device on port 2
I have never seen this issue before until I performed an update from PROXMOX v2.3 to 3.0
I have tried running a fsck on the devices myself manually using a live cd with no results to show there is an issue with the drives.
I would like to get this fixed as it prevents the server from booting up itself without manual intervention.
In the meantime I am going to keep the system booted so that I can utilise the server.
Results of pveversion -v is below:
root@proxmoxprd1:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 1.0-36
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
root@proxmoxprd1:~#
root@proxmoxprd1:/var/log/fsck# cat checkfs
Log of fsck -C -R -A -a
Thu Jul 25 14:20:06 2013
Log from var/log/fsck/checkfs
fsck from util-linux-ng 2.17.2
fsck.ext3: No such file or directory while trying to open /dev/pve/data
/dev/pve/data:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/sda1: clean, 236/131072 files, 118189/523264 blocks
fsck died with exit status 8
Thu Jul 25 14:20:06 2013
----------------
root@proxmoxprd1:/var/log/fsck#
Any help in this regard would be greatly appreciated.
Thank you in advance.
fsck died with exit status 8
failed (code 8)
file system check failed. A log is being saved in var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue): hub 1-1:1.0 unable to enumerate USB device on port 2
I have never seen this issue before until I performed an update from PROXMOX v2.3 to 3.0
I have tried running a fsck on the devices myself manually using a live cd with no results to show there is an issue with the drives.
I would like to get this fixed as it prevents the server from booting up itself without manual intervention.
In the meantime I am going to keep the system booted so that I can utilise the server.
Results of pveversion -v is below:
root@proxmoxprd1:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 1.0-36
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
root@proxmoxprd1:~#
root@proxmoxprd1:/var/log/fsck# cat checkfs
Log of fsck -C -R -A -a
Thu Jul 25 14:20:06 2013
Log from var/log/fsck/checkfs
fsck from util-linux-ng 2.17.2
fsck.ext3: No such file or directory while trying to open /dev/pve/data
/dev/pve/data:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/sda1: clean, 236/131072 files, 118189/523264 blocks
fsck died with exit status 8
Thu Jul 25 14:20:06 2013
----------------
root@proxmoxprd1:/var/log/fsck#
Any help in this regard would be greatly appreciated.
Thank you in advance.
Last edited:
