#.

164 messages · Page 1 of 1 (latest)

harsh sonnet
#

idk if perhaps it glitched in the install. the part when says remove usb stick sometimes throws squashfs read or I/O errors but that's nothing.

#

you may want to try 2 things:

  • verify the ISO
  • if the verify checksum matched, reinstall again, choosing the erase-and-install option
#

ok so no boot now at all?

#

just as that above pic?

#

can u boot the live usb to its desktop to troubleshoot, please?

#

also..

#

before doing that

#

be sure u boot the usb drive as a UEFI USB storage device

#

not just plain usb storage device

#

what do u see when u press the boot-menu key a second after power-on?

#

...

#

ok start the first option

#

ok now open disks in the start menu

#

in accessories

#

then click the hard drive or device u supposedly install onto,

#

and show a pic in landscape orientation fairly close zoomed to the full window

#

correction: a pic with the main partition that u installed onto showing

#

@pseudo swan

#

it will probably say "Type: Ext4"

#

k, show with p2 selected please

#

2nd partition

oak trench
#

if this is a fresh install and after installing it reboots to this screen, means the install went wrong somewhere. did you select custom partitioning or erase and install?

harsh sonnet
#

is that Kingston thing removable or permanently attached?

oak trench
#

I see you have /boot/efi /boot and / partitions encrypted with luks. im not entirely familiar with how it works, but you can try to mount it. then check it's /etc/fstab file.

harsh sonnet
#

the Kingston CY14 drive shown in the picture above

oak trench
#

usually sudo mount /dev/sda3 /mnt
cat /mnt/etc/fstab would work but again this is encrypted and I'm not familiar with it

harsh sonnet
#

fstab might be in p2, Lot

oak trench
harsh sonnet
#

no dont remove anything

#

note the difference between my last two posted pics

#

wait, @pseudo swan can u show a pic of partition 3 highlighted please, same style as before

oak trench
#

sorry, I meant to make the partition readable from your current system. that's called mounting, or whatever. the /etc/fstab file is a system file that says about configuration of partitions. your emergency shell complains about not being able to mount some filesystem it can't find.

#

can you press the little lock 🔒 button?

harsh sonnet
#

point is to try to unlock it

#

so u can mount it. idk if it gonna prompt for the LUKS encryption password

#

but as far as it stands, the UUID of ur blackscreen doesn't match neither p2's nor p3's so idk how that happened.

#

and that's why it won't boot.

#

i mean if u dont absolutely NEED encryption, try to install without.. it's way easier to troubleshoot/recover if issues

oak trench
#

yes, or opt in for /home encryption only

harsh sonnet
#

it would have asked and u say no

oak trench
#

don't check the use encryption box

harsh sonnet
#

or just do erase and install. dont go into advanced or anyhthing like that

#

just reboot or turn off the disks app

#

and relaunch the install

oak trench
#

you pressed the lock icon on luks partition and that's why it did that.

#

just reboot

harsh sonnet
#

yep. just a plain old default install

#

np. boot the live usb again

oak trench
#

did you verify your image btw?

harsh sonnet
#

then open disks app,

harsh sonnet
#

can sometimes have a download error or write erro

#

anyway click p2 in the disks app

#

this time the 2nd partition (of only 2) should be the ext4 one

#

