My new installation just died

esi_y · Oct 8, 2024

gfngfn256 said:
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.

These were actually good points from @gfngfn256, both re Zigbee (1) and USB bus (2) and the kernel could explain if started to happen to you only now, but I understood you installed it only recently, so this was first time you went on to reboot...

thusband · Oct 8, 2024

esi_y said:
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).

Yeah, I would agree. The same situation happened with a previously owned NUC. On a restart it wouldn't boot up but inserting the install media did something. Or it seemed to kick start something so it booted up. I'm probably making some assumptions and misreading something.

esi_y said:
This is a USB drive that it is storing video onto?

Yes, a 1TB USB SSD. It records 24/7 and automatically deletes a portion when more space is needed.

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

The install script for the SSD drive is here. It's part of the program install procedure.

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

root@kilnclose:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=39D5-FF15 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

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

It sure didn't seem like two minutes to boot up this morning. I'm a little gun shy about about rebooting to test it out though.

esi_y · Oct 8, 2024

thusband said:
The install script for the SSD drive is here. It's part of the program install procedure.

Alright, I think I know now what's going on, I confused myself above, in fact.

Can you show:

Code:

# fill in whatever $VMID you chose for your NVR

cat /etc/pve/lxc/$VMID.conf

# and then also

lsblk -o +UUID

thusband · Oct 8, 2024

esi_y said:
Alright, I think I know now what's going on, I confused myself above, in fact.

Can you show:

Code:

# fill in whatever $VMID you chose for your NVR cat /etc/pve/lxc/$VMID.conf # and then also lsblk -o +UUID

Here you go.
root@kilnclose:~# cat /etc/pve/lxc/10443.conf
#<div align='center'>
# <a href='https%3A//Helper-Scripts.com'>
# <img src='https%3A//github.com/koush/scrypted/blob/main/docs/plugins/core/ui/img/icons/icon-128x128.png?raw=true'/>
# </a>
#
# # Scrypted
#
# <div><a href='https%3A//scrypted%3A10443/'>Management Console</a></div>
# <div><a href='https%3A//docs.scrypted.app'>Docs</a></div>
#
# <br/>
# <div>Container root password%3A scrypted</div>
#</div>
arch: amd64
cores: 4
features: nesting=1
hostname: scrypted
memory: 16384
mp0: local-lvm:vm-10443-disk-1,mp=/root/.scrypted/volume,backup=1,size=16G
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:64:08:CC,ip=dhcp,ip6=auto,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-10443-disk-0,size=24G
swap: 512
unprivileged: 1
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/accel dev/accel none bind,optional,create=dir
lxc.mount.entry: /dev/apex_0 dev/apex_0 none bind,optional,create=file
lxc.mount.entry: /dev/apex_1 dev/apex_1 none bind,optional,create=file
lxc.mount.entry: /dev/bus/usb dev/bus/usb none bind,optional,create=dir
lxc.mount.entry: /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage none bind,optional,create=dir
root@kilnclose:~#

And:
root@kilnclose:~# lsblk -o +UUID[/CODE]
lsblk: unknown column: UUID[/CODE]
root@kilnclose:~#
Maybe I messed that one up.

esi_y · Oct 8, 2024

thusband said:

Here you go.

Code:

lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/accel dev/accel none bind,optional,create=dir
lxc.mount.entry: /dev/apex_0 dev/apex_0 none bind,optional,create=file
lxc.mount.entry: /dev/apex_1 dev/apex_1 none bind,optional,create=file
lxc.mount.entry: /dev/bus/usb dev/bus/usb none bind,optional,create=dir
lxc.mount.entry: /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage none bind,optional,create=dir

Ok, so now, let's check how this was mounted:

Code:

mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage

thusband said:
root@kilnclose:~# lsblk -o +UUID[/CODE]
Maybe I messed that one up.

Yeah, this forum is also a bit messed up. There's two way here to include code-like text, inline or block. Either you use the icons above looking like </> and [>_] (inline and block respectively), or you enclose whatever text into (I am putting in extra space to have it show) [ ICODE ] [ /ICODE ] and [ CODE ] [ /CODE ] tags.

I think you just copied the forum tag somehow.

It should be:

lsblk -o +UUID

gfngfn256 · Oct 8, 2024

