Hey @Impact, | Home Assistant | Page 1

mint sphinx Jun 4, 2024, 1:05 PM

#

And the other command you asked for, with labels (and with the dev/loop partitions removed for brevity):

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS                         LABEL                  FSTYPE
/dev/sda      8:0    1 114.6G  0 disk                                     Ubuntu 24.04 LTS amd64 iso9660
├─/dev/sda1   8:1    1   5.7G  0 part /cdrom                              Ubuntu 24.04 LTS amd64 iso9660
├─/dev/sda2   8:2    1     5M  0 part                                     ESP                    vfat
├─/dev/sda3   8:3    1   300K  0 part                                                            
└─/dev/sda4   8:4    1 108.9G  0 part /var/crash                          writable               ext4
                                      /var/log                                                   
/dev/sdb      8:16   0 238.4G  0 disk                                                            
├─/dev/sdb1   8:17   0     1G  0 part                                     hassos-boot            vfat
└─/dev/sdb2   8:18   0 237.3G  0 part                                                            ```

fringe dew Jun 4, 2024, 1:42 PM

#

Yeah it should look like what I shared or the flashing didn't work.

#

We could flash like this: #installation-archived message

mint sphinx Jun 4, 2024, 2:04 PM

#

Meaning the terminal method not via etcher, right?

fringe dew Jun 4, 2024, 2:04 PM

#

Yeah.

mint sphinx Jun 4, 2024, 2:23 PM

#

I'll give it a go. Should I reformat the ssd or anything before running those commands?

fringe dew Jun 4, 2024, 2:32 PM

#

Shouldn't be needed.

#

Just pick the right disk.

#

And check again with lsblk.

mint sphinx Jun 4, 2024, 2:35 PM

#

🤞

mint sphinx Jun 4, 2024, 2:59 PM

#

Ok, here's the result of that exercise. I substituted in the current version of HAOS and otherwise the only other thing was that I had to sudo the dd... command
log here: https://pastebin.mozilla.org/RMGh44Pi

fringe dew Jun 4, 2024, 2:59 PM

#

What does lsblk -po+LABEL,FSTYPE say now after the dd?

mint sphinx Jun 4, 2024, 3:01 PM

#

/dev/loops removed...

ubuntu@ubuntu:~$ lsblk -po+LABEL,FSTYPE
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS LABEL                  FSTYPE
/dev/sda      8:0    1 114.6G  0 disk             Ubuntu 24.04 LTS amd64 iso9660
├─/dev/sda1   8:1    1   5.7G  0 part /cdrom      Ubuntu 24.04 LTS amd64 iso9660
├─/dev/sda2   8:2    1     5M  0 part             ESP                    vfat
├─/dev/sda3   8:3    1   300K  0 part                                    
└─/dev/sda4   8:4    1 108.9G  0 part /var/crash  writable               ext4
                                      /var/log                           
/dev/sdb      8:16   0 238.4G  0 disk

😬

fringe dew Jun 4, 2024, 3:02 PM

#

The loops are part of the live iso/system I think.

mint sphinx Jun 4, 2024, 3:03 PM

#

Oh I mean I just manually removed them from the output for brevity, but yes I think you are right

fringe dew Jun 4, 2024, 3:03 PM

#

/dev/sdb should look like in my example I linked to earlier.

#

Multiple partitions, one with a label of hassos-boot.

#

Oh I see.

#

Hmm. No I don't.

mint sphinx Jun 4, 2024, 3:05 PM

#

Yeah, I'm not seeing anything on that drive now

#

should I try the alternate command that you had recommended?
xzcat haos_generic-x86-64-10.1.img.xz | dd bs=16M of=/dev/sdb status=progress

fringe dew Jun 4, 2024, 3:08 PM

#

Shouldn't make a difference.

#

I will try to reproduce it again in a minute.

mint sphinx Jun 4, 2024, 3:11 PM

#

Thank you in advance!

fringe dew Jun 4, 2024, 3:20 PM

#

https://dpaste.org/6DH75

#

Works fine as it always did.

#

You might be thinking

what happens if the disk was already used? After all I asked this earlier
Should I reformat the ssd or anything before [...]?
I reinitialized the disk and created a single small partition on it just to prove that it works fine still
https://dpaste.org/Kmqwk

mint sphinx Jun 4, 2024, 3:32 PM

#

😟

#

Any recommendations for things to try next?

fringe dew Jun 4, 2024, 3:40 PM

#

Not at the moment.

fringe dew Jun 4, 2024, 4:07 PM

#

Can you try fdisk -l /dev/sdb?

#

Can you perhaps also share the full output of lsblk -po+LABEL,FSTYPE,MODEL?

mint sphinx Jun 4, 2024, 5:25 PM

#

fringe dew Can you try `fdisk -l /dev/sdb`?

root@ubuntu:/home/ubuntu# fdisk -l /dev/sdb
Disk /dev/sdb: 114.62 GiB, 123060879360 bytes, 240353280 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x405a23c7

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdb1  *          0   8498951   8498952   4.1G  0 Empty
/dev/sdb2       5717156   5725283      8128     4M ef EFI (FAT-12/16/32)
/dev/sdb3       8499200 240353279 231854080 110.6G 83 Linux

mint sphinx Jun 4, 2024, 5:26 PM

#

mint sphinx ``` root@ubuntu:/home/ubuntu# fdisk -l /dev/sdb Disk /dev/sdb: 114.62 GiB, 12306...

