Selfhosted

42055 readers

592 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Struggling to get PI OS working on a 3B (lemmy.ca)

submitted 1 day ago* (last edited 1 day ago) by Darkassassin07@lemmy.ca to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

Got a couple rpi 3Bs I'd like to use headless.

Downloaded 32bit pi os lite, flashed it to an sd card, powered on and did the initial setup (select keyboard layout, set first user+pass).

As soon as I'm dropped into a shell, I run 'sudo apt update' then 'sudo apt upgrade -y'.

Once these finish, I type 'sudo reboot'; the pi reboots, shows the rainbow splash, about a dozen lines of kernal boot messages then the video output dies and after a couple seconds the act light stops flashing too. Disconnecting power and powering it again does the same thing.

I don't think it's hardware failure as I get the same results with both 3Bs and with a 4B.

I don't know what to do from here.

I've spent the last 6 hours retrying this with both the 32 and 64 bit versions of pi os light. I can't get past the initial update/upgrade.

Anyone got any ideas? Anyone got a spare sd card, a pi 3B, and some free time to see if I'm just stupid somehow? I don't understand what I'm doing wrong.

/edit: RESULTS!

I can only assume this was a bad sd card. Tried a different card, with the exact same procedure: it finally booted after an upgrade.

Ran the update/upgrade again + a dist-upgrade and a couple more reboots. Up and running.

Excuse me while I go grab an image of that working card to file away.

you are viewing a single comment's thread
view the rest of the comments

[–] Darkassassin07@lemmy.ca 1 points 1 day ago (1 children)

didn't look like anything unusual, but I'll try and grab a photo before it disappears from screen. Waiting on 'apt upgrade' rn.
the devices MAC has a fixed DHCP lease. The IP becomes and remains unreachable as soon as I enter 'sudo reboot'.
this is a previously known to be good card (it had a working OS on it prior to todays messing around), but I'll try another for good measure.

[–] Deckweiss@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

Grab the sd card, and look at it on your pc. If windows can't read it (idk anything about windows), do so from another linux (live boot Ubuntu or something on your windows machine).

The journal log should be stored at either one of:

/var/log/journal/<machine-id>/*.journal

/run/log/journal/<machine-id>/*.journal

Post it's contents in full here via pastebin.com