[00:54] <RubixDebian> hello
[00:55] <devslash> When upgrading Ubuntu, can you go from 22.04 directly to 23.10 or do you have to upgrade 22.04 -> 23.04 -> 23.10 ?
[00:58] <rbox> https://askubuntu.com/questions/1489052/how-to-migrate-from-22-04-lts-to-23-10
[00:59] <devslash> ok thanks I guess I have to do each upgrade in the upgrade path
[01:25] <webchat16> Hi, I'm running Ubuntu 22.04 on a Raspberry Pi. I can't boot into my normal interface, I'm stuck within initramfs. I've checked Stack exchange and the forums and tried the obvious, but nothing has seemed to work so far. Can anyone help guide me into figuring out what I can do from this interface and what my options are?
[01:26] <rbox> what does the output look like
[01:27] <webchat16> Basically it's just showing BusyBox v1.30.1 and a prompt for (initramfs)
[01:28] <rbox> theres more than that...
[01:28] <webchat16> Sure, I think the most unique line on my screen is "Target filesystem doesn't have requested /sbin/init."
[01:29] <rbox> sounds like your rootfs is corrupt
[01:30] <webchat16> Is there a way to fix that from this initramfs prompt? I can't seem to get a live CD running over this, no GRUB loads up.
[01:32] <arraybolt3> webchat16: Let's start by mounting the primary drive.
[01:32] <arraybolt3> `ls /dev/mmcblk*`
[01:32] <arraybolt3> `ls /dev/sd*`
[01:32] <arraybolt3> do either of those commands show anything?
[01:33] <webchat16> Yep, mmcblk has 0, Op1, and Op2
[01:33] <webchat16> I believe there's a message above (I can't scroll up either) about mmcblkOp2
[01:34] <arraybolt3> hmm, that may have been important, probably an fsck notification
[01:34] <arraybolt3> fsck /dev/mmbclk0p2
[01:34] <arraybolt3> (if it warns that it may cause damage, do not proceed)
[01:34] <webchat16> Read-only file system while trying to open. Disk write protected; use the -n option to do a read-only check of the device.
[01:34] <arraybolt3> dead SD card.
[01:35] <webchat16> Ah, okay.
[01:35] <arraybolt3> It's locked itself into read-only mode almost certainly.
[01:35] <arraybolt3> Flash a new one with Ubuntu and boot from that.
[01:35] <arraybolt3> Then put the old card in a card reader and copy your data off.
[01:35] <JanC> can't be dead or you wouldn't get that far, but might have some errors indeed
[01:35] <arraybolt3> JanC: Well technically it's not *dead* dead, but it can't be safely written to any more. That's the only time (that I know of) when these sort of devices go read-only.
[01:36] <webchat16> So I probably can't even flash a new OS on it?
[01:36] <arraybolt3> Correct.
[01:36] <JanC> the filesystem might be readonly because it wasn't unmounted cleanly
[01:36] <arraybolt3> You should be able to access the data that's still on it though.
[01:36] <arraybolt3> JanC: He got the read-only notice from fsck, not mount.
[01:36] <arraybolt3> fsck would have fixed it if it were an unclean unmount issue, or at least have tried to.
[01:37] <webchat16> Yeah, I ran through a couple of fsck commands as well and nothing changed
[01:37] <JanC> IIRC some cards can be made read-only also
[01:37] <webchat16> Dang, okay, thank you! I have another card that's working so at least now I know.
[01:38] <arraybolt3> SD cards are easy to burn out when using them to store an OS, so it's not that surprising.
[01:38] <webchat16> Is there a better alternative for a 24/7 Pi?
[01:38] <arraybolt3> You might look into an industrial SD card if you use this regularly, they theoretically can last quite a bit longer.
[01:38] <webchat16> Ah, good advice.
[01:38] <JanC> webchat16: did you check that the SD card doesn't have a physical read-only switch?
[01:39] <webchat16> I'm not sure what that is...
[01:39] <arraybolt3> Sometimes full-size (not micro) SD cards have a switch on the side that can be used as a write-protect.
[01:39] <arraybolt3> I've never seen one on a micro SD card, but they might exist.
[01:39] <webchat16> Oh nope, this is micro.
[01:39] <webchat16> And it completely makes sense that it burned out, this is my first 24/7 computer
[01:39] <pragmaticenigma> webchat16: I wouldn't recommend Ubuntu for a 24/7 Rpi "server" ... Raspberry Pi OS, or DietPi are both Debian and have the same packages (possibily differing versions) but are setup to write less logging to the storage. Another option is to flash the SD card with the boot partition and have the system partition attached through USB
[01:40] <arraybolt3> There's also ways to mount the root partition as read-only to preserve SD card life when using RPiOS. Might work on Ubuntu too.
[01:41] <JanC> can also make SD cards read-only through software, I think
[01:42] <arraybolt3> https://superuser.com/questions/956232/how-to-make-sdcard-really-read-only that's probably filesystem-level sadly, even the physical write protect switch apparently can be bypassed on SD cards.
[01:42] <pragmaticenigma> JanC: nope, only way an SD card can be made readonly is if it's the original formfactor with the Readonly switch located on the side
[01:43] <JanC> it might be a filesystem parameter indeed
[01:43] <pragmaticenigma> JanC: That's not readonly, as the host device/OS would be at liberty to honor such things.
[01:44] <JanC> yes, of course
[01:44] <arraybolt3> I wish they made SD cards more durable, or at least put a warning on them that they're liable to burn out. I have literally piles of dead SD cards here all killed by dash cameras.
[01:45] <arraybolt3> or I wish the "industrial" ones were more popular :P
[01:45] <JanC> probably cost a lot more too?
[01:46] <arraybolt3> meh, only a couple bucks more depending on who you buy from
[01:46] <pragmaticenigma> it's not durability as much as just fundamental physics. To "write" a bit to a cell, you have to use very highvoltage to overcome a gate and effectively "squirt" electrons into the cell. Overtime, the material of the cell breaks down
[02:19] <brightside777> will 24.04 be lts?
[02:20] <arraybolt3> yes
[02:20] <brightside777> k thanks
[02:56] <Sir_Leto> lately I've had really high ram usage that can't really seem to be explained, how can make sure it's just that caching behavior has changed and not that my device has malware or something? https://dpaste.org/9TZjW please let me know if you want more output or if there's something else I can check
[03:00] <sarnold> Sir_Leto: that feels pretty weird, I think I would have expected way more buff/cache here
[03:02] <sarnold> Sir_Leto: given that a lot of this looks like you'll have *lots* of memory sharing candidates, the smem tool in the smem package might give you a different way of looking at your memory usage that's more useful to figuring out what's going wrong here
[03:03] <sarnold> Sir_Leto: it's also possible that you've got a kernel memory leak; those can be *really* hard to track down; checking the output of slabtop from the procps package can help..
[03:05] <sarnold> if you're absolutely desperate for more ram, the old drop_caches interface might be worth a try. the free output suggests that won't actually get much, but iirc that also drops dnodes, and that might not be counted in the buff/cache column. I can't recall :(
[04:14] <Sir_Leto> https://dpaste.com/A8NDQ5TYD
[04:26] <Sir_Leto> sarnold, so is guess it's all cache? https://dpaste.org/KR6tu
[04:27] <Sir_Leto> 2032912k isn't very much actually
[04:41] <Sir_Leto> here is more smem output https://dpaste.com/C694ASJ9U
[05:10] <Psil0> hey trying to shutdown my computer first time i saw this message ever, Operation inhibited by "User" (PID 4167 "gnome-session-b", user User), reason is "user session inhibited".
[05:10] <Psil0> why do i have two sessions and why is it Inhibiting my main user, from shutting down the computer?
[05:10] <Psil0> Please retry operation after closing inhibitors and logging out other users.
[05:10] <Psil0> i am getting this wierd message, how do i avoid this since first time i am seeing this on my distro
[08:39] <hid3> Greetings everyone. I have a large LVM volume (nearly 9 TB). It consists of small block devices, 50-200 GB in size, some are larger. Each block device has a partition (/dev/sdx1) and LVM on top of it. I don't think this is neat setup, so I'd like to tidy up. I want to extend one block device and use `pvmove` to get rid of dozen block devices. I've increased size of one of my block devices. How should I increase the partition size?
[13:37] <cbreak> hid3: you can change partition sizes with parted or gparted
[13:38] <cbreak> (among many others)
[13:38] <cbreak> (fdisk works too)
[14:18] <GolDust> ciao
[14:47] <BluesKaj> Hi all
[15:26] <Guest21> hello
[15:28] <jailbreak> bear_: stop it.
[15:28] <Guest21> sorry
[15:28] <jailbreak> Wasn't talking to you.
[15:28] <Guest21> i am bear
[15:28] <bear_> i am bear
[15:29] <leftyfb> Guest21: bear_: what can we help you with?
[15:30] <Guest21> im just lurking i guess was reading ubuntu docs about how to use irc
[15:31] <leftyfb> Guest21: ok, just keep in mind this is a support channel. Let us know if you have any Ubuntu support questions
[15:31] <bear_> k thx
[17:52] <GrandPa-G> Having trouble installing mosquitto. Keep failing to start with Unable to open pwfile "/etc/mosquitto/passwd.  The file is there, I did the create user/password correctly. The conf file has password_file correct. anonymous  false. What now?
[17:53] <rbox> namei -l /etc/mosquitto/passwd
[17:53] <rbox> and how are you starting it
[17:54] <GrandPa-G> https://dpaste.com/66TJTXSZU for config file. I start with systemctl
[17:54] <GrandPa-G> -rw------- root root passwd
[17:55] <rbox> the output of namei -l isn't 1 line...
[17:55] <rbox> and how are you running systemctl
[17:55] <GrandPa-G> I thought that might be all you need. Just a sec
[17:56] <GrandPa-G> https://dpaste.com/CNZE79H87
[17:58] <GrandPa-G> sudo systemctl restart mosquitto
[17:58] <rbox> what does systemctl cat mosquitto say
[17:59] <GrandPa-G> https://dpaste.com/5DH727XZR I just reinstalled a few minutes ago as I was having same issue ever since I tried to add password
[18:00] <GrandPa-G> The only change was to create the user/password and make the conf file the way it is now.
[18:01] <rbox> it looks like its running as the user mosquitto
[18:01] <rbox> and that user can't read that password file
[18:01] <GrandPa-G> why would a fresh install do that. I didn't think of that, shouldn't it run as root?
[18:02] <rbox> nothing should run as root
[18:02] <GrandPa-G> should I just change ownership of passwd file to mosquitto?
[18:03] <rbox> yes
[18:05] <GrandPa-G> It still got error trying to start, but it is address in use. I am doing reboot to clear everything up
[18:06] <GrandPa-G> I am surprised none of the install tutorials seem to mention the need to change file ownership
[18:09] <GrandPa-G> rbox, thanks, that did it. Also, it wouldn't start with the listner 1883 in the conf, complained already in use.
[18:09] <rbox> ss will tell you wahts listening on that port
[18:12] <GrandPa-G> now I can't get connection from another lan computer. I must have something still not quite correct. Thanks again
[18:15] <GrandPa-G> got it, the listner has to come before password line in config file.
[19:01] <rjwiii> Ubuntu 22.04 - System76 Thelio ... How do I block a single bluetooth device?
[19:16] <rjwiii> my work laptop keeps trying to establish a bluetooth connection to my Ununtu box ... How can I block this?
[19:19] <jailbreak> rjwiii: turn off Bluetooth.
[19:19] <rjwiii> jailbreak: is that the only way?
[19:21] <jailbreak> rjwiii: would be the easiest way, yes.
[19:32] <rjwiii> jailbreak: Is there a way to block just a single device?
[19:33] <pragmaticenigma> rjwiii: no
[19:34] <pragmaticenigma> though I'm not sure why you would be repeatedly prompted for a connection, unless something is in discovery mode
[19:34] <leftyfb> rjwiii: bluetoothctl block <BT address>
[19:35] <rjwiii> pragmaticenigma: hmmmmmmm ... Maybe I can turn off discovery on the work laptop ...
[19:35] <pragmaticenigma> those would be my first steps before blocking devices
[19:37] <pragmaticenigma> kind unsettling to me that a work issued machine would be doing that. And if you don't need bluetooth rjwiii , disable it. It's secures a system to not have that running if you're not actively using it anyways
[19:39] <rjwiii> pragmaticenigma: Unsettling to me, too ... it shows as "Not setup" on my Ubuntu machine ... I'm not going to set it up.
[20:39] <nuovolnx> Hi everyone, I intend to buy a smartphone and then replace Android with Ubuntu. Can you recommend a cheap smartphone? Is it possible to use WhatsApp? Taking photos?
[20:40] <daft> nuovolnx, it is possible but you need a phone that is compatible.
[20:41] <nuovolnx> daft: could you advise me something?
[20:42] <jailbreak> nuovolnx: maybe pinephone. But off topic either way.
[20:43] <daft> https://www.online-tech-tips.com/smartphones/guide-install-ubuntu-touch-on-an-android-phone/
[20:43] <nuovolnx> jailbreak: works fine with ubuntu touch?
[20:44]  * jailbreak shrugs
[20:44] <jailbreak> No idea, sorry
[20:44] <daft> pinephone was plasma i tought.
[20:44] <jailbreak> Plasma is a de, no?
[20:45] <daft> yea. of kde.
[20:46] <nuovolnx> with pinephone it's difficult than find a cover
[20:47] <pragmaticenigma> nuovolnx: This channel is dedicated to providing support for the Ubuntu desktop OS. You can try asking about Ubuntu Touch in the #ubuntu-touch channel
[20:48] <nuovolnx> pragmaticenigma: thank you