#I'm trying to get Home Assistant to use my RAID array, but am having no luck

1 messages · Page 1 of 1 (latest)

tranquil summit
#

Running the two following commands through Advanced SSH shell shows me the following:

➜  ~ lspci | grep -i raid
03:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3108 [Invader] (rev 02)
➜  ~ dmesg | grep -i raid
[   13.773895] md: If you don't use raid, use raid=noautodetect
[   13.781506] md: Autodetecting RAID arrays.

However, the RAID array isn't detected though I believe I have set it up correctly in the BIOS (and formatted it into EXT4 with a different operating system).

I get this when I run the following:

➜  ~ lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    1    0B  0 disk
sdb      8:16   0  1.8T  0 disk
├─sdb1   8:17   0   32M  0 part
├─sdb2   8:18   0   24M  0 part
├─sdb3   8:19   0  256M  0 part
├─sdb4   8:20   0   24M  0 part
├─sdb5   8:21   0  256M  0 part
├─sdb6   8:22   0    8M  0 part
├─sdb7   8:23   0   96M  0 part
└─sdb8   8:24   0  1.8T  0 part /etc/pulse/client.conf
                                /var/log/journal
                                /etc/hosts
                                /etc/hostname
                                /etc/resolv.conf
                                /run/audio
                                /etc/asound.conf
                                /share
                                /ssl
                                /homeassistant
                                /media
                                /backup
                                /addons
                                /data
                                /addon_configs
zram0  252:0    0    0B  0 disk
zram1  252:1    0   32M  0 disk
zram2  252:2    0   16M  0 disk

Would appreciate help figuring out what I'm doing wrong, or need to be doing to get HA to see my RAID array!

craggy hull
#

Please try

apk add pciutils
lspci -vnnk -s 03:

Maybe it doesn't have a driver for it.

tranquil summit
#

Output of the second command is as follows:

➜  ~ lspci -vnnk -s 03:
03:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02)
    Subsystem: Dell PERC H730P Adapter [1028:1f42]
    Flags: bus master, fast devsel, latency 0, IRQ 255, NUMA node 0
    I/O ports at 2000 [size=256]
    Memory at 92000000 (64-bit, non-prefetchable) [size=64K]
    Memory at 91f00000 (64-bit, non-prefetchable) [size=1M]
    Expansion ROM at <ignored> [disabled]
    Capabilities: [50] Power Management version 3
    Capabilities: [68] Express Endpoint, IntMsgNum 0
    Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [c0] MSI-X: Enable- Count=97 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [1e0] Secondary PCI Express
    Capabilities: [1c0] Power Budgeting <?>
    Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
craggy hull
#

I expected to see a Kernel driver in use: line.

tranquil summit
#

ah so does that mean no driver then? or does it mean the driver is there but not being loaded? (apologies for the basic question(s), this is a bit out of my league)

craggy hull
#

It's possible. You can try to go through the whole kernel log with | less. Perhaps see if there's more output related to the device.

tranquil summit
#

what's the command i should use for that? if you wouldnt mind

craggy hull
#

I'm not completely sure what to search for

dmesg | grep -Ei "(md:|lsi|03:)"

The one iI had in mind would be dmesg | less or ha host logs | less.

#

I'd recommend using this so you have times

apk add dmesg
dmesg -T | less

The default dmesg does not support -T.

tranquil summit
#

thanks i'll try that ... I havent but am not against it. will check your post in a little bit (at work currently)

#

i suppose one question i have (though i havent looked at your link) is what's the major benefit of virtualizing HAOS?

#

benefit / benefits

craggy hull
#

In your case a benefit would be freedom. You would not be reliant on HAOS' drivers and can install the drivers on the virtualization host instead.
HAOS only sees the virtualized storage for which it has drivers.

#

An older version of the content behind that link is also here: #hardware-archived message
I can't edit that any more though hence putting it on github.

tranquil summit
#

great thanks @craggy hull , let me read your page! I have another question though, based on these two links:

https://community.home-assistant.io/t/ha-os-vs-supervised/395968/2

https://www.home-assistant.io/installation/#advanced-installation-methods

again pardon my ignorance, but I decided to HAOS instead of supervised based on the info in the first link. If I choose to virtualize Home Assistant, which version would you recommend out of the 4 that are shown in advanced installation methods? Still HAOS (the first column in the table)?

Home Assistant

Install Home Assistant

craggy hull
#

Supervised is discouraged. I'd recommend either a HAOS VM or a debian VM with the HA container installation.

