 Hello does anybody know how to delete grub from may main drive and install it on external?
 Cuz lubuntu installer installed grub on my main drive and lubuntu on external hardrive
 Do you prefer encrypted or unencrypted system on Lubuntu?
 ? Unencrypted
[06:06] <arraybolt3> @YarikMihalchik: I don't know of any way to uninstall GRUB from a drive. It shouldn't be a problem for it to be there at least for now (indeed removing it might make it tricky to boot whatever OS is on your internal drive!). However, installing GRUB to an external drive is relatively easy.
[06:07] <arraybolt3> @YarikMihalchik: Do you know if your system uses BIOS firmware or UEFI firmware? If not, run "ls /sys/firmware/efi" in a terminal and tell me if it shows you folder contents, or if it says "No such file or directory".
 Hi brothers And sisters
[13:51] <Igor> hello everyone
[13:52] <Igor> where can I find support on linux, I think I did something seriously bad to my machine and can not find a way out
 Did somebody knows whats the best compilation for my old small asus eee 1001px, n450@1667mhz, VGA intel 915, 2GB ram ddr2@667Mhz, SSD, cpuid limit disabled, sata ahci enhanced mode, changed WiFi modul (now sone Intel model, not ath9k). Boot booster activated and disk Will be parted for it. I need this machine for car obd diagnostics software. My idea is dual boot, Linux 32bit distro with wine And virtual box with XP or win7, second An
[14:06] <Igor> there is no one on ubuntu-helpteam
[15:05] <arraybolt3> Igor: This is a support channel for Lubuntu, there's also the #ubuntu channel.
 i just know it uses bios (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: Do you know if your system uses BIOS firmware or UEFI firmware? If not, run "ls /sys/firmware/efi" in a terminal and tell me if it shows you folder contents, or if it says "No such file or directory".)
[15:07] <arraybolt3> @MyRealLife444: I would suggest using Debian if you need a modern, supported Linux distro for use on 32-bit hardware. However, running a 32-bit version of Windows in VirtualBox will probably not work because VirtualBox no longer works without hardware virtualization support in the processor.
[15:07] <arraybolt3> @YarikMihalchik: OK, is there a "/boot" folder *on the external drive*?
 n450 is 64bit, but 1core, 2threads. And Qemu And etc..? (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: I would suggest using Debian if you need a modern, supported Linux distro for use on 32-bit hardware. However, running a 32-bit version of Windows in VirtualBox will probably not work because VirtualBox no longer works without hardware virtualization support in the processor.)