Actuall sdb and sda seem to have gotten swapped at some point in all of this. here's sda

root@ubuntu:/home/ubuntu# fdisk -l /dev/sda
GPT PMBR size mismatch (12582911 != 62486527) will be corrected by write.
Disk /dev/sda: 238.38 GiB, 255944818688 bytes, 62486528 sectors
Disk model: KLUEG8U1EA-B0C1 
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: gpt
Disk identifier: C2D94067-8908-41BE-9DE0-F5C77DEB4EB7

Device      Start      End  Sectors   Size Type
/dev/sda1     256   275455   275200   1.1G EFI System
/dev/sda2  275456 62486271 62210816 237.3G Linux filesystem

mint sphinx Jun 4, 2024, 5:28 PM

#

fringe dew Can you perhaps also share the full output of `lsblk -po+LABEL,FSTYPE,MODEL`?

root@ubuntu:/home/ubuntu# lsblk -po+LABEL,FSTYPE,MODEL
NAME     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT LABEL                 FSTYPE MODEL
/dev/loop0
           7:0    0   2.2G  1 loop /rofs                            squash 
/dev/loop1
           7:1    0     4K  1 loop /snap/bare                       squash 
/dev/loop2
           7:2    0 346.3M  1 loop /snap/gnom                       squash 
/dev/loop3
           7:3    0    46M  1 loop /snap/snap                       squash 
/dev/loop4
           7:4    0  63.3M  1 loop /snap/core                       squash 
/dev/loop5
           7:5    0  91.7M  1 loop /snap/gtk-                       squash 
/dev/loop6
           7:6    0  49.9M  1 loop /snap/snap                       squash 
/dev/sda   8:0    0 238.4G  0 disk                                         KLUEG
├─/dev/sda1
│          8:1    0   1.1G  0 part            hassos-boot           vfat   
└─/dev/sda2
           8:2    0 237.3G  0 part                                         
