07:43 <sopparus_> thanks

10:30 <BillTorvalds> I used the standard Raspberry Pi tool to "burn" LibreELEC onto my 32 GB memory card for my RPI4. It created two partitions: one very small one for just LibreELEC/Kodi, and one called "STORAGE". The "STORAGE" one ironically was extremely small, hardly enough to store anything beyond one or two pictures. So I used GParted to extend the STORAGE partition to use all the remaining space on the card (basically > 31 GB). Then I put a bunch of

10:30 <BillTorvalds> media on it. LibreELEC boots up and seems to be working as expected, with one major exception: try as I might, I just can't make it "see" the STORAGE partition. It's as if it doesn't exist to Kodi. I am able to browse and view media on a USB stick if I stick it in, so there is no issue with that. What to do?

10:31 <BillTorvalds> To make it clear: if I put the memory card into my Debian Linux PC (XFCE), I can browse the "STORAGE" partition as if it were just a directory on the card, and freely put files on there with no issues.

10:32 <BillTorvalds> This surprises me since it was the default behaviour (in fact, I was given no choice in the matter!) to create that "STORAGE" partition.

10:32 <BillTorvalds> I really didn't expect Kodi to not be able to "see" it; I assumed it would be auto-mounted and available.

12:02 <BillTorvalds> Yet another ghost town chatroom? :/

12:53 <vpeter> BillTorvalds: Burn image to sd card and boot. Second storage partition will be resized automatically.

13:35 <BillTorvalds> vpeter: I see. How come it's not done at the burning step, though?

13:35 <BillTorvalds> vpeter: And why doesn't LibreELEC/Kodi "see" it? Did I somehow "destroy" it by using GParted?

13:40 <vpeter> Burning is faster this way. And yes, you broke something with gparted which is not needed to run as I wrote above.

13:41 <BillTorvalds> vpeter: How would anyone magically know this?

13:41 <BillTorvalds> vpeter: When it was super small, there was no room to put any content on it.

13:42 <BillTorvalds> So obviously anyone would resize it.

13:42 <BillTorvalds> Still don't get why resizing it makes it break, though.

13:43 <LEBot> [slack] <CvH> "So obviously anyone would resize it." - Nobody 🙂

13:43 <LEBot> [slack] <CvH> this is and was really not a problem in the past

13:44 <LEBot> [slack] <CvH> the resize script is likely depending at something that has changed due the manual resize

13:45 <BillTorvalds> Sigh. Time to re-install the whole thing, I guess...

13:45 <BillTorvalds> And first let it boot, then shut down, then carry it back here, actually put media on it, and then go back to where the HDMI monitor is to watch it.

14:20 <LEBot> [slack] <chewitt> the number of times per-year when some user over-thinks the install process by “fixing” our does-not-need-fixing installer USB/SD image can be counted on one hand

14:20 <LEBot> [slack] <chewitt> it does happen though

14:21 <LEBot> [slack] <chewitt> the image is designed to self-expand from 32MB to 100% of available size on first use

14:22 <LEBot> [slack] <chewitt> something probably trashed /storage/.please_resize_me on the disk, and thus the first-run script(s) that look for that didn’t nuke/recreate the partiion

20:38 <BillTorvalds> Seems like LibreELEC created a bunch of dirs in STORAGE, and my files were "outside" of those.

20:38 <BillTorvalds> So I've moved them into "videos" or whatever now, so probably will show up next time.

20:38 <BillTorvalds> But not making it the full size and with the correct dirs right away is insanity.

20:38 <BillTorvalds> And feels like making it difficult and weird on purpose.

20:39 <BillTorvalds> I often get that feeling. That various projects that claim ease of use have some really inane default behaviour which bypasses all the ease of use.

21:01 <mack> Summary of angry person: They burned the installation image, messed with it before booting, then complained it didn't install correctly.