then note its uuid (likely it's off from the blackscreen thing last posted) then click the play button under it, and visit the blue text link it shows by clicking it

harsh sonnet
#

press ctrl+L in the file manager

#

what's the path read?

#

go into the etc folder

#

then type fs to quickly locate the fstab file, then open it.

#

show it clear

#

ok all good

#

check your BIOS settings. if u see Fast Boot there, or Quick boot, turn it off

#

give it a go

#

no, after turning off fast boot in BIOS, save/exit it and give it a test reboot to the internal drive

oak trench
#

that means it can't access the partition or the drive correctly on startup. I been trying to read forums on if that happens and if it's easily solveable but can't find much useful stuff

#

last thing you can try is to regenerate initramfs maybe

#

in terminal type sudo su

harsh sonnet
#

also could that kingston drive be faulty?

#

I think it's one of those soldered-on jobs

oak trench
#

then mount your 2 partitions

#

mount /dev/sdb2 /mnt mount --mkdir /dev/sdb1 /mnt/boot/efi

#

then apt install arch-install-scripts

#

then arch-chroot /mnt

#

you now will load into your mint OS via terminal

#

then type update-initramfs -U

#

then update-grub

#

then show the terminal window

#

correct

#

sorry, I was unclear. mount --mkdir /dev...

#

yes just follow the rest of the command

#

mount --mkdir /dev/sda1 /mnt/boot/efi

harsh sonnet
#

ur live media is sda

oak trench
#

ohhhhhhhh. I am sorry I missed that

harsh sonnet
#

lsblk -o NAME,TYPE,SIZE,LABEL,FSTYPE,FSUSED,MOUNTPOINT

#

or just lsblk for crude version

oak trench
#

fixed the commands above. do umount -R /mnt before to unmount the usb drive

#

means executed properly

harsh sonnet
#

check again now with lsblk

#

alright so do the chroot mount thing that lot was mentioning.

#

using sdb

harsh sonnet
#

need a 1 in there

#

ur efi is in p1 thus, sdb1

#

lsblk and show

#

good

#

now the other for sdb2

harsh sonnet
#

then follow the rest

#

then tag lot when u get to his final sentence there

harsh sonnet
#

clearly not 😄

#

the whole messup was removing sda

oak trench
#

yeah I didn't think umount /mnt unmounts other stuff too. reboot and don't do any umount now

#

this is a pretty unusual issue. also make sure any setting related to RAID or other no standard thing in UEFI setup is disabled. last resort is to check out distros with a different base like arch or fedora

#

I'll be going to sleep now

harsh sonnet
harsh sonnet
#

did u reboot first and then do the mount sdb things?

#

n u need internet to be active in the live mode for this to get the packages

harsh sonnet
#

didn't you already reinstall 6 times?

#

I think you were on the right track before you left.

#

this is a pretty unusual issue. also make sure any setting related to RAID or other no standard thing in UEFI setup is disabled

#

lot@redhatlinux:~
—
Yesterday at 16:11
then mount your 2 partitions
mount /dev/sdb2 /mnt
mount --mkdir /dev/sdb1 /mnt/boot/efi
then apt install arch-install-scripts
then arch-chroot /mnt
you now will load into your mint OS via terminal
then type update-initramfs -U
then update-grub
then show the terminal window

#

I believe this is the right way to go.

harsh sonnet
#

at end of what?

harsh sonnet
#

prepend sudo

#

did it execute it?

#

just check this before going to BIOS.

#

lsblk -o NAME,TYPE,SIZE,LABEL,FSTYPE,FSSIZE,FSUSED,MOUNTPOINT

#

no check full

#

always case-sensitive too in linux

#

ok.

#

close the terminal and try a reboot. u may want to go into BIOS settings first

#

and check that the ubuntu loader is at top of boot list.

#

while ur there, check under storage or advanced if the internal drive is set to RAID or AHCI mode.

#

should be AHCI

#

alright

#

see if it loads

#

yeah it's something in ur BIOS for sure

#

only other explanation

#

show all the bios screens plz

#

in landscape view the camera

#

aight

#

in security category, it may help to add a uefi file as trusted

#

and if u can change secure boot mode from "standard" to some other option, perhaps audit or non-windows

#

also noticed it has hard drive ports. might be a 2.5 inch empty bay for an SSD option to consider

#

cuz that internal kingston UFS flash is being kinda weird

#

mkay

#

what did u prep the usb with?

#

well that computer is kinda useless atm in this state

#

u could try MX linux

#

in persistent mode

#

MX KDE edition

#

i didnt make an estimation as to whether it would install and boot. However persistent mode is a type of semi-installed setup, where the iso boots off usb, and all persistence data resides on hard drive (or also on usb)

#

I think frugal_persist_all (asks to save at shutdown) or frugal_persist-root would be a good choice.

#

thus u use the usb to start up the boot, (and mx) and from then on, all disk operations are carried out on the Kingston drive ( u can set the persist size to like 10 gigs just to start, growable later)

#

because the persist device can be any device

#

yes especially Acers

#

i would highly recommend to have a look at MX KDE, it's not far off from Mint. plus it has those great features exclusive to it and AntiX as the guy outlines in the vid.

#

it's a cousin of MX.. just more light n basic

#

shared developers

#

dolphin Oracle (the lead dev.) shows it off with the persist features in some YT vid. Though, he rambles kind of fast and/or drunkenly.

#

ur welcome.have fun exploring

pseudo swan
#

.

oak trench
#

@harsh sonnet is this solved?

#

ok why are people so fucking weird #🪵logs message

harsh sonnet
#

(and all OP messages deleted = LOL)