[15:09] <arraybolt3> @MyRealLife444: If you're on 64-bit hardware, that might work then. Let me do a quick search.
 Thx too much. Its not neccessary, but some days now i am at research 😅😅😅🤦‍♂️🤷‍♂️😆😆 (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: If you're on 64-bit hardware, that might work then. Let me do a quick search.)
[15:11] <arraybolt3> @MyRealLife444: Sadly, according to Intel, that CPU doesn't support hardware virtualization. Qemu will technically work, but it will be so miserably slow it will probably not be functional, and if it is functional it probably won't be worth using. Dual-booting XP or 7 alongside Debian or Lubuntu would probably be the best way to go.
[15:11] <arraybolt3> @MyRealLife444: If your car diagnostic software requires the use of Windows, you can use your old version of Windows for just running the car diagnostic, and then use Debian or Lubuntu for things that require an up-to-date OS (like Web browsing).
 If i produce some money work  And not research.... 😅😅😅 Netbook 2022 willst on my table now 😆😆😆😜 (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: If you're on 64-bit hardware, that might work then. Let me do a quick search.)
 Better then Linux is dual boot win + android. (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: If your car diagnostic software requires the use of Windows, you can use your old version of Windows for just running the car diagnostic, and then use Debian or Lubuntu for things that require an up-to-date OS (like Web browsing).)
 Because diag soft is only win And android
 😅
[15:14] <arraybolt3> @MyRealLife444: That might also work. The only good Android system for x86 that I know of is *really glitchy*, though.
[15:14] <arraybolt3> (Interestingly, though, you *might* be able to run an Android container within a Linux distro and do things that way.)
 I tested android x86, And it works too much better then linux
 yes (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: OK, is there a "/boot" folder *on the external drive*?)
 oh wait
 not a folder
 but partition
[15:15] <arraybolt3> @YarikMihalchik: That's fine.
[15:15] <arraybolt3> @MyRealLife444: Nice, sounds like that's your answer! You can install Windows first, then install Android-x86 alongside and have everything working.
[15:15] <arraybolt3> @YarikMihalchik: OK, so can you run "lsblk | nc termbin.com 9999" and send the link that prints?
 Not yet. I am testing now 9.0 rc2 32bit, And it works like charm (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: That might also work. The only good Android system for x86 that I know of is *really glitchy*, though.)
 oh wait im not in lubuntu rn lemme reboot (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: OK, so can you run "lsblk | nc termbin.com 9999" and send the link that prints?)
 Older mint distros works better than lubuntu 🤷‍♂️😉
[15:18] <arraybolt3> @MyRealLife444: This is the Lubuntu support channel. Sorry that Lubuntu didn't work for you, but this is off-topic for this channel and there is an active support session going on at the moment.
 Resolution with mint xfce is right 1024*600 at First boot. Lubuntu cant recognize. Same after updates And changing kernnelss
 Still bad : https://matterbridge.lubuntu.me/27efac01/file_6123.jpg
 Ok 😉 (re @lubuntu_bot: (irc) <arraybolt3> @MyRealLife444: This is the Lubuntu support channel. Sorry that Lubuntu didn't work for you, but this is off-topic for this channel and there is an active support session going on at the moment.)
 Thx for ideas And infos
 My research was la grande😄
[15:20] <arraybolt3> @MyRealLife444: No problem, glad to try and help!
 Nice day Boys!
 It says a https://termbin.com/cny3 (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: OK, so can you run "lsblk | nc termbin.com 9999" and send the link that prints?)
[15:24] <arraybolt3> @YarikMihalchik: Hmm... ok that's weird. What's at /media/a/NO_LABEL?
[15:24] <arraybolt3> Is that the boot partition on the external drive?
 Oh i mounted a boot volume (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: Hmm... ok that's weird. What's at /media/a/NO_LABEL?)
 There ia nothing here
[15:26] <arraybolt3> @YarikMihalchik: Hmm... ok this is somewhat confusing. Can you run "ls /boot | nc termbin.com 9999"?
 Https://termbin.com/c06w
[15:31] <arraybolt3> @YarikMihalchik: OK, that's encouraging. One moment, I'll see if I can figure out the command to install GRUB.
[15:32] <arraybolt3> @YarikMihalchik: Try running "sudo grub-install /dev/sdb" and see if that does the trick.
 Ok no errors
 Let me check
 Yay grub have been installed on external hardrive
 But what about grub on main drive?
 Is there a command for it?
[15:38] <arraybolt3> @YarikMihalchik: I see you already have Windows installed on the main drive (I believe). I really recommend that you *not* try to remove GRUB from it. It is now what is allowing your computer to still boot Windows, and removing it may cause trouble.
[15:38] <arraybolt3> (The only way I can think of that would safely remove it would be to install the Windows bootloader over the top of it, but that could still be risky.)
[15:39] <arraybolt3> (Besides, if you're using a supported version of Windows, it will probably overwrite the bootloader with its own bootloader at some point or another during a Windows update.)
[15:39] <arraybolt3> (If I'm remembering correctly, that is.)
 I use windows 7... (re @lubuntu_bot: (irc) <arraybolt3> (Besides, if you're using a supported version of Windows, it will probably overwrite the bootloader with its own bootloader at some point or another during a Windows update.))
[15:41] <arraybolt3> @YarikMihalchik: Hmm. Well... crud. Do you still have a Windows 7 installation disk somewhere?
[15:41] <arraybolt3> It has a tool that can be used to install the Windows bootloader.
 I can make one (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: Hmm. Well... crud. Do you still have a Windows 7 installation disk somewhere?)
[15:42] <arraybolt3> OK. If you really want to risk installing the original Windows bootloader instead of GRUB's bootloader, then making a Windows 7 disk would probably be the best way to proceed.
[15:42] <arraybolt3> (This isn't going to be a full reinstall of Win7, btw, we're just going to run a command from off the disk.)
 Ah
 The onstallation of it has stoped
 Wait
[16:16] <arraybolt3> @YarikMihalchik: You're still just making the Win7 disk, right?
[16:18] <arraybolt3> (Just making sure things are going correctly.)
 Yea (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: You're still just making the Win7 disk, right?)
 Its all fine
 Arraybolt3
 I just get a windows 7  disk
[18:22] <arraybolt3> @YarikMihalchik: OK, can you boot into the Windows 7 that's already installed on your system?
 I just shutdown from windows 7
 Wait I will load rn
 I can boot
 I’m booting rn
 Loaded in (re @lubuntu_bot: (irc) <arraybolt3> @YarikMihalchik: OK, can you boot into the Windows 7 that's already installed on your system?)
[18:25] <arraybolt3> Actually, I thought booting the installed Windows 7 was the right thing to do next, but a quick Google reveals that I was mistaken. Here's the instructions for installing the Windows 7 bootloader. (Make sure your Lubuntu external drive is **not** plugged into the computer before doing this!) https://superuser.com/questions/234824/how-do-i-install-the-windows-7-boot-loader
 Ok
[18:30] <arraybolt3> Igor: Please tell us about your problem here, where people who can help can see it. Not in DMs, please. :)
[18:31] <Igor> well, sorry about that, it was so far behind in chat, I did not want to write about it againn
[18:31] <Igor> but OK
[18:32] <Igor> so I managed to screw my computer
 Hi
[18:32] <Igor> I run a SBC and the machine uses a eMMC disk
[18:32] <Igor> this is basically flash memory in a form of a chip, eg soldered to the board
[18:33] <arraybolt3> Yeah. I've got some systems that use that kind of storage, so I know what you mean.
 Pls somebody know how i can make partitioning for lubuntu for boot booster And dual boot?
[18:33] <Igor> so with the constant updates coming for lubuntu the machine would occasionally fill its disk and lock me out during updates
[18:34] <Igor> so finally I decided to add another disk, a SSD on M2 slot
[18:34] <Igor> the big idea was to move the system to the SSD, to clone it and simply update the boot settings
[18:35] <Igor> well, since I am a noob, I decided to use Clonezilla
[18:35] <Igor> a SW, that can clone a disk
[18:35] <Igor> so I did it
[18:35] <Igor> BUT
 Tysm anyway I will install Ubuntu cuz of risk of when update It will update (re @lubuntu_bot: (irc) <arraybolt3> Actually, I thought booting the installed Windows 7 was the right thing to do next, but a quick Google reveals that I was mistaken. Here's the instructions for installing the Windows 7 bootloader. (Make sure your Lubuntu external drive is **not** plugged into the computer before doing this!) https://superuser.com/questions
[18:36] <Igor> I did not read untill the bottom of the tutorial, where it is clearly stated not to leave the original disk in the machine
 But at least I got my  windows t work
[18:36] <arraybolt3> Igor: Oh... and now both disks aren't bootable, I'm guessing.
 Ok bye see you next time... or not
[18:36] <Igor> so now I have 2 disks with BOOT records on it, two bootloaders, each disk its own, up untill recently both disks had same UUID, so a massive screw-up
[18:37] <arraybolt3> @YarikMihalchik: Glad you got a solution! See you later!
[18:37] <arraybolt3> Igor: OK, this doesn't sound too tricky to fix. Your SBC uses UEFI, right?
[18:37] <Igor> arraybolt3: actually it boots in both cases to "emergency mode"
[18:37] <Igor> yes, it does
[18:37] <Igor> it uses UEFI
[18:38] <arraybolt3> Igor: Nice. In theory, this should be a matter of changing UUIDs and cleaning up the EFI partitions and config files.
[18:38] <Igor> I mean I have 0 idea what that is, but yes, it uses it
[18:38] <Igor> :D
[18:38] <arraybolt3> Igor: One moment while I look up how to change a UUID...
[18:39] <Igor> I already changed this
[18:39] <Igor> each disk now has its own UUID
[18:39] <arraybolt3> Igor: 
[18:39] <arraybolt3> Igor: Oh, OK. Nice.
[18:39] <arraybolt3> Alright, can you boot the wonky system from a USB drive?
[18:39] <Igor> I edited /etc/fstab on both disks
[18:40] <Igor> yes, tried that too
[18:40] <Igor> heck, I managed to boot it from a read only disk, but it is no permanent solution
[18:40] <arraybolt3> Igor: OK, boot from the USB drive, connect to the Internet, and run "lsblk | nc termbin.com 9999" so I can see your drives and partitions.
[18:40] <Igor> I have a KALI distribution on USB stick
[18:41] <arraybolt3> (Send the link that command prints on the screen after running it. Also, the Kali USB should work fine for this.)
[18:41] <Igor> OK
[18:42] <Igor> hould be booted in a minute or so
[18:44] <Igor> .com/664d
[18:44] <Igor> cool feature
[18:45] <arraybolt3> Alright, I can see it. And... that's weird. Can you run "ls /sys/firmware/efi/efivars" and tell me if that says "No such file or directory", or if it spits a ton of gunk on your screen?
[18:46] <Igor> https://termbin.com/664d
[18:46] <Igor> yes, I did screw around it, so...
[18:46] <arraybolt3> It looks like somehow the EFI partitions are just... gone.
[18:47] <arraybolt3> I would expect there to be a small (~300 MB) partition at the start of each disk, so I'm doubting if your system actually does use UEFI or not.
[18:48] <Igor> yes, as predicted
[18:48] <arraybolt3> Igor: So the ls command above does print a whole ton of gunk?
[18:48] <Igor> for UEFI I can check if there is option in bios?ž
[18:48] <arraybolt3> Igor: That shouldn't be necessary. Just run "ls /sys/firmware/efi/efivars" and tell me what it does.
[18:49] <Igor> the command above says no such directory
[18:49] <arraybolt3> OK. What SBC is this?
[18:49] <Igor> UDOO x86
[18:49] <arraybolt3> (This will be handy for knowing how to troubleshoot this.)
[18:50] <arraybolt3> ...that is *so confusing.* OK, uh... can you run "sudo grub-install /dev/sda" and tell me what that does?
[18:51] <Igor> sure, but I belive I already have sda
[18:51] <Igor> but no matter
[18:51] <arraybolt3> Right. I'm interested in more what the command says more than what it does.
[18:51] <arraybolt3> I'm currently gathering info about the system to try and figure out what exactly it is and what went wrong so that I can try and figure out how to fix it.
[18:53] <Igor> command not found
[18:53] <arraybolt3> Tar.
[18:53] <arraybolt3> Hmm, ok. Try "sudo mount /dev/sda1 /mnt && cd /mnt/boot && ls | nc termbin.com 9999" and send the link.
[18:53] <Igor> try 'tar --help'
[18:54] <arraybolt3> LOL no my "Tar" was an expression of frustration, not a command :P
[18:56] <Igor> :D
[18:56] <Igor> sorry, was not sure
[18:56] <Igor> output is https://termbin.com/k7yg
[18:57] <Igor> Z
[18:57] <Igor> output is https://termbin.com/k7zg
[18:57] <arraybolt3> I am so sorry to interrupt but I have to go away from keyboard really quick, I'll be right back.
[18:57] <Igor> OK
[19:03] <arraybolt3> OK, I am back.
[19:03] <Igor> good to have you back
[19:04] <arraybolt3> OK, so Lubuntu isn't installed using UEFI after all. So it's probably a GRUB configuration problem, The Kali USB doesn't seem to have all of the tools to fix it, but we can probably finish diagnosing it here.
[19:05] <arraybolt3> Can you show the output of "cat /mnt/boot/grub/grub.cfg | nc termbin.com 9999"?
[19:05] <Igor> sure, just a minute
[19:07] <Igor> https://termbin.com/2tvu
[19:08] <Igor> the UUIDs are for the eMMC disk, I think
[19:08] <arraybolt3> Igor: Looks pretty normal to me, so I'm guessing it's probably just a matter of getting the GRUB configuration regenerated.
[19:09] <arraybolt3> OK, shut down Kali, remove the USB, boot the system from the NVMe drive, and enter recovery mode, since it will let you do that.
[19:09] <Igor> possibly?, but I would like to use the other disk
[19:09] <arraybolt3> Igor: Right, that's the intended end goal.
[19:09] <Igor> yes
[19:10] <arraybolt3> Once you're in Recovery Mode, select the "network" option with your arrow keys and press Enter, then select "root" and press Enter.
[19:10] <arraybolt3> That should give you a shell where we can finish fixing things.
[19:10] <Igor> rebooting
[19:13] <Igor> which image?
[19:13] <Igor> 193 or 192?
[19:13] <arraybolt3> Igor: Actually, can you drop to a GRUB rescue shell here?
[19:13] <Igor> I'm in
[19:14] <Igor> GNU GRUB version 2.02
[19:14] <arraybolt3> OK. Press "c".
[19:14] <arraybolt3> Does this give you a prompt where it says something like 'Minimal BASH-like editing is possible'?
[19:14] <Igor> yes, I did this step
[19:14] <Igor> yes
[19:14] <arraybolt3> Great. Run "ls" and tell me what that says.
[19:15] <arraybolt3> (It may be tedious to type across, you can take pictures and upload them to Imgur if you want.)
[19:16] <Igor> (hd0) (hd0, msdos1) (hd1) (hd1,msdos1) (hd2) (hd2,msdos2) (hd2,msdos1)
[19:16] <Igor> that is it
[19:17] <arraybolt3> OK, well... crud, that doesn't let me know which one's the eMMC and which one's the NVME. And it's a clone so...
[19:17]  * arraybolt3 does some quick checs
[19:17] <arraybolt3> *checks
[19:17] <arraybolt3> OK, run "search --no-floppy --fs-uuid --set=root 8e2f44c8-bbf2-4b80-b594-fc43f56f18cf". Type that big long number carefully, obviously.
[19:17] <Igor> if it is a clone, then none should have the SSD, right?
[19:18] <arraybolt3> Igor: My idea is, find the eMMC by using that search command, then we can select the *other* drive and be sure we have the NVMe. Then manually boot from it.
[19:19] <arraybolt3> Once that command is finished, run "echo $root" and tell me what it says.
[19:20] <Igor> hd0, msdos1
[19:20] <Igor> if you need UUID for other disk, I have it written
[19:20] <arraybolt3> Fantastic. Now run "set root=(hd1,msdos1)".
[19:21] <arraybolt3> (Also the UUID for the other disk will come in handy in just a bit.)
[19:21] <Igor> done
[19:22] <arraybolt3> Igor: Alright, now for the tricky part. Carefully type the following command:
[19:22] <Igor> :D
[19:23] <arraybolt3> linux /boot/vmlinuz root=UUID=<insert NVMe UUID here> ro quiet splash
[19:23] <arraybolt3> Replace <insert NVMe UUID here> as appropriate, making sure to not put a space between the = sign and the UUID.
[19:24] <Igor> UUID="something" ?
[19:24] <arraybolt3> Igor: No quote marks.
[19:24] <Igor> or no "" nedded?
[19:24] <Igor> OK
[19:24] <arraybolt3> It should look like root=UUID=8e2f44c8-bbf2-4b80-b594-fc43f56f18cf (but change the UUID to the NVMe one)
[19:26] <Igor> let me double check, last time I screwed this up
[19:28] <Igor> ha
[19:29] <Igor> boot/vmlinuz not found
[19:29] <arraybolt3> OK one moment...
[19:30] <arraybolt3> :facepalm: Sorry, I expected that to be there, but it's not.
[19:30] <arraybolt3> linux /boot/vmlinuz-4.15.0-193-generic root=UUID=<insert NVMe UUID here> ro quiet splash
[19:31] <Igor> OK
[19:31] <Igor> done
[19:31] <arraybolt3> Alright, next is:
[19:32] <arraybolt3> initrd /boot/initrd.img-4.15.0-193-generic
[19:33] <Igor> OK
[19:34] <arraybolt3> Alright, now run "boot" and tell me what happens.
[19:35] <Igor> it stopped when mounting usb 1-4
[19:36] <Igor> (initramfs)
[19:36] <Igor> bla bla bla
[19:36] <arraybolt3> Oh, ok, what's the message on the initramfs prompt?
[19:38] <Igor> [8.008183 usb 1-4: Product: UDOO X86
[19:38] <Igor> two more lines, last one is serial number
[19:39] <arraybolt3> Right, but it should say something like "Gave up waiting on root device <whatever>. Dropping to a shell!" or something along those lines.
[19:39] <Igor> next to initramfs is my USB key brand name
[19:40] <Igor> nope
[19:40] <Igor> write protect is off
[19:40] <Igor> write cache: disabled, read cache: enabled, doesn+t support DPO or FUA
[19:40] <arraybolt3> Hmm... *sigh.* This sounds trickier than I thought initially.
[19:41] <Igor> sdb: sdb1 sdb2
[19:41] <arraybolt3> So there's no indicator as to *why* it dropped to a prompt, you're just there?
[19:41] <Igor> I am not in prompt
[19:41] <Igor> it just freezed?
[19:42] <arraybolt3> You can't type anything?
[19:42] <Igor> nope
[19:42] <Igor> correction
[19:42] <Igor> I can
[19:42] <arraybolt3> OK, type "ls", press Enter, and see what happens.
[19:42] <Igor> I am in (initramfs)
[19:43] <Igor> did I pause?
[19:43] <arraybolt3> No, something went wrong and you're at a recovery shell where we can try to fix it.
[19:43] <Igor> dev
[19:43] <Igor> var
[19:43] <Igor> lib64
[19:43] <arraybolt3> OK, that's all I need to know.
[19:43] <Igor> run
[19:43] <Igor> bin
[19:43] <arraybolt3> Looks hopeful.
[19:43] <Igor> proc
[19:43] <Igor> root
[19:44] <arraybolt3> Igor: Crud, a bot just muted you for the rapid info. It will take about 60 seconds before it fixes. Sorry about that.
[19:44] <arraybolt3> OK, in the mean time, run "mount /dev/sda1 /root" and see if that returns any text on the screen.
[19:44] <arraybolt3> OK, it unmuted you.
[19:45] <Igor> unable to find mount
[19:45] <arraybolt3> ?!
[19:45] <arraybolt3> Welp, that's bad.
[19:45] <Igor> this is weird
[19:45] <arraybolt3> What happens if you just run "mount"?
[19:45] <Igor> if I type help, it is in there
[19:46] <Igor> rootfs etc
[19:46] <arraybolt3> OK, "ls /dev/sda1"
[19:46] <Igor> no, man
[19:46] <Igor> my error
[19:46] <Igor> says can't find -dev-sda1-root
[19:46] <arraybolt3> You need a space between /dev/sda1 and /root.
[19:47] <Igor> sorry
[19:47] <arraybolt3> No problem.
[19:47] <Igor> EXT4-fs (sda1): mounted filesystem
[19:48] <arraybolt3> OK, run "ls /root" and tell me if you see anything in there. (I don't need to know what's in there, though.)
[19:48] <arraybolt3> (Just if there's anything in there.)
[19:48] <Igor> full of stuff
[19:49] <Igor> vmlinuz
[19:49] <Igor> vmlinuz.old
[19:49] <Igor> swapfile
[19:49] <arraybolt3> NicE, ok stop.
[19:49] <Igor> dev
[19:49] <Igor> var
[19:49] <Igor> all the goodies
[19:49] <arraybolt3> OK, run "exit" and see what happens.
[19:49] <Igor> exit
[19:49] <Igor> sorry, wrong keyboard
[19:50] <Igor> kernel panic
[19:50] <Igor> attempted to kill init! exit code 0x100
[19:50] <arraybolt3> Bah, great. Sounds like Clonezilla threw some wrenches in the works.
[19:50] <Igor> or me
[19:50] <Igor> probably me
[19:51] <arraybolt3> At this point, it looks like it's corrupted your boot configuration and now can't find systemd anymore (which would explain why it was specifically mentioned in the kernel command line from the grub configuration).
[19:51] <arraybolt3> How exactly to fix this is currently beyond me. We could keep troubleshooting, but at this point I'd just back up your data to an external drive, and install Lubuntu from scratch.
[19:51] <Igor> hmmm
[19:51] <Igor> bu I cloned the disk
[19:52] <Igor> so my original eMMC should be still OK?
[19:52] <arraybolt3> Igor: 
[19:52] <arraybolt3> Igor: Depends on whether Clonezilla messed with it too or not.
[19:53] <arraybolt3> Igor: If you take the NVMe out entirely, can you boot again?
[19:53] <Igor> that is it, I am getting out the screw driver
[19:53] <Igor> :D
[19:53] <Igor> just a minute
[19:56] <Igor> no, it is still read only..
[19:56] <Igor> wait another minute
[19:57] <Igor> I think I changed UUIDs here too
[19:57] <Igor> and also screwed with grub
[19:57] <Igor> nope
[19:57] <Igor> still read only
[19:58] <Igor> reboot
[19:58] <Igor> I just reverted back to old UUID
[19:58] <arraybolt3> I'd probably be able to fix this if I was able to sit down at your computer and fiddle with it for a while, but remotely, and as broken as it is, this is going to be beyond difficult. I think you'll be up and running in 30 minutes to an hour if you backup and reinstall.
[19:59] <arraybolt3> (Maybe more than that depending on how complicated your setup works, but it should be faster than trying to recover this.)
[19:59] <arraybolt3> Make sure to get all of the data (including hidden files) from your home directory, so you don't lose things like browser passwords and the like.
[20:00] <Igor> dang
[20:00] <Igor> I had my cnc sw on it
[20:00] <Igor> well, we will fix this
[20:00] <arraybolt3> You'll be able to reinstall that, right?
[20:00] <arraybolt3> If not, then I see why you'd want to recover this instead.
[20:01] <arraybolt3> I'm just not exactly sure how - something seems severely messed up with it if it can't find your init anymore.
[20:01]  * arraybolt3 is very tired and has to go afk. You might find people with more energy and experience in #ubuntu who may be able to help with this.
[20:02] <Igor> I have to fix Rufus to bake an image on usb, and I have to look-up how to install on disk2, but this should be trivial
[20:02] <Igor> do not worry
[20:02] <Igor> you showed plenty
[20:03] <Igor> thanks, man
[20:03] <Igor> appreciate that
[20:17] <arraybolt3> Igor: Glad to try to help, sorry that we didn't end up with success yet. You've got this, good luck!
[20:18] <Igor> thanks, have a good day
[20:41] <Igor> dude, I managed to recover the original eMMC disk
[20:44] <Igor> and now
[20:44] <Igor> I am going to screw with it again :D
[21:18] <Igor> quick question for anyone
[21:19] <Igor> I have 2 disks, each has its own boot sector
[21:19] <Igor> how would I figure out which one I am runnin?
[21:20] <arraybolt3> Igor: Run "lsblk", it will tell you which disk has a partition mounted at /
[21:20] <Igor> thank you!
[21:38] <Igor> I think there is progress
[21:38] <Igor> the issue is still read-only fs
[21:38] <Igor> first fail is at Unit systemd-tmpfiles-setup.service
[21:42] <arraybolt3> Read-only fs? Do you use this system really heavily?
[21:42] <arraybolt3> Maybe the eMMC is failing,
[21:43] <Igor> I'll be brief: I am a complete moron
[21:43] <Igor> sorry about that
[21:43] <Igor> :D
[21:43] <Igor> I managed to boot from second disk
[21:44] <Igor> looking at /etc/fstab there is now different UUID that previously and I think this is the issue
[21:45] <Igor> I think system protects itself by loading into read-only mode if it does not find correct UUID in fstab
[21:45] <arraybolt3> Possibly, you can get read-write mode to kick in if the filesystem is mounted at / properly by running "sudo mount -o remount,rw /"
[21:46] <arraybolt3> I don't know if an fstab issue would cause a read-only mode, though.
[21:52] <Igor> the format in fstab is different?
[21:52] <Igor> ?đ
[21:52] <arraybolt3> Igor: If you mean different from how you use the "mount" command, yes, the formats of the "mount" command and the /etc/fstab file are quite different.
[21:53] <arraybolt3> You can use "man fstab" to see /etc/fstab file format info, and "man mount" to see info on using the mount command (though both are kinda tricky to get through, and since I'm right here, why bother?).
[21:54] <Igor> would this work? UUID="something" TYPE="ext4"
[21:55] <arraybolt3> Not sure, wanna show me the /etc/fstab file? "cat /etc/fstab | nc termbin.com 9999"
[21:55] <arraybolt3> And you're trying to set the UUID in the file to your NVMe drive's UUID, right?
[21:55] <Igor> I cant
[21:56] <Igor> because reqad-only the network does not start
[21:56] <arraybolt3> Oh. Shooey. OK, one moment...
[21:56] <arraybolt3> You'll want a line that looks something like this:
[21:57] <arraybolt3> UUID=<NVMe UUID here> / ext4 errors=remount-ro 0 1
[21:57] <arraybolt3> No quote marks around the UUID, and make sure it's right up against the = sign. Also, the spaces are important.
[21:59] <Igor> you just saved me an error
[21:59] <Igor> thanks
[22:00] <Igor> OK
[22:00] <Igor> edited the fstab
[22:00] <Igor> now reboot
[22:02] <Igor> still not
[22:02] <Igor> wait
[22:02] <Igor> did I choose wrong grub entry?
[22:13] <Igor> I did it!
[22:13] <Igor> but I do not know if it is permanent?
[22:13] <arraybolt3> What all did you do after modifying the fstab file?
[22:13] <Igor> my boot drive is now the SSD
[22:15] <arraybolt3> \o/
[22:15] <Igor> I have followed your instruction and in beginning the fstab was wrong
[22:16] <Igor> I corrected and rebooted, but the change in grub was gone
[22:16] <Igor> so I did it once again
[22:16] <Igor> and as the fstab was correct this time around, it booted into SSD
[22:16] <Igor> I do not know if it is permanent?
[22:17] <Igor> I will reboot now
[22:17] <arraybolt3> It should be permanent.
[22:18] <Igor> NOPE
[22:18] <arraybolt3> Hopefully. You might try booting from the NVMe and then running "sudo update-grub", then rebooting to make sure everything's still working right.
[22:18] <Igor> back to eMMC
[22:18] <arraybolt3> Blah. Lemme look at my GRUB file.
[22:21] <arraybolt3> Igor: Maybe you need to set your NVMe as the default boot drive in the BIOS.
[22:22] <Igor> well, where are all these changes happen, when I type in grub?
[22:23] <arraybolt3> If you're typing in a GRUB rescue prompt or some such from within GRUB itself, that's not permanent - you'd need to edit /boot/grub/grub.cfg from a booted OS for it to be semipermanent.
[22:23] <arraybolt3> Then once booted, you can use update-grub to rebuild the config (hopefully) correctly.
[22:27] <Igor> https://help.ubuntu.com/community/Grub2/Troubleshooting
[22:32] <Igor> I think it updates wron the grub.cfg
[22:32] <Igor> let us see
[22:33] <Igor> yes, it is wrong
[22:33] <Igor> back from 0 again
[22:51] <Igor> dang
[22:51] <Igor> must figure out how to make this permanent
[22:51] <Igor> but also must go to sleep
[22:51] <Igor> good night!