Search results

nevermind it just booted. I literally rebooted it 6 times with nothing....figures.

I see on the server's console the booting up........................ message then instead of the Proxmox blue background selection screen, the server just goes on to other means of booting like PXE, and never actually boots Proxmox. Can i do a repair from the install CD or am I stuck with...

Thanks to everyone who helped, but after reinstalling unsuccessfully multiple times on 4 different HDD's using newly burned install media, I finally broke down ran the mem test off the proxmox install media... and well looky there (see below screenshot), the box is not under warranty so I guess...

My Cisco box is old but it does have an IPMI or IMC as they call it, but not the ability to upload an iso file that I can see. It's ok, I need the fresh air anyways.

Ok burned new CD at my house, we are mostly remote still, this afternoon will schedule an office visit to insert CD into drive then we'll see.

I reinstalled again, named it proxomox6, just in case, and have not updated or joined to the cluster yet and I get this already: I guess my install media is corrupt? Or hardware maybe? I got not errors during install, seems weird to me.

I did name it the same name as the previously failed node. Should I reinstall and rename to 'proxmox6' and see if the cluster treats it differently? Just a thought. only other thing would be to get a different physical box and see if its hardware somehow.

fresh install, even wiped HDD's, but same install CD as the other 4 proxmox's that ARE working.

yes, the iscsi and lvm were removed, then proxmox5 was restarted. journal result attached

root@proxmox5:~# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● run-rpc_pipefs.mount loaded failed failed RPC Pipe File System ● iscsid.service loaded failed failed iSCSI initiator daemon (iscsid) ● lvm2-activation-early.service...

notice this error in the cli: root@proxmox5:~# zpool list The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. root@proxmox5:~# How do I get the ZFS modules to load? and why do they quit after joining the new node to the cluster?

I did that and i still get this on the ZFS window in the GUI:

also for what its worth the proxmox5 syslog on the failing iscsi connection:

I did notice that the ZFS was running initially, but stopped sometime after i joined it to the existing cluster of 4 other Proxmox boxes. Can the act of joining to a cluster have an adverse affect on the zfs module?

Wow, i completely blew away the proxmox5 machine and reinstalled from scratch, it also has the ZFS not running error. exactly the error that the old box had when i first started this thread. unbelievable?! Maybe hardware bad, but how could that effect zfs system from even running? when I try...

root@proxmox5:~# journalctl -u lvm2-pvscan@253:16.service -- Logs begin at Fri 2020-05-29 14:38:34 CDT, end at Fri 2020-05-29 15:45:20 CDT. -- -- No entries -- root@proxmox5:~# pvscan PV /dev/sdg3 VG pve lvm2 [<184.83 GiB / <16.00 GiB free]...

No encryption. If i login to 1 of the other 4 hosts and goto Datacenter -> Storage -> Add -> ZFS -> then RAIDZ does not populate only "replication" (an existing zfs) If i login to Proxmox5 and goto Datacenter -> Storage -> Add -> ZFS -> then RAIDZ does populate but not "replication" clearly...

No Ceph. One ISCSI target to a Nimble SAN. (LVM) Trying to add zfs local RAIDZ using on board JBOD HDD's, which shows in pool list: root@proxmox5:~# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT RAIDZ 2.71T 528K 2.71T - -...

root@proxmox5:~# systemctl list-units --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION ● lvm2-pvscan@253:16.service loaded failed failed LVM event activation on device 253:16 ● zfs-import-cache.service loaded failed failed Import ZFS pools by cache file LOAD =...

● proxmox5 State: starting Jobs: 4 queued Failed: 3 units