/dev/sdb   8:16   1 114.6G  0 disk            Ubuntu 20.04.6 LTS amd64
│                                                                   iso966 SanDi
├─/dev/sdb1
│          8:17   1   4.1G  0 part /cdrom     Ubuntu 20.04.6 LTS amd64
│                                                                   iso966 
├─/dev/sdb2
│          8:18   1     4M  0 part                                  vfat   
└─/dev/sdb3
           8:19   1 110.6G  0 part /var/crash writable              ext4   ```

fringe dew Jun 4, 2024, 6:09 PM

#

Hmm.

#

I'm confused why this happens and that bugs me.

mint sphinx Jun 5, 2024, 2:12 PM

#

Seems like I've managed to royally muck this up 😓

mint sphinx Jun 8, 2024, 9:48 PM

#

Hey @fringe dew, I haven't gotten anywhere with the baremetal install. I was able to install Ubuntu 20.04, but then ran into issues when I tried to update it. For the hell of it, I then tried to install Proxmox VE and it seems to have worked...? I've never used Proxmox. I know that you didn't recommend PVE in this case (I think because limited RAM (8 GB), but I'm feeling a bit hopeless with the baremetal approach. Thoughts?

fringe dew Jun 9, 2024, 12:30 AM

#

Also because I thought the disk would be listed as eMMC but it isn't.

#

I guess you can try with PVE and this guide: https://www-derekseaman-com.webpkgcache.com/doc/-/s/www.derekseaman.com/2023/10/home-assistant-proxmox-ve-8-0-quick-start-guide-2.html

mint sphinx Jun 9, 2024, 3:49 AM

#

Yes, after some finagling with my network, I got that working! 🎉 . Everything went smoothly except I named my FQDN host1 for some reason and it seems like changing that to something more descriptive like pve or proxmox is finicky without starting over (unless ya know of an easy method)

fringe dew Jun 9, 2024, 3:50 AM

#

Pretty simple actually.

#

Well, kind of.

#

https://pve.proxmox.com/wiki/Renaming_a_PVE_node

mint sphinx Jun 9, 2024, 3:53 AM

#

Yeah... I did that and it seemed to mess things up...

#

changed the names back and it seemed to work fine.

#

Well, I changed things here:
/etc/hosts
/etc/hostname

fringe dew Jun 9, 2024, 3:54 AM

#

Mess up how?

mint sphinx Jun 9, 2024, 3:55 AM

#

The VM seemed to completely disappear? And there was still a host1 node but it was unreachable (forge the verbiage, but it was throwing an error).

fringe dew Jun 9, 2024, 3:56 AM

#

You might have to reboot or restart the PVE services.

#

I'll try to reproduce when I'm done with my shenanigans.

mint sphinx Jun 9, 2024, 3:58 AM

#

That'd be awesome! It's just bothering me aesthetically, but would be nice to clean up. Otherwise, HA seems to be working well!

fringe dew Jun 9, 2024, 4:16 AM

#

Okay so steps are pretty simple.

# Edit/replace accordingly
nano /etc/hosts
nano /etc/hostname
hostnamectl hostname NEWHOSTNAME
cd /etc/pve/nodes/
cp -Rf OLDNODENAME/ NEWNODENAME/
mv OLDNODENAME/ /tmp
systemctl restart pve-cluster.service pveproxy.service pvestatd.service

Refresh the Web GUI and see if it works.

mint sphinx Jun 9, 2024, 7:02 PM

#

Well, my HA and AdguardHome VMs seem to have disappeared...

#

Though HA is still running...?

fringe dew Jun 9, 2024, 7:17 PM

#

Refresh the frontend or reboot. These steps worked for my test PVE.

#

You might have to copy more things from the directory in /tmp

mint sphinx Jun 9, 2024, 7:20 PM

#

I think that I may have misconfigured /etc/hosts. I was getting a Proxy not allowed 500 message and now I can't access it at it's IP address

fringe dew Jun 9, 2024, 7:20 PM

#

Maybe. You can share the config files with me but I'm too tired to help right now.

mint sphinx Jun 9, 2024, 7:21 PM

#

This is what I have:

127.0.0.1 localhost.localdomain localhost
192.168.20.6 proxmox.local proxmox

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts```

fringe dew Jun 9, 2024, 7:22 PM

#

What's your node name?

mint sphinx Jun 9, 2024, 7:22 PM

#

proxmox

fringe dew Jun 9, 2024, 7:22 PM

#

What does hostname -i and ip -a say?

mint sphinx Jun 9, 2024, 7:23 PM

#

let me see

#

hostname -i
192.168.20.6

#

ip -a gives options for commands, I think

fringe dew Jun 9, 2024, 7:25 PM

#

Check journalctl -f while you access the GUI.

mint sphinx Jun 9, 2024, 7:28 PM

#

I can't access the GUI at all now

#

GUI issue was a firewall rule 🤦‍♂️

fringe dew Jun 9, 2024, 7:31 PM

#

Oof.

mint sphinx Jun 9, 2024, 7:32 PM

#

