[megoldva] proxmox 4 boot fail

Virtualizáció

Sziasztok!

Adott egy proxmox 4-es cluster és az egyik node újraindítás után nem akar elindulni.

Itt a bootlogja, azt látom hogy hol a gond, viszont azt nem tudom hogy lehet elhárítani.

Loading Linux 4.2.6-1-pve ...
Loading initial ramdisk ...
[ 1.803356] i8042: No controller found
Loading, please wait...
fsck from util-linux 2.25.2
/dev/mapper/pve-root: clean, 61832/3801088 files, 775228/15204352 blocks
[ 4.270940] systemd-sysv-generator[268]: Ignoring creation of an alias umountiscsi.service for itself
[ 7.087438] Error: Driver 'pcspkr' is already registered, aborting...
[ TIME ] Timed out waiting for device dev-pve-data.device.
[DEPEND] Dependency failed for /var/lib/vz.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for File System Check on /dev/pve/data.
[ TIME ] Timed out waiting for device dev-pve-swap.device.
[DEPEND] Dependency failed for /dev/pve/swap.
[DEPEND] Dependency failed for Swap.
Starting Proxmox VE Login Banner...
Starting Proxmox VE firewall logger...
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Serial Getty on ttyS0.
[ OK ] Stopped getty on tty2-tty6 if dbus and logind are not available.
[ OK ] Stopped target Graphical Interface.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped Deferred execution scheduler.
[ OK ] Stopped target ZFS startup target.
[ OK ] Stopped ZFS file system shares.
[ OK ] Stopped ZFS Event Daemon (zed).
[ OK ] Stopped PVE VM Manager.
[ OK ] Stopped PVE SPICE Proxy Server.
[ OK ] Stopped PVE API Proxy Server.
[ OK ] Stopped Kernel Samepage Merging (KSM) Tuning Daemon.
[ OK ] Stopped OpenBSD Secure Shell server.
[ OK ] Stopped PVE Status Daemon.
[ OK ] Stopped Self Monitoring and Reporting Technology (SMART) Daemon.
[ OK ] Stopped PVE Local HA Ressource Manager Daemon.
[ OK ] Stopped LXC Container Initialization and Autoboot Code.
[ OK ] Stopped FUSE filesystem for LXC.
[ OK ] Stopped LXC network bridge setup.
[ OK ] Stopped PVE Cluster Ressource Manager Daemon.
[ OK ] Stopped Proxmox VE watchdog multiplexer.
[ OK ] Stopped PVE API Daemon.
[ OK ] Stopped Cgroup management proxy.
[ OK ] Stopped Cgroup management daemon.
[ OK ] Stopped /etc/rc.local Compatibility.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped Login Service.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Reached target Login Prompts.
[ OK ] Stopped LSB: Start NTP daemon.
[ OK ] Stopped target Mail Transport Agent.
[ OK ] Stopped LSB: Postfix Mail Transport Agent.
[ OK ] Stopped LSB: start the RRDtool data caching daemon.
[ OK ] Stopped Regular background program processing daemon.
[ OK ] Stopped System Logging Service.
[ OK ] Stopped target Basic System.
[ OK ] Reached target Timers.
[ OK ] Stopped target System Initialization.
Starting Commit Proxmox VE network changes...
Starting Create Volatile Files and Directories...
Starting LSB: Raise network interfaces....
[ OK ] Closed Syslog Socket.
[ OK ] Reached target Sockets.
Starting Emergency Shell...
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
[ OK ] Started Proxmox VE firewall logger.
[ OK ] Started Commit Proxmox VE network changes.
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[ OK ] Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of LVM2 logical volumes...
Starting Copy rules generated while the root was ro...
[ OK ] Started Copy rules generated while the root was ro.
[ OK ] Started Proxmox VE Login Banner.
Activating swap /dev/pve/swap...
[ OK ] Activated swap /dev/pve/swap.
[ OK ] Started Activation of LVM2 logical volumes.
[ OK ] Reached target Encrypted Volumes.
Starting Import ZFS pools by device scanning...
Starting Activation of LVM2 logical volumes...
Starting File System Check on /dev/pve/data...
[ 99.467895] systemd-fsck[753]: /dev/mapper/pve-data: clean, 19/9428992 files, 639771/37686272 blocks
[ OK ] Started File System Check on /dev/pve/data.
Mounting /var/lib/vz...
[ OK ] Started Activation of LVM2 logical volumes.
Starting Monitoring of LVM2 mirrors, snapshots etc. ...ress polling...
[ OK ] Mounted /var/lib/vz.
[ OK ] Started Import ZFS pools by device scanning.
Welcome to emergGive root password for maintenance
(or type Control-D to continue):

  • 3558 megtekintés

Nehéz a google-be beírni hogy:
" Welcome to emergGive root password for maintenance
(or type Control-D to continue): "

Kb az első találat felsorol vagy 5 tippet mit érdemes meglesni miért csinálhatja.

Hogy ne kelljen google-hoz nyulni ideirom:

- wrong or misconfigured disk controller driver (e.g. a kernel update gone wrong)
- hardware failure in a disk controller
- wrong root filesystem specification in the kernel command line (in the bootloader configuration file)
- damaged root filesystem
some other local filesystem that is listed in /etc/fstab is missing or damaged
- typo in /etc/fstab

Fedora 22, Thinkpad x220

Szerintem ez: 


[ TIME ] Timed out waiting for device dev-pve-data.device.
[ TIME ] Timed out waiting for device dev-pve-swap.device.

Nem tudja/túl lassan csatolja a fentieket, és ennek az eredménye a:

Welcome to emergency mode! After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.

De nem láttam még proxmoxt.

( Elbandi v | 2016. 01. 19., k – 20:39 )

itt a forumon senkinek nincs gondolatolvaso kepessege (barmennyire is szeretne :D), igy irhatnal par infot a kornyezetrol. milyen a network (egyszeru, vagy vannak vlanok), milyen storagek van beallitva (iscsi, zfs, stb)

--
A vegtelen ciklus is vegeter egyszer, csak kelloen eros hardver kell hozza!

Azért nem írtam nem én sem vagyok gondolat olvasó és nem gondoltam hogy kelleni fog :)

Akkor a felállás:
3 node-os cluster: intel szerver 16GB - 8GB - 16GB-os felállásban 1 db desktop Seagate hdd minden egyiben ( ebből a egyik megadta magát ezért is kezdődött ez a mizéria ) 2x1Gbit lacp trunk production hálózat fele és 2x1Gbit storage hálózat fele
storage rész: 2 db kiszuperált pc-ből épült gluster fs storage, 4 hdd raid 6-ban ubuntu 14.04 alapon ext4-el

( dzsambo | 2016. 01. 21., cs – 21:42 )

sikerült megoldani a problémát, a gond a filerendszerrel volt és mind a 3 node-on. Csak azt nem értem miért.

És akkor a lényeg:

e2fsck 1.42.12 (29-Aug-2014)
e2fsck: Invalid argument while trying to open /dev/sdb1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
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
or
e2fsck -b 32768

root@xxx-node-x:~# mke2fs -n /dev/sdb1
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 1004 1k blocks and 128 inodes