magic hollyBOT
#

Home Assistant Supervised is considered advanced and should only be used if you are an expert in managing a Linux operating system, Docker and networking. Maintaining a Debian installation to a very specific set of requirements is hard.
Insecure installations and Unsupported configurations will result if you dont know what you are doing.
You MAY regret using this method.

craggy hull
tranquil summit
#

yeah i think i installed supervised a long long time ago and had a bunch of issues

craggy hull
#

Addons are just docker containers. If you run HA as a container you can run anything else yourself too.

tranquil summit
#

True, that does make sense.

craggy hull
#
tranquil summit
#

the times i've tried to run additional docker containers that arent "Home assistant approved" adjacent to HAOS, HAOS started saying some error ... maybe something like it was an unsupported build. i'm forgetting the terminology now

craggy hull
tranquil summit
#

i think you're probably right haha. i would love to understand docker better w/ time. not there yet

craggy hull
#

The only benefit I see for supervised is that you can better troubleshoot and install some system tools. Like rclone for example. Nothing the HAOS target base should need. It's a poor middleground.
I run the docker variant in production but I have a HAOS VM to be able to help here.

tranquil summit
#

so ... 2 questions about container, so I can think about trying it some day:

  1. If it doesn't support add-ons "out of the box" per say, i'm assuming its still easy to use addons for Home Assistant that others have created through the CLI or in some other way?

  2. Will container not say unsupported configuration if run additional docker containers next to it?

You're right that this is the benefit of virtualization. Can try anything in a virtual machine, totally screw it all up, but not lose everything

