So I’ve got a friend that I’m helping to set up some external hard drives in his system. He had a working instance of Home Assistant with the OS running on bar metal. But he picked up a 9212–4e4i LSIHBA card and for whatever reason as soon as he plugs the HBA into his system and turns it on, he can see the OS boot locally, but he can no longer access the web interface from the URL. Does anybody happens to know what’s going on here?
#can’t open web interface with HBA connected
1 messages · Page 1 of 1 (latest)
To elaborate, even when he has the hard drives disconnected from the HBA, so it’s just plugged into a PCI slot, and nothing else is connected to it, this issue persists. If he shuts down the system, remove the HBA, and restart the system, you can access the web interface again.
Best to get your friend on here. So other than networking everything works. The CLI can be used? Have them type ha network info there.
I don't really understand why they want to use an HBA with HAOS.
But yes he said CLI is working local on the machine
I'm wondering because HAOS does not really support using multiple disks for data storage.
Oh really? Even if they’re just multiple SATA disks on the mobo?
I’ll have to ask him the use case because he honestly hasn’t said lol
My guess is the network device name changed due to adding a PCIe device and following this will fix it: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md#reset-network
Depends how their network was configured of course, but that should create a new DHCP based config.
See here how to log in: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md#using-nmcli-to-set-a-static-ipv4-address
Because they didn't follow the second link. they have to log in first. The > ha prompt is strictly for HA commands while rm and reboot are linux commands.
Wow. How small is that monitor?
I said the same thing lol 😂
Ok I think I’ve got him running it correctly
He’s gotten the connectivity issue sorted I believe. He’s just testing now.
Is there somewhere he can check system devices to confirm the HBA is showing up?
lspci.
Why don't they join here?
I would highly recommend to run this via the SSH addon as you can install additional software in it. The default tools are very neutered and don't display anything useful
apk add pciutils
lspci -vvk
He’s not on discord and thought this would be a two second fix lol
There's also this ☝️
The fix is very simple, yes, but requires some back and forth talking usually which is cumbersome through a proxy.
100%. I told him to get setup on discord so he can pop in here going forward. Community support is fantastic.
Is the ‘lspci’ command an HA command?
Nope.
He just wants to get to the point of having the disks show up so he can confirm everything works
I prefix all HA commands with ha even if you don't need the ha in the HA CLI.
Another way would be lsblk -o+FSTYPE,MODEL.
lspci shows PCI devices, lsblk block devices. Both useful here.
He ran lspci and it came back ‘not found’
I need to see their screen.
But again, use the command via the addon: #1293248595302023198 message
This only spews a few PCI ids. Not the names of the devices.
HAOS is NOT a normal linux OS.
True true got him on it 👍
I very much recommend virtualizing it: #hardware-archived message
Use HAOS for what you can, put other stuff that doesn't work well with it inside their own VM or container.
Ya that’s what I recommended. He’s starting to realize how in over his head he is I think
I appreciate your assistance and trying to help him though. Support by proxy is never great lol
He tried to install the pciutils addon but got another ‘not found’ error.
I confirmed the spelling this time lol.
These commands have to be run inside the SSH addon's command prompt.
They have to install a SSH addon first.
People generally don't run commands directly in the OS via keyboard and monitor so this is their way (and the recommended way) to run things.
So im the one Ezekial was attempting to help today.
Im sorry but I don’t understand what you mean by running the ssh addon.
Im really just trying to plug in a larger hdd to back up video feeds out of frigate. The hdd he gave me is sas so it required an hba card to access.
I have been advised in the past not to run HAOS via container as it can cause compatibility issues so it’s not my preferred option.
See here: https://github.com/home-assistant/addons/blob/master/ssh/DOCS.md
What compatibility issues?
So I bought a barebones pc to run HAOS as this is my first time using HA and this is meant to be an MVP test and learn. The drive I got is an hgst like enterprise drive that uses sas not sata. I actually didn’t know what sas was until I tried to plug this thing in so that’s on me for assuming a drive is a drive. Anyway my motherboard obviously doesn’t support sas so I spoke with Ezekial who offered me an hba card that has sata outputs that should in theory support sas via an adapter. I plugged it all in and through the troubleshooting you kindly offered via proxy above I was able to regain access to the pc via web. However there doesn’t appear in HAOS to be any good tools or support to allow the pc to see the hdd.
My understanding is that ssh is just a way to remotely access the cli. So I’m not sure that would offer additional tools to update any missing drivers or the like.
ssh is just a way to remotely access the cli.
Correct but HAOS itself is based on Build Root and has no package manager and using the OS CLI is discouraged: https://developers.home-assistant.io/docs/operating-system/.
You cannot install drivers and the only supported way to add software is through addons.
The SSH addon is based on alpine which has a package manager so you can install a version oflspcithat is not poop: #1293248595302023198 message
But addons are docker containers. They cannot do everything and you cannot installer drivers with it either.
As I was saying, HAOS is not a normal linux OS. If you want more freedom you should virtualize. Consider using the keyboard & monitor CLI only in emergencies and please read this whole thread from top to bottom because I explained most of this and more already. You are currently in the OS's terminal which is considered for developers/emergencies; https://developers.home-assistant.io/docs/operating-system/debugging/
Also see the table here for the differences between HAOS and container: https://www.home-assistant.io/installation/#advanced-installation-methods