thusband said:
The same situation happened with a previously owned NUC. On a restart it wouldn't boot up but inserting the install media did something. Or it seemed to kick start something so it booted up.

Possibly you have secure-boot enabled in BIOS. Try disabling it. Also check in BIOS that the PVE system disk is the first boot device option.

thusband · Oct 8, 2024

esi_y said:
Ok, so now, let's check how this was mounted:

Code:

mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage

Did I mess this up?
root@kilnclose:~# mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage
grep: mnt/nvr/large/nvr-storage: No such file or directory
root@kilnclose:~#

esi_y said:
Yeah, this forum is also a bit messed up. There's two way here to include code-like text, inline or block. Either you use the icons above looking like </> and [>_] (inline and block respectively), or you enclose whatever text into (I am putting in extra space to have it show) [ ICODE ] [ /ICODE ] and [ CODE ] [ /CODE ] tags.

I think you just copied the forum tag somehow.

It should be:

lsblk -o +UUID

And...

Code:

root@kilnclose:~# lsblk -o +UUID
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS UUID
sda    8:0    0 931.5G  0 disk             
└─sda1
       8:1    0 931.5G  0 part /mnt/pve/nvr-storage
                                           e5bfba41-b327-4e86-b5bf-a91b36fad6bc
nvme0n1
     259:0    0 931.5G  0 disk             
├─nvme0n1p1
│    259:1    0  1007K  0 part             
├─nvme0n1p2
│    259:2    0     1G  0 part /boot/efi   39D5-FF15
└─nvme0n1p3
     259:3    0 930.5G  0 part             0xFadj-nfWi-A0sY-v84u-UrI0-cB50-nay8bO
  ├─pve-swap
  │  252:0    0     8G  0 lvm  [SWAP]      3be7899b-144c-4510-bc0d-05269ff07244
  ├─pve-root
  │  252:1    0    96G  0 lvm  /           37c45738-8ac4-403a-9be3-7131490d8b3a
  ├─pve-data_tmeta
  │  252:2    0   8.1G  0 lvm             
  │ └─pve-data-tpool
  │    252:4    0 794.3G  0 lvm             
  │   ├─pve-data
  │   │  252:5    0 794.3G  1 lvm             
  │   ├─pve-vm--10443--disk--0
  │   │  252:6    0    24G  0 lvm              789a6add-5ae0-4128-990c-083d4ece8883
  │   ├─pve-vm--10443--disk--1
  │   │  252:7    0    16G  0 lvm              ece17991-aef1-4c0a-bfbd-cdcae5a1327d
  │   ├─pve-vm--10443--disk--2
  │   │  252:8    0     8G  0 lvm              fa02964b-2883-482d-8b5c-04837c103985
  │   ├─pve-vm--10443--disk--3
  │   │  252:9    0     8G  0 lvm              79eb9cb2-6c1c-403a-9593-27be413ac242
  │   ├─pve-vm--10443--disk--4
  │   │  252:10   0     8G  0 lvm              f32eb062-c11e-4964-895b-b84b8a1e3a93
  │   ├─pve-vm--100--disk--0
  │   │  252:11   0     4M  0 lvm             
  │   └─pve-vm--100--disk--1
  │      252:12   0    32G  0 lvm             
  └─pve-data_tdata
     252:3    0 794.3G  0 lvm             
    └─pve-data-tpool
       252:4    0 794.3G  0 lvm             
      ├─pve-data
      │  252:5    0 794.3G  1 lvm             
      ├─pve-vm--10443--disk--0
      │  252:6    0    24G  0 lvm              789a6add-5ae0-4128-990c-083d4ece8883
      ├─pve-vm--10443--disk--1
      │  252:7    0    16G  0 lvm              ece17991-aef1-4c0a-bfbd-cdcae5a1327d
      ├─pve-vm--10443--disk--2
      │  252:8    0     8G  0 lvm              fa02964b-2883-482d-8b5c-04837c103985
      ├─pve-vm--10443--disk--3
      │  252:9    0     8G  0 lvm              79eb9cb2-6c1c-403a-9593-27be413ac242
      ├─pve-vm--10443--disk--4
      │  252:10   0     8G  0 lvm              f32eb062-c11e-4964-895b-b84b8a1e3a93
      ├─pve-vm--100--disk--0
      │  252:11   0     4M  0 lvm             
      └─pve-vm--100--disk--1
         252:12   0    32G  0 lvm             