Oh one more question, how does persistence work for HAOS in a VM? Or any OS running as a VM? That's something I've never quite understood (this last question may be more tangential than necessary for me to understand, but i'm curious about it!)

finite crescent
#
  1. Nope, it doesn't care
#

VM persistence is handled by the VM platform, and the fact that it writes to the disk like normal

#
  1. No add-ons means just that, none
#

Not that it usually matters

tranquil summit
#

i suppose i dont understand that part

#

i run a lot of add-ons in my Home Assistant instance

finite crescent
#

They're just software

#

It's likely that a container image for it exists

#

Hell, the add-on may even be based on it

tranquil summit
#

🤦‍♂️

#

so basically, instead of running the add-on, you just run the docker container directly

finite crescent
#

Yup

tranquil summit
#

hence why you can run any docker containers and Container wont shit the bed

finite crescent
#

Yup

tranquil summit
#

oh sorry another question! and i appreciate you and impacts help with this, truly

#

so the whole reason i asked this Q in the first place was about HAOS not recognizing my RAID controller

#

Impact mentioned: In your case a benefit would be freedom. You would not be reliant on HAOS' drivers and can install the drivers on the virtualization host instead.
HAOS only sees the virtualized storage for which it has drivers.

#

so lets say i go the virtualization route, and in the base OS, I install the drivers for this RAID controller

#

(hopefully my terminology is making sense)

finite crescent
#

Yup

tranquil summit
#

do i need to "do" anything to make those drivers available to the virtualized HAOS, or will it basically have access to all drivers available in the base OS

finite crescent
#

The VM guest knows nothing about the underlying hardware

#

That's the point

tranquil summit
#

oh that does make sense too. it's a virtual machine, its sort of "sandboxed"

finite crescent
#

Yup

#

More than sort of

tranquil summit
#

truth

#

so ... what would i need to do (generally speaking) to allow the VM to see the RAID array? I've played around with proxmox very little but i remember it being pretty straightforward to say, hey, give this VM access to this Z-wave USB stick. is it that easy for the RAID array as well?

finite crescent
#

You... Don't

#

See above

#

The guest gets a disk, it knows nothing about the underlying hardware

#

No RAID, nothing like that

tranquil summit
#

Maybe I'm asking the question incorrectly

#

you can share USB periperals with the VM right?

#

like my Z-wave stick

finite crescent
#

You're missing how VMs work

tranquil summit
#

i really really am haha

finite crescent
#

The guest is isolated from the details of the hardware

#

It just gets "a" disk, didn't know the hardware involved

tranquil summit
#

I think, i THINK i understand what you're saying

#

when you say it "gets a disk", you dont mean it gets it's own virtual disk - which is what i thought you meant. you're saying it gets the additional disk of the RAID. but knows nothing about the RAID controller because it's not the Base OS

craggy hull
#

There's a lot of variables as there's lots of choice so this is opinionated and highly simplified.
The OS uses the RAID controller via the driver it needs. You format that RAID "disk" with some storage type/format. You give the VM a virtual disk from that. The VM sees a virtual disk and uses an appropriate driver for it. Usually that's VirtIO which is included. The VM does not really know where/what that storage is. It could come from a network share an it wouldn't care.

tranquil summit
#

yes i think i understand this better now

#

do you have recommendations for the base os? i know a little about proxmox, which seems to try to make virtualization very simple, but perhaps you have better recs in your github page

craggy hull
#

This gives you lots of freedom to move the VM to different hardware, extend the virtual disk, change CPU cores, memory and so on.
My recommendation is in the link. I might be a bit biased but Proxmox VE seems to be go to for a free hypervisor.

tranquil summit
#

wonderful

#

i gave it a bookmark emoji above for obv reasons

#

i really appreciate your help both @craggy hull and @finite crescent

craggy hull
#

You can mostly learn as you go. The only real thing you really ought to know/research before installing it is how to pick an ip outside of the DHCP range of your router.

tranquil summit
#

........ isnt that something you set in the router? I'm given dedicated IPs to most of my devices in the 10.0.0.2 - 200 range, then left the rest up for grabs

#

meaning the DHCP range is 201 and above

#

(or, in some cases, made the dedicated IP set on the device match the IP set for that device in the router)

craggy hull
#

PVE uses a static ip (DHCP during install for the ip placeholder). You can reserve that in your router and I recommend that anyways to potentially be able to resolve it by hostname.
The safest way is to pick an ip outside of the range that your router gives to other devices via DHCP. Ip confllicts are very unpleasant.

tranquil summit
#

i have so many little ESPHome devices and whatever else that i can't risk them clashing

craggy hull
#

I should perhaps add a disclaimer. I do not know if PVE can use your RAID controller out of the box. But at least you have the ability to install one if there's one for debian/linux.

tranquil summit
#

no worries, HAOS couldnt use my RAID controller out of the box either 😛

craggy hull
#

Yeah but I used that inability to "sell" you on PVE.

tranquil summit
#

I didnt think it was malignant in any way though 😉

#

oh i suppose i have one more question

#

currently as you know i'm running HAOS on bare metal. I assume if I run it as a virtual machine, there'll be no issue loading up a backup into the VM?

But .... what about if I use Container? No add-ons i would assume means it's not going to accept the HAOS backup

#

(which is fine, I'm just thinking through pitfalls I may run into someday if/when switching to container)

craggy hull
#

The HAOS backup should be able to be restored on a HAOS VM without issues.
If I remember correctly the HAOS backup does not include system/OS specific things like the network config.
If you switch to container you can still restore core. The addons you have to create yourself. Depending on the app you can restore the data for it.
Don't forget to write down your keys and reboot after restoring the backup.

tranquil summit
#

exciting lol

#

better not try to do this on a work night 😛

craggy hull
#

I'd just use a different disk to install PVE on if you have it. If anything goes wrong just use the old one again.
I usually always use two disks anyways to separate the OS from the guests.

tranquil summit
#

yeah i agree

#

writing right over my current HD, if and when things go wrong with the new OS ... that would be devastating 😛

tranquil summit
#

one question about installing proxmox - can i install through a different computer than the one i'm going to run the OS on? Meaning, run the installer on a different computer and install to the hard drive that i'm going to use, then take that hard drive and put it in the computer where it'll eventually be? that wont mess anything up, I assume (but i better double check)

craggy hull
#

In theory yes but I don't recommend that. Networking would not work without modification because the network names will be different for example.

tranquil summit
#

even if on the same network?

#

or you mean network interfaces

craggy hull
#

It's hardware related. The device name of the NIC will 99% be different.

tranquil summit
#

right, gotcha

#

thanks!

craggy hull
#

Very simple to fix by editing /etc/network/interfaces but still.

tranquil summit
#

right, still a thing i dont need to deal with lol

tranquil summit
#

sorry another question. i was running through the steps in the github page you linked, then got to the part where i install home assistant. i gave the IP address for proxmox 10.0.0.10 ... which is what i usually give home assistant. i shouldnt have done that, if I want home assistant to have that IP address, correct? Should have given it something else

craggy hull
#

Yes. Creating ip conflicts is not a good idea 😄
Pick an ip outside the DHCP range of your router.

tranquil summit
#

i changed the entries in /etc/network/interfaces and /etc/hosts according to the instructions here https://forum.proxmox.com/threads/help-with-changing-ip-address-reinstalling.55421/

and am rebooting

#

seemed to work ... not able to access the HAOS site yet though

craggy hull
tranquil summit
#

yes i saw those

#

i didnt quite understand all that

#

oh sorry, i meant, i started at the top and didnt understand everything

craggy hull
#

As for HAOS, check ha network info in the VM's CLI.

tranquil summit
#

thanks for that tip sheet, looks like i have a few more places to edit

craggy hull
#

HAOS can take a while to be fully up and reachable.

tranquil summit
#

yeah thats what i've noticed when i've tried running it in the past. will give it a minute. it has the IP 10.0.0

#

10.0.0.224 but not yet reachable

#

working ... but my dumb ass didnt save my most recent backup before doing all this lol

#

time to load up the old machine, get the backup off of it, restore from backup ....

#

actually

#

before i do tht

#

do you have any idea how i would add that RAID array into proxmox!? thats what started this whole thing lol

#
Last login: Sat Jan 18 15:05:52 EST 2025 on pts/0
root@proxmox:~# lsblk
NAME                     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda                        8:0    0 58.2T  0 disk 
├─sda1                     8:1    0  200M  0 part 
└─sda2                     8:2    0 58.2T  0 part 
sdb                        8:16   0  1.8T  0 disk 
#

can actually see it so this is a plus

craggy hull
#

Show me lsblk -o+FSTYPE,MODEL and lspci -nnk again.

tranquil summit
#

sure

#
root@proxmox:~# lsblk -o+FSTYPE,MODEL
NAME                 MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS FSTYPE  MODEL
sda                    8:0    0 58.2T  0 disk                     PERC H730P Adp
├─sda1                 8:1    0  200M  0 part             vfat    
└─sda2                 8:2    0 58.2T  0 part             ext4    
sdb                    8:16   0  1.8T  0 disk                     Samsung SSD 870 QV
├─sdb1                 8:17   0 1007K  0 part                     
├─sdb2                 8:18   0    1G  0 part /boot/efi   vfat    
└─sdb3                 8:19   0  1.8T  0 part             LVM2_me 
  ├─pve-swap         252:0    0    8G  0 lvm  [SWAP]      swap    
  ├─pve-root         252:1    0   96G  0 lvm  /           ext4    
  ├─pve-data_tmeta   252:2    0 15.9G  0 lvm                      
  │ └─pve-data-tpool 252:4    0  1.7T  0 lvm                      
  │   ├─pve-data     252:5    0  1.7T  1 lvm                      
  │   ├─pve-vm--100--disk--0
  │   │              252:6    0    4M  0 lvm                      
  │   └─pve-vm--100--disk--1
  │                  252:7    0   32G  0 lvm                      
  └─pve-data_tdata   252:3    0  1.7T  0 lvm                      
    └─pve-data-tpool 252:4    0  1.7T  0 lvm                      
      ├─pve-data     252:5    0  1.7T  1 lvm                      
      ├─pve-vm--100--disk--0
      │              252:6    0    4M  0 lvm                      
      └─pve-vm--100--disk--1
                     252:7    0   32G  0 lvm                      
sdc                    8:32   1    0B  0 disk                     UDISK
sdd                    8:48   1 29.9G  0 disk             iso9660 Type-C
├─sdd1                 8:49   1  242K  0 part                     
├─sdd2                 8:50   1    8M  0 part             vfat    
├─sdd3                 8:51   1  1.3G  0 part             hfsplus 
└─sdd4                 8:52   1  300K  0 part                     
root@proxmox:~# 
craggy hull
#

Ah, perfect. You can go to node > Disks > LVM-Thin and create yourself a datastore there.

tranquil summit
#

that second command puts out a lot of output

#

ok cool

#

where is "Node" under in the web ui

craggy hull
#

Hmm. My screen is too small to properly read that. It seems like you installed the OS onto the RAID.

#

Node is the name of your node 😄
Proxmox VE calls the hosts nodes.

tranquil summit
#

lmao

#

no i installed it onto SB2

#

sorry, sdb

craggy hull
#

Ah, sda is the RAID. Do you need the data on it?

tranquil summit
#

sda is the 58T RAID array

#

no, there's no data on it

#

its completely clean

craggy hull
#

Then go to node > Disks and wipe it first. After that proceed with the LVM instruction.

tranquil summit
#

i only set up the RAID10 hardware controller to use all 8 disks

#

in the bios

#

but no data on it

#

sounds good

craggy hull
#

It has partitions and the PVE tools below Disks want a empty disk.

tranquil summit
#

sorry i meant to have that cropped

craggy hull
#

Select sda and then click wipe.

tranquil summit
#

done

craggy hull
#

ZFS is kind of the best but it's not compatible with HW RAID hence we use LVM-Thin.

tranquil summit
#

yeah, i used ZFS on my QNAP before

#

ok so i've wiped the disk ...

craggy hull
#

You could also use IT mode if possible for your HBA and use ZFS RAID.

tranquil summit
#

Ah, perfect. You can go to node > Disks > LVM-Thin and create yourself a datastore there.

#

gotcha

#

creating

craggy hull
#

Note that this is a block storage only type. You can only store VM and CT disks there.

tranquil summit
craggy hull
#

Meaning you cannot store isos or backups on it.

#

At least not directly.

tranquil summit
#

what about basic multimedia, movies, etc

#

or ISOs that i want to save for use on other computers

#

not the ISOs i would need to run a VM

craggy hull
#

Nope. Your VMs can do that with a disk stored on there but not PVE.

tranquil summit
#

so if i allow the HAOS VM to access the tank disk

craggy hull
#

But... you can create a volume on the thin pool and format it as ext4 and mount it on the node. Then add that as Directory data store.

tranquil summit
#

hmmmmm 🤔

craggy hull
#

I can teach you that later.

tranquil summit
#

i guess what i'd like to do is be able to SMB into this disk from anywhere on my network, and also let the HAOS VM access this disk

#

kinda how i do with a different NAS on my network

craggy hull
#

What shall provide the network share? Another VM/CT? HAOS itself?

tranquil summit
#

just so i know, what does CT mean

#

virtual machine = VM, i dont know what CT means 😛

craggy hull
tranquil summit
#

perfect, thank you

craggy hull
#

Similar to docker in some ways but also not.

tranquil summit
#

hmmmm. i suppose ... i'm thinking about pros and cons

#

the pro of having it not through HAOS is that if HAOS is down for some reason, this will still be accessible in other ways

craggy hull
#

Lots of choice. The freedom I talked about.

tranquil summit
#

exactly

#

what do you suggest? reading the link you linked, it looks like containers are more lightweight than full VMs, so perhaps that's the best option?

#

i would have thought proxmox could provide the smb share itself though

craggy hull
#

The main issue with CTs is permission management. But that's only if you want to share a directory or device with the node and you don't need to here.

#

In theory it can but don't.

tranquil summit
#

yessir 🤣 🫡

craggy hull
#

You can also run TrueNAS as a VM but that wants real disks, not a HW RAID one.

tranquil summit
#

Ok, so i'm trying to understand one thing here. You said "The main issue with CTs is permission management. But that's only if you want to share a directory or device with the node and you don't need to here"

I'm not sure that I "don't need to here". this is all sorta new to me. Lets take a relatively simple use case, and please bear with me for any incorrect terminology i use, if i do

#

when i SMB into my NAS, this is what I see:

#

i think the first picture shows different shares on the disk, and the second simply shows folders on the share?

#

hopefully correct terminology

craggy hull
#

You can share directorirs on the node with a CT. The user ids inside the CT are shifted so you need to "unshift" them for specific ids of your choice. But you don't need to. You can just give it a normal disk on your new datastore.

tranquil summit
#

so the use case is, lets say I want to store movies in this RAID array. I want to be able to SMB into the share to add / delete / modify the files, but also allow HAOS to access the share / directories directly so it can have plex stream them

#

(diirectly obviously meaning, i have to give the HAOS VM access to the disk via Proxmox)

craggy hull
#

The idea is to give a CT a disk stored on the newly created data store and install software inside that CT to provide the shares. One option is cockpit linked above. Another option would be to create a openmediavault VM and use that. Another option would be to use the CT fileserver template.

tranquil summit
#

i see

#

i'm not familiar with any of those softwares

#

i've used TrueNAS but with the changes that happened recently and Truecharts dropping them, i kinda would rather not use that

craggy hull
#

I don't want to overwhelm you with options but an informed choice requires information. And the plan was just HAOS initially 😄

tranquil summit
#

hahahhahahaha

#

no you've been EXTREMELY helpful

#

trust me, i can't thank you enough

#

yes the plan was just HAOS initially, but it was HAOS in the service of doing all this

#

getting HAOS to talk to the RAID controller that it wasn't talking to

#

so proxmox installation became step 1 out of ... like, 42 steps 😄

#

if you dont mind sharing more, can you help me choose one of these CT softwares you mentioned, or go with a choice of VM instead if that's a better choice?

craggy hull
#

If you just want to provide network shares I'd follow the link above. That still gives you a lot of freedom. Most NAS software is very restrictive and opinionated.

craggy hull
tranquil summit
#

oh sweet

craggy hull
#

I gotta shower but I can tell you a little bit more later.

tranquil summit
#

oh of course, please! go

#

thanks again i'll read through this

craggy hull
#

Once you have that installed you can just do apt install cockpit-identities and so on and you will also get updates. It eludes me why they didn't do that.

tranquil summit
#

so ... based on the new URL, you gave me, how should I change the installation instructions from the original link?

#

(decided to re-install proxmox since i needed to get the HAOS backup anyway and i wanted to make sure the IP / hostname was set correctly from the get go)

#

use this?

curl -sSL https://repo.45drives.com/setup | sudo bash
sudo apt-get update
sudo apt install cockpit-file-sharing
craggy hull
#

Yup.

tranquil summit
#

sorry if this is a basic question, but does that command replace this:

apt install --no-install-recommends cockpit -y

or this

#Download Cockpit File Sharing
wget https://github.com/45Drives/cockpit-file-sharing/releases/download/v3.3.4/cockpit-file-sharing_3.3.4-1focal_all.deb
#Download Cockpit Navitator
wget https://github.com/45Drives/cockpit-navigator/releases/download/v0.5.10/cockpit-navigator_0.5.10-1focal_all.deb
#Download Cockpit Identities
wget https://github.com/45Drives/cockpit-identities/releases/download/v0.1.12/cockpit-identities_0.1.12-1focal_all.deb
#Install them
apt install ./*.deb
#It will complain about being unable to delete the deb files, so we will do that now
rm ./*.deb

or both

craggy hull
#

The latter.

tranquil summit
#

the other questions i have are,

  1. how do i use cockpit to create the samba share we were talking about earlier

  2. how do i connect my USB Z-wave device to the HAOS virtual machine?

  3. how do i connect my "tank" volume group to the HAOS virtual machine?

craggy hull
#
  1. There's a video linked in the article. Too many steps to explain.
  2. Add a USB device in the Hardware tab. Choose vendor.
  3. Go to Hardware, select the disk and move it to the data store you want. Unless you meant something different.
tranquil summit
#

let me try. i'm also having trouble using the home assistant installer script, it's giving me an error. but let me try rebooting and see if i get past that error

craggy hull
#

I'm actually not a huge fan of these helper scripts but people love them so 🤷

tranquil summit
#

i might have to try not using it

craggy hull
#

It also makes sense to add a serial port and enabling the guest agent. The script does some of that.

tranquil summit
#

yeah i gotta try something different. i've gotten this error 3 times now:

[ERROR] in line 448: exit code 0: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null
#

which is odd as i was able to do this without an issue when i first ran the script, before reinstalling proxmox

craggy hull
#

Seems like it fails at creating the EFI disk. I can't tell you much more. It discards all the output.

tranquil summit
#

no worries. you've been very helpful, i'll troubleshoot a few things

#

can always reinstall the whole thing from scratch if necessary, havent gotten very far yet in this process. and still have my SSD w/ HAOS on bare metal so am in a good spot 🙂

tranquil summit
#

I reinstalled the whole thing and got it functional again. now i'm trying to figure out this part:

3) how do i connect my  "tank" volume group to the HAOS virtual machine?

Go to Hardware, select the disk and move it to the data store you want. Unless you meant something different.

When I go to Hardware, i dont see the "tank" volume group i'm looking to add ... though I can see it under "lvm-thin" still

craggy hull
#

Have you added it as LVM-Thin in Datacenter > Storage?

#

Btw you need to add a disk on Hardware and then select the data store referring to tank as storage.

dense frost
#

i'm not using proxmox, but I actually ended up using HAOS's support for network mounts to mount a volume from my NAS to HAOS (even tho HAOS is running as a VM on my NAS). that's the simplest way to make a shared volume that can be seen both inside HA and by other computers accessing the NAS.

tranquil summit
#

thanks! Will check this out in a bit

tranquil summit
#

could i get some instructions on what it takes to install Home Assistant Container into Proxmox? I used the script to install HAOS, but want to try playing w/ HA Container as well and seeing what capabilities it has

craggy hull
tranquil summit
#

Knowing very little about docker ... does it matter where i put the compose.yml file, and do i have to do something every startup to get the "docker compose up -d" command work on startup every time? Like, this wont run by itself unless i have a debian service or crontab, correct?