But journalctl -f helped me identify it. It was an NTP issue, I think

fringe dew Jun 9, 2024, 7:33 PM

#

I tested the steps earlier in my nested PVE VM so I know they work. I can't remember if I checked if the guest(s) still shows up though. I don't see a reason why not other than that cp missed some files.

mint sphinx Jun 9, 2024, 7:34 PM

#

Guest meaning something like HA/adguard?

fringe dew Jun 9, 2024, 7:34 PM

#

VMs/CTs.

mint sphinx Jun 9, 2024, 7:42 PM

#

No need to answer this now, I know you already mentioned you are tired, but inside of /etc/pve/nodes/proxmox is a host1 file. Do you think that needs to be renamed to proxmox?

fringe dew Jun 9, 2024, 7:43 PM

#

Probably not. Please share

ls -lh /etc/pve/nodes/proxmox
ls -lh /etc/pve/nodes/proxmox/host1

#

Here's mine for comparison

# ls /etc/pve/nodes/mynode/
config  host.fw  lrm_status  lxc  openvz  priv  pve-ssl.key  pve-ssl.pem  qemu-server  ssh_known_hosts

mint sphinx Jun 9, 2024, 7:51 PM

#

total 1.5K
drwxr-xr-x 2 root www-data    0 Jun  9 14:55 host1
drwxr-xr-x 2 root www-data    0 Jun  8 21:05 lxc
drwxr-xr-x 2 root www-data    0 Jun  8 21:05 openvz
drwx------ 2 root www-data    0 Jun  8 21:05 priv
-rw-r----- 1 root www-data 1.7K Jun  8 21:05 pve-ssl.key
-rw-r----- 1 root www-data 1.8K Jun  8 21:05 pve-ssl.pem
drwxr-xr-x 2 root www-data    0 Jun  8 21:05 qemu-server
-rw-r----- 1 root www-data  560 Jun  9 15:35 ssh_known_hosts```

#

total 3.5K
-rw-r----- 1 root www-data   78 Jun  9 14:55 config
-rw-r----- 1 root www-data   84 Jun  9 14:55 lrm_status
drwxr-xr-x 2 root www-data    0 Jun  9 14:55 lxc
drwxr-xr-x 2 root www-data    0 Jun  9 14:55 openvz
drwxr-xr-x 2 root www-data    0 Jun  9 14:55 priv
-rw-r----- 1 root www-data 3.2K Jun  9 14:55 pveproxy-ssl.key
-rw-r----- 1 root www-data 3.9K Jun  9 14:55 pveproxy-ssl.pem
-rw-r----- 1 root www-data 1.7K Jun  9 14:55 pve-ssl.key
-rw-r----- 1 root www-data 1.8K Jun  9 14:55 pve-ssl.pem
drwxr-xr-x 2 root www-data    0 Jun  9 14:55 qemu-server
-rw-r----- 1 root www-data  558 Jun  9 14:55 ssh_known_hosts```

fringe dew Jun 9, 2024, 7:52 PM

#

Mhh. I guess you can try to take a backup of /etc/pve and try to merge them.

#

As in cp -Rf /etc/pve/nodes/proxmox/host1/* /etc/pve/nodes/proxmox/ or similar.

#

I'm not sure why host1 is even in there.

mint sphinx Jun 9, 2024, 7:53 PM

#

i'll see how it goes. i'm getting to the point of just nuking the whole thing and starting from scratch.

fringe dew Jun 9, 2024, 7:53 PM

#

You can't use rsync, at least not with default arguments, because /etc/pve is a bit special. It's not a normal file system.

#

:<

mint sphinx Jun 9, 2024, 7:54 PM

#

cp -Rf /etc/pve/nodes/proxmox/host1/* /etc/pve/nodes/proxmox/ seems like it might have worked some magic

#

VMs appeared in a stopped state. Starting them now...

#

We have life, I think!

fringe dew Jun 9, 2024, 7:58 PM

#

Always back up configs ybefore editing them.

#

rsnapshot and etckeeper are some simple tools for that.

mint sphinx Jun 9, 2024, 7:59 PM

#

I'll look into those tools, thanks!

#Hey @Impact,