I purchased a new $400 device from Umbrel and have gotten a couple hits of support over the past 30 days or so. Mostly unanswered emails and no relies. The one time tehy did connect with me, they can not fix the problem. I can not install anything. I can log in, see setting, apps store etc but NOTHING will install. I couldn’t even install the upgrade yesterday to 1.1 OS. It showed there was an update, tried installing. I WOULD LIKE A LITTLE support here PLEASE. I feel like thsi is a LOST CAUSE and should contact my credit card. Is this normal for Umbrel?? I thought it was a decent a responsible company when I signed up. At this point I don’t know what else to do. I really want to get a BTC node up and running.
2 Likes
whats in the logs?
Here is a section of system logs:
Apr 21 04:31:59 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:31:59 umbrel kernel: pcieport 0000:00:1c.6: AER: Corrected error message received from 0000:00:1c.6
Apr 21 04:31:59 umbrel kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 21 04:31:59 umbrel kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Apr 21 04:31:59 umbrel kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First)
Apr 21 04:32:02 umbrel umbreld[798]: [server ] GET /trpc/system.status
Apr 21 04:32:04 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:04 umbrel kernel: pcieport 0000:00:1c.6: AER: Corrected error message received from 0000:00:1c.6
Apr 21 04:32:04 umbrel kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 21 04:32:04 umbrel kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Apr 21 04:32:04 umbrel kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First)
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“State transition: inventory-update-retry-wait [Sync] → inventory-update [Sync]”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“Device unauthorized; attempting reauthorization”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“Failed to authorize with "": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“Reauthorization failed with error: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“Failed to submit inventory data: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“inventory submit failed: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“State transition: inventory-update [Sync] → inventory-update-retry-wait [Sync]”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“Handle update inventory retry state try: 2”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“Device unauthorized; attempting reauthorization”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“Failed to authorize with "": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“Reauthorization failed with error: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“Failed to submit inventory data: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=error msg=“inventory submit failed: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“RetryPollIntervalSeconds is not defined”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=warning msg=“RetryPollIntervalSeconds is not defined”
Apr 21 04:32:09 umbrel mender[543]: time=“2024-04-21T04:32:09Z” level=info msg=“Wait 1m0s before next inventory update attempt in 59.999994526s”
Apr 21 04:32:10 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:12 umbrel umbreld[798]: [server ] GET /trpc/system.status
Apr 21 04:32:15 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:20 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:20 umbrel kernel: pcieport 0000:00:1c.6: AER: Corrected error message received from 0000:00:1c.6
Apr 21 04:32:20 umbrel kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 21 04:32:20 umbrel kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Apr 21 04:32:20 umbrel kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First)
Apr 21 04:32:22 umbrel umbreld[798]: [server ] GET /trpc/system.status
Apr 21 04:32:25 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:30 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:30 umbrel kernel: pcieport 0000:00:1c.6: AER: Corrected error message received from 0000:00:1c.6
Apr 21 04:32:30 umbrel kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 21 04:32:30 umbrel kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Apr 21 04:32:30 umbrel kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First)
Apr 21 04:32:32 umbrel umbreld[798]: [server ] GET /trpc/system.status
Apr 21 04:32:35 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:40 umbrel umbreld[798]: [server ] GET /trpc/system.cpuTemperature
Apr 21 04:32:40 umbrel kernel: pcieport 0000:00:1c.6: AER: Corrected error message received from 0000:00:1c.6
Apr 21 04:32:40 umbrel kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 21 04:32:40 umbrel kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Apr 21 04:32:40 umbrel kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First)
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“State transition: inventory-update-retry-wait [Sync] → inventory-update [Sync]”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“Device unauthorized; attempting reauthorization”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“Failed to authorize with "": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“Reauthorization failed with error: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“Failed to submit inventory data: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“inventory submit failed: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“State transition: inventory-update [Sync] → inventory-update-retry-wait [Sync]”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“Handle update inventory retry state try: 3”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“Device unauthorized; attempting reauthorization”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“Failed to authorize with "": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“Reauthorization failed with error: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“Failed to submit inventory data: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=error msg=“inventory submit failed: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“RetryPollIntervalSeconds is not defined”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=warning msg=“RetryPollIntervalSeconds is not defined”
Apr 21 04:33:09 umbrel mender[543]: time=“2024-04-21T04:33:09Z” level=info msg=“Wait 2m0s before next inventory update attempt in 1m59.999981508s”
Now, I can’t explain it, BUT just now I l clicked to upgrade to 1.1 and IT DID! That has failed a dozen times before. I was getting excited and I have ZERO ideas why it worked this time BUT I still cannot install bitcoin core or any apps. I’m not real good at reading code. Is there more logs I need to send maybe?
1 Like
Is there anybody who can please help me? Let me know what logs to send? or any commands i can run maybe? I appreciate any help I can get. Thanks!
1 Like
i have no idea there.
does bitcoin just hang forever?
I wish i could help
Are you still having issues?
Obviously, YES!!!
I can’t even update the OS without fail.
I can’t believe no-one else is having these issues. I have a like new MAC latest version, latest everything. I have ZERO problems with nothing else.
It upgraded from 1.0 to 1.1 after about 15 tries the last time so i will keep tryting I guess…
Hmmm, I wonder if you can re-image the Umbrel Home or boot from USB to get past it.
Once you updated to 1.1, were you able to use the device as normal? You could try to get the Beta updates if you go to advance settings and opt into the beta OS updates.
no, it simply won’t install ANYTHING … including itself. I’m signed up for the betas. It tells me there is 1.2beta2 now and it will not install. OS works fine. I can navigate setting, app store or whatever no problem. Everyone seems to tell me it is the “docker” that is causing the problem but can’t seem to fix it. I was running .53 (or pre 1.0 version) for over a year running just the bitcoin node and this all happened once upgrading from that to the 1.0 version. This was from the exact same machine I am using today. It was running fine the say i upgraded, until after the upgrade. It didn’t run the node afterwards. It showed it but said it wasn’t running. I said OK, and reformatted the drive and started fresh and just planned on redownloading the blockchain but nothing after this point…
This could be part of the problem but lets start from the top.
From the logs, it seems there are two primary issues being highlighted (if I’m reading it correctly)
- PCIe Bus Errors: These errors are being corrected, but they may still indicate a hardware issue.
- Mender Authorization Errors: This seems to be an issue with the Mender service failing to authorize and submit inventory data.
Potential Steps to Troubleshoot and Resolve:
- Address PCIe Bus Errors:
- While these are corrected errors and might not be critical, they indicate some underlying hardware communication issue. Ensure that all hardware components are properly seated and functioning.
- Check for any available firmware or BIOS updates for your hardware.
- Investigate Docker Container Logs:
- As mentioned previously, check the specific logs for the Bitcoin Docker container to understand why it is restarting.
sudo docker logs bitcoin_bitcoind_1
- Review Mender Service Configuration:
- It appears that the Mender service is unable to find the
mender-device-identityscript. Ensure that this file exists and is correctly configured.
ls -l /usr/share/mender/identity/mender-device-identity
- If the file is missing, you may need to reinstall or reconfigure the Mender client.
- Check Docker Status and Resources:
- Ensure that Docker is running properly and there are no resource constraints (memory, CPU, disk).
sudo systemctl status docker
free -h
df -h
- Restart Docker Service:
- Sometimes, a simple restart of the Docker service can resolve issues.
sudo systemctl restart docker
- Update Docker Images:
- Ensure that you are running the latest version of the Bitcoin node Docker image.
sudo docker pull lncm/bitcoind:v27.0
sudo docker-compose up -d
- Reindex the Blockchain (if needed):
- If data corruption is suspected, reindexing the blockchain might help.
sudo docker stop bitcoin_bitcoind_1
sudo docker run -it --rm -v /path/to/bitcoin/data:/root/.bitcoin lncm/bitcoind:v27.0 bitcoind -reindex
- Check System Logs for Further Clues:
- Review additional system logs for more details on what might be causing the issues.
sudo journalctl -xe
By following these steps, you should be able to identify and potentially resolve the issues causing your Bitcoin node to restart and any related system issues.
I tried a few of these. I currently do not have botcoin node or nay apps installed as it will not install any app.
Here is a screenshot of what i ran. How do you install this “mender” service?
Seems like the docker is running, and there are no immediate issues with the Docker service itself.
Mender is an open-source over-the-air (OTA) software update manager specifically designed for connected devices, such as IoT devices. It allows for the efficient deployment of software updates to devices.
Before giving any further codes on the mender, check out these posts and see if those solutions work.
Also, if I’ve helped you any please consider liking my responses. #teamwork
I ran
curl -L https://link.umbrel.com/factory-reset | bash
and it did a bunch of stuff and setup like a new account
and I tried upgrading to beta again … same thing! 
Hmmm. Maybe get some more debug logs to see what else is going on.
Hi @cryptogoody, really sorry that you’re going through this saga of not being able to run umbrelOS. And thanks for stepping up and helping, @TheDecentralizedVet 
.
I’ll try and help get you sorted, but from what I remember of our last call there were some finicky networking issues specific to your local network + umbrelOS 1.x that we could not resolve. Are the three points below correct? This will help to make sure I’m not confused:
-
The original issue at the top of this post was for an Umbrel Home that you purchased. You were troubleshooting with Will on support and ended up returning the unit for a refund.
-
Later, I jumped on a call with you to try and troubleshoot the same issue to the one you were having with your Umbrel Home, but this was for a Raspberry Pi 4. The same issue occurring on both the Pi and the Home mean that this was very likely not an issue with the specific Home unit, but is actually a tricky networking issue with umbrelOS 1.x and your local network.
After our call did you end up installing umbrelOS 0.5.4 again on the Pi to see if the issue was isolated to umbrelOS 1.x?
-
Your recent responses to @TheDecentralizedVet starting here (first message shown below) are actually for a Raspberry Pi 4, correct? Not an Umbrel Home because you returned it?:
Obviously, YES!!!
I can’t even update the OS without fail.
I can’t believe no-one else is having these issues. I have a like new MAC latest version, latest everything. I have ZERO problems with nothing else.
It upgraded from 1.0 to 1.1 after about 15 tries the last time so i will keep tryting I guess…
If that's correct and you are currently running umbrelOS on a Raspberry Pi 4, then here are the steps we should try:
-
Let’s be careful not to run any Umbrel Home specific commands, like this one which specifically factory resets a Home. It will not do the correct thing to a Raspberry Pi:
I ran
curl -L https://link.umbrel.com/factory-reset | bashand it did a bunch of stuff and setup like a new account
and I tried upgrading to beta again … same thing!
-
Try installing the old umbrelOS 0.5.4 on the Pi:
- Use a wiped SSD
- Flash the 0.5.4 image onto the microSD card
- Connect ethernet to router and plug in Pi
- Are you able to install an app? The Transmission app would be a good one to test for install because it is small and won’t do anything once it’s done installing.
- Try installing the latest umbrelOS on the Pi:
- Use a wiped SSD
- Flash the latest umbrelOS for Pi 4 (umbrelOS 1.2.0 at the time I’m writing)
- Connect ethernet to router and plug in Pi
- Are you able to install an app?
- Once you try installing an app, regardless of whether or not it works, can you please download the logs and send them to me? I can then look at them again and try to come up with a path forward.
Here’s how to get the troubleshooting logs on umbrelOS 1.2:
- From the umbrelOS homescreen go to Settings > Troubleshoot > umbrelOS
- Click “Download umbrelOS logs”
- Send them to my email at nate@umbrel.com
I appreciate the shoutout @nmfretz! Loving the device and community so far!
1 Like