My new installation just died

[thusband]

I installed Proxmox on my BeeLink Mini and it started without any problem. I set up a LXC for Scrypted (security camera software) and then a VM for Home assistant. Both were running. I then plugged in my Zigbee antenna to set up the pass through and the connection just dropped. in my router it shows off line. I've tried powering off and on but nothing happens except the power light on the mini comes on.

This is more or less the same thing that happened previously so I reinstalled Proxmox. I really thought I wouldn't see this issue again.

I know this isn't much information but I really don't know where I should start looking.

Any hints would be greatly appreciated.

 

[thusband]

Screenshots. Sorry, I'm grasping at straws here. I have no idea where to look.


This is as far as I get. It finally times out.

 

[thusband]

Could it be something the BIOS perhaps? Something really basic?

 

[esi_y]

I would start by pressing 'e' on the GRUB screen and editing out the "quiet" from the line (at the bottom) where the options is defined, then watch the output from there.

 

[thusband]

Do you mean "quiet" from the linux line?

Editing involves just moving the cursor down and deleting "quiet" and then rebooting?

Thanks for the start.

 

[esi_y]

Do you mean "quiet" from the linux line?

Editing involves just moving the cursor down and deleting "quiet" and then rebooting?

Thanks for the start

Correct, but not "rebooting", proceeding to boot with (or rather without) that option (with F10 or follow the shortcuts mentioned in the footer). Note the settings is only for the current boot, if you reboot again, you are going to default to the boot with quiet option again, unless you remove it.

 

[thusband]

OK, I removed the "quiet", hit F10 and the boot continued to a long list of things. At the bottom was a timer with seconds/1:30. When it reached 1:30 it continued to this screenshot which has my Proxmox IP address. Now, however, Proxmox is available on my home network. I can login and it opens up.
Does this screenshot say what the issue might be?

 

[esi_y]

Nope, this looks normal to me, but what you can do now, since you have access is to check the whole bootlog, so get output (this will redirect it to a file):

journalctl -b > current.log

You can then copy out the file and attach it to have a look? It should show whatever was taking so long as well.

 

[thusband]

If I enter the code in the node shell nothing happens.
edit: I can get the log but I'm not sure What I do with it. There appears to be hundreds of lines.

 

[gfngfn256]

If I enter the code in the node shell nothing happens.

If by "nothing happens" you mean; it just goes down a line - then this is perfect. You should have a file named current.log in your active directory, which you can check.

On your main problem - since it seems your PVE fails when you attach that Zigbee dongle, I would suspect one of 2 things:

1. Your mini-pc has a power problem, that can't power correctly when the above dongle is attached.
2. On recent Proxmox kernels (I believe from 6.8), some people with some USB devices have complete USB bus crashes. This maybe what you are experiencing.

To test, you could try installing a previous kernel/version of Proxmox. Also try connecting a different dongle / USB device & see what happens. Also you could try a different USB port. This helps sometimes.

Good luck.

 

[gfngfn256]

edit: I can get the log but I'm not sure What I do with it. There appears to be hundreds of lines.

You need to check it for errors, kernel crashes etc. You could upload it here, & maybe others will take a look at it. It may not show any serious errors if your whole system just "completely crashed".

 

[thusband]

OK, finally got it. Lots of lines. I don't see anything off hand but I'm not sure (to say the least).
Again, many thanks for any assistance.

 

[thusband]

If by "nothing happens" you mean; it just goes down a line - then this is perfect. You should have a file named current.log in your active directory, which you can check.

On your main problem - since it seems your PVE fails when you attach that Zigbee dongle, I would suspect one of 2 things:

1. Your mini-pc has a power problem, that can't power correctly when the above dongle is attached.
2. On recent Proxmox kernels (I believe from 6.8), some people with some USB devices have complete USB bus crashes. This maybe what you are experiencing.

To test, you could try installing a previous kernel/version of Proxmox. Also try connecting a different dongle / USB device & see what happens. Also you could try a different USB port. This helps sometimes.

Good luck.

I reconnected the Zigbee dongle this morning after it booted up and so far it's holding on. I guess I'll try to reboot Proxmox and see what happens as that's when it crashed in the past.

Maybe it's the Beelink mini. I managed to finally post current.log .

 

[thusband]

Maybe remove the CMOS battery and let it discharge to bring the BIOS back to the default?

 

[esi_y]