root@kilnclose:~#

gfngfn256 · Oct 8, 2024

thusband said:
mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage

You didn't mess it up, but you should have entered:

Code:

mount | grep "/mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage"

thusband · Oct 8, 2024

gfngfn256 said:
You didn't mess it up, but you should have entered:

Code:

mount | grep "/mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage"

Sorry, is that with the parenthesis? With them or without them I get nothing.

esi_y · Oct 8, 2024

gfngfn256 said:
You didn't mess it up, but you should have entered:

Code:

mount | grep "/mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage"

No, this is double-mess up, this time by me as well.

It should be just:

Code:

mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr

esi_y · Oct 8, 2024

thusband said:

And...

Code:

root@kilnclose:~# lsblk -o +UUID
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS UUID
sda    8:0    0 931.5G  0 disk           
└─sda1
       8:1    0 931.5G  0 part /mnt/pve/nvr-storage
                                           e5bfba41-b327-4e86-b5bf-a91b36fad6bc
...

This is good now!

esi_y · Oct 8, 2024

This is just note to myself (in case I reply late) or for someone else who takes over:

You were originally failing in the boot because:

Code:

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.

But above in the lsblk output, there is no such blockdev even.

And I suspect there's something wrong with:

Code:

lxc.mount.entry: /mnt/pve/nvr-storage/mounts/scrypted-nvr mnt/nvr/large/nvr-storage none bind,optional,create=dir

This is a product of the script:
https://raw.githubusercontent.com/koush/scrypted/main/install/proxmox/setup-scrypted-nvr-volume.sh

esi_y · Oct 8, 2024

esi_y said:
No, this is double-mess up, this time by me as well.

It should be just:

Code:

mount | grep /mnt/pve/nvr-storage/mounts/scrypted-nvr

Btw I am pretty positive now this will be empty as well, but that's not the issue.

Can you show:

Code:

cat /etc/systemd/system/mnt-pve-scrypted.mount

thusband · Oct 8, 2024

esi_y said:
Btw I am pretty positive now this will be empty as well, but that's not the issue.

Can you show:

Code:

cat /etc/systemd/system/mnt-pve-scrypted.mount

Yes, it was empty. The cat request shows:

root@kilnclose:~# cat /etc/systemd/system/mnt-pve-scrypted.mount
[Install]
WantedBy=multi-user.target

[Mount]
Options=defaults
Type=ext4
What=/dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501
Where=/mnt/pve/scrypted

[Unit]
Description=Mount storage 'scrypted' under /mnt/pve

root@kilnclose:~#
Many thanks for all the help.

esi_y · Oct 8, 2024

thusband said:
Yes, it was empty. The cat request shows:

root@kilnclose:~# cat /etc/systemd/system/mnt-pve-scrypted.mount
[Install]
WantedBy=multi-user.target

[Mount]
Options=defaults
Type=ext4
What=/dev/disk/by-uuid/791bc6ef-2083-40c4-ade6-c25f680eb501
Where=/mnt/pve/scrypted

[Unit]
Description=Mount storage 'scrypted' under /mnt/pve

root@kilnclose:~#
Many thanks for all the help.

I suppose you have nothing in /etc/pve/scrypted.

I do not see it referenced anywhere. I would literally remove /etc/systemd/system/mnt-pve-scrypted.mount.

(When I say remove anything during troubleshooting, you may want to e.g. mkdir ~/stash and then mv /etc/systemd/system/mnt-pve-scrypted.mount ~/stash/ instead.

)

I would then go on to reboot. BEFORE that, so that you do not have to keep manually removing the quiet boot option, just make it permanent (Section 2):
https://forum.proxmox.com/threads/boot-troubleshooting-verbose-output.155631/

Search

Search

My new installation just died

esi_y

Renowned Member

thusband

Member

esi_y

Renowned Member

thusband

Member

esi_y

Renowned Member

gfngfn256

Renowned Member

thusband

Member

gfngfn256

Renowned Member

thusband

Member

esi_y

Renowned Member

esi_y

Renowned Member

esi_y

Renowned Member

esi_y

Renowned Member

thusband

Member

esi_y

Renowned Member