Oct 08 07:10:41 kilnclose systemd[1]: systemd-fsckd.service: Deactivated successfully.
Oct 08 07:11:40 kilnclose systemd[1]: dev-disk-by\x2duuid-791bc6ef\x2d2083\x2d40c4\x2dade6\x2dc25f680eb501.device: Job dev-disk-by\x2duuid-791bc6ef\x2d2083\x2d40c4\x2dade6\x2dc25f680eb501.device/start timed out.
Oct 08 07:11:40 kilnclose systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-791bc6ef\x2d2083\x2d40c4\x2dade6\x2dc25f680eb501.device - /dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501.
Oct 08 07:11:40 kilnclose systemd[1]: Dependency failed for mnt-pve-scrypted.mount - Mount storage 'scrypted' under /mnt/pve.
Oct 08 07:11:40 kilnclose systemd[1]: mnt-pve-scrypted.mount: Job mnt-pve-scrypted.mount/start failed with result 'dependency'.
Oct 08 07:11:40 kilnclose systemd[1]: dev-disk-by\x2duuid-791bc6ef\x2d2083\x2d40c4\x2dade6\x2dc25f680eb501.device: Job dev-disk-by\x2duuid-791bc6ef\x2d2083\x2d40c4\x2dade6\x2dc25f680eb501.device/start failed with result 'timeout'.
Oct 08 07:11:40 kilnclose systemd[1]: Reached target local-fs.target - Local File Systems.

Do you have any idea what this disk is?

 

[thusband]

Hmmm, Scrypted is my NVR system for an outside security camera. It uses an SSD to store video. It seems to be working OK since Proxmox started back up this morning (I'm in the UK). Is it causing problems?

 

[esi_y]

You may want to check what it is that it cannot actually mount by:

ls -l /dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501

I just go backwards from you symptoms, you started with "nothing happens" on boot, but the only thing that PVE does on bootup is go quiet (pretty weird default) until all is booted up. All you did with removing the quiet is let it show you on the console what it is that it was doing. I was expecting it would halt at some point where you would have a screen showing what caused it, but instead it proceeded to boot. The only thing notable was something is delaying the boot by 1min30sec, now - this is it. At this point, not sure if your "nothing happens" was just describing this prolonged wait or something else.

About your "plugged in my Zigbee antenna to set up the pass through and the connection just dropped" - I suspect this is entirely different problem and it would need reproducing separately while watching e.g. dmesg when you are attemting it. But I doubt it has anything to do with your delayed (quiet) boot at this point.

 

[esi_y]

NB How is the NVR system installed there, actually?

 

[thusband]

Yes previously it would not boot. In the past Proxmox would run fine until I had to reboot (due to a kernal update or something). Then it would not boot back up until I hooked a monitor up and inserted the Proxmox install USB flash card. I know, weird isn't it?

The SSD drive, I think, is mounted as it's now storing video.


The Zigbee antenna seems to be OK after I installed it again and got Home Assistant to recognise it. I haven't hooked it up to any devices however.

I installed Scrypted via a script provided by the developer (https://docs.scrypted.app/installation.html#proxmox-ve). He also had a script to mount the SSD.

When I run the drive mount inquiry I get:
root@kilnclose:~# ls -l /dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501
ls: cannot access '/dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501': No such file or directory


I guess I'll continue on until it dies again.

Thanks for all your help. I learned a few things today.

 

[esi_y]

Yes previously it would not boot. In the past Proxmox would run fine until I had to reboot (due to a kernal update or something). Then it would not boot back up until I hooked a monitor up and inserted the Proxmox install USB flash card. I know, weird isn't it?

This does not make much sense to me. I mean I believe your observations are valid, but I do not think it's related (with the install media).

The SSD drive, I think, is mounted as it's now storing video.

This is a USB drive that it is storing video onto?

I installed Scrypted via a script provided by the developer (https://docs.scrypted.app/installation.html#proxmox-ve). He also had a script to mount the SSD.

Where's the mounting script? I suspect you are mounting it too early, that's delaying your boot.

When I run the drive mount inquiry I get:
root@kilnclose:~# ls -l /dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501
ls: cannot access '/dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501': No such file or directory

The this should be removed from /etc/fstab, can you check what's in cat /etc/fstab?

I guess I'll continue on until it dies again.

It will take 2min to boot for no good reason. You should fix this.