#How to load the kernel
185 messages · Page 1 of 1 (latest)
I'm afraid your partitions are no more.
🥲
can you run fsck from the live usb?
K
not sure if that'll do anything, but worth a try I guess
this is your live usb?
be more specific. what is compatible mode?
One of the 2 options in live usb
fsck /dev/[your drive and partition, so example sda2]
that won't do anything. at most, you could try recovery from your installed system (in the grub menu under advanced options) but am not sure if there's anything useful in your case
space.
well that seems bad
can you open disks app and show me what you see?
this @brittle shoal
that's your live system, no worry
never seen such a cluttered partition layout before
that's a horrendous layout.
well only things I can try of right now would be to rebuild initrd and boot-repair
@sacred fox can you boot to windows normally?
repeat with sda8, and sda10 . use sudo everytime
would just data partitions make you unable to boot? I guess he should also check the efi partition
sda 10 is taking time
sudo fsck /dev/sda10
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda10 primary superblock features different from backup, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
still loading
you might want to invest in an SSD drive. even 256gb
sudo fsck /dev/sda10
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda10 primary superblock features different from backup, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda10: 1199740/3276800 files (1.0% non-contiguous), 11452827/13107200 blocks
////////////////////////////////////////////
mint@mint:~$ sudo fsck /dev/sda1
fsck from util-linux 2.37.2
fsck.fat 4.2 (2021-01-31)
/dev/sda1: 237 files, 18651/65536 clusters
mint@mint:~$ sudo fsck /dev/sda2
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
mint@mint:~$ sudo fsck /dev/sda3
fsck from util-linux 2.37.2
mint@mint:~$ sudo fsck /dev/sda4
fsck from util-linux 2.37.2
mint@mint:~$ sudo fsck /dev/sda5
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda5: clean, 553932/8208000 files, 6985830/32768000 blocks
mint@mint:~$ sudo fsck /dev/sda6
fsck from util-linux 2.37.2
mint@mint:~$ sudo fsck /dev/sda7
fsck from util-linux 2.37.2
mint@mint:~$ sudo fsck /dev/sda8
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
Games: clean, 35294/4924800 files, 7489430/19660800 blocks
mint@mint:~$ sudo fsck /dev/sda9
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: No such file or directory while trying to open /dev/sda9
Possibly non-existent device?
mint@mint:~$ sudo fsck /dev/sda10
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda10 primary superblock features different from backup, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda10: 1199740/3276800 files (1.0% non-contiguous), 11452827/13107200 blocks
mint@mint:~$ sudo fsck /dev/sda11
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: No such file or directory while trying to open /dev/sda11
Possibly non-existent device?
mint@mint:~$ sudo fsck /dev/sda12
fsck from util-linux 2.37.2
mint@mint:~$ sudo fsck /dev/sda13
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: No such file or directory while trying to open /dev/sda13
Possibly non-existent device?
mint@mint:~$
there is no 9 and 11 really
i was typing with the flow
dont fsck anything but fat and ext4
ok
mint@mint:~$ sudo fsck /dev/sda1
fsck from util-linux 2.37.2
fsck.fat 4.2 (2021-01-31)
/dev/sda1: 237 files, 18651/65536 clusters
mint@mint:~$ sudo fsck /dev/sda10
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda10: clean, 1199740/3276800 files, 11452827/13107200 blocks
mint@mint:~$ sudo fsck /dev/sda8
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
Games: clean, 35294/4924800 files, 7489430/19660800 blocks
mint@mint:~$ sudo fsck /dev/sda5
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda5: clean, 553932/8208000 files, 6985830/32768000 blocks
mint@mint:~$
should i try to open windows?
done
yes, and do a chkdsk for every drive letter
ok
any progress?
I started with d since it only had 3 gb data, it is still not finished
its doing something right?
hmm
that's a lot for 3 gb.
you might want to run boot-repair from the live usb after this one is completed
otherwise, not sure if checking C will also do anything. you might have to reinstall
and if you decide to, ffs make your partitioning a bit better. don't create that many partitions. just keep windows C partition, and make a single root partition for Linux (or if you want seperate /home)
i don't have any experience with chkdsk. you might want to ask this on a windows related server, and tell that your chkdsk has been running for this long.
or if you don't want to wait and don't mind having all your data wiped from that 3gb partition, just give it up
you can run boot-repair as last resort. if that doesn't work, regenerate initrd. if that doesn't work, wait until someone has a decent idea or just give up and reinstall.
well, these things can take literal days
first time seeing less than 100 %use on my lap
you can also use crystaldiskinfo while on windows
might say something nice
'crystaldiskinfo' is not recognized as an internal or external command,
operable program or batch file.
nvm installed
is it bad?
@brittle shoal
i will do c when going to sleep as it will probably take a long time
i mean, its status is caution, but it doesn't seem like it's failed already
but I would replace it when you can
it'll probably fail sooner or later
get a 256gb sata if you really can't spare more money, but even 1tb ones are fairly cheap nowadays
and according to some nerd
"multiple read errors, LOTS of seek errors (0x2b = 43 so far), lots of uncorrectable errors (0x2a1 = 673), shitton of command timeouts (0x60014 = 393236) and it was used a lot"
he's saying it's cooked
rest
u dont need to do a surface scan with /r.. just log to c drive in admin-command prompt (eg. type c: n enter) then just do chkdsk /f
surface scan takes hours or days
so just chkdsk /f, not chkdsk C: /f
u log to c first
C:\WINDOWS\System32>
ok
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
it basically means itll check when you reboot
@sacred fox any progress?
Restarted normally, windows is working fine
.
I need to try to recover data i guess
Uhm, will the sda name of the home folder change?
Looking through advanced linux option
aha. that's a nice screen.
I believe you should just regenerate initrd
@sacred fox did you have this error before?
you need prepare a Linux mint usb drive
i was looking through the advanced options (the second one while booting)
how to do that
i have it
if you don't mind to reinstall it, it's faster
mount /dev/sda5 /mnt
mount /dev/sda1 /mnt/boot
sudo chroot /mnt (you now use your system from the live usb)
update-initramfs -u (I'm pretty sure that's the correct command and will do it correctly, if not then someone please correct me)
then you can reboot
boot mint thru advanced options
if it doesn't work, then boot to the usb drive and run boot-repair, and then do recommended repair. If that doesn't work, you can press e when you have the advanced option that got you to the init error before (or if boot-repair fixes it, the default option) selected, and send the contents of it here)
Sudo chroot/mnt gives no directory/bin /bash
try again but add final slash>> mount /dev/sda5 /mnt
mount /dev/sda5 /mnt/
if that doesn't work, make a temporary mounting directory in the live environment:
sudo mkdir /mnt/rootsystem
then mount /dev/sda5 /mnt/rootsystem
then sudo mkdir /mnt/bootpart
then mount /dev/sda1 /mnt/bootpart
then sudo chroot /mnt/rootsystem
sudo chroot /mnt/rootsystem
chroot: failed to run command ‘/bin/bash’: No such file or directory
@ivory hinge
uhm, should i try reinstall>
?
yes
mint@mint:~$ ls /mnt
bin boot-sav lib lib64 lost+found opt rootsystem swapfile
boot bootpart lib32 libx32 mnt root sbin
hmmm
if you have any data on sda5 you need, back it up now, then just reinstall
U can enter it in live system using file manager
check thru its home folder
either upload to dropbox/OneDrive or to second usb drive or memory card
chroot /mnt/rootsystem /bin/bash
mint@mint:~$ sudo chroot /mnt/rootsystem /bin/bash
chroot: failed to run command ‘/bin/bash’: No such file or directory
showing no directory again
wdym?
what should be my bootloader installation device?
d /mnt/rootsystem/bin
bash: cd: /mnt/rootsystem/bin: No such file or directory
can you ls /mnt/rootsystem?
sda1
isnt it windows?
I might interrupt but wouldn't it be just /dev/sda?
grub efi can coexist with winboot efi
that's for legacy BIOS mode
oh I guess. but it still should install It properly by default
meh . better to specify the ESP explicitly if setting up a UEFI-run dualboot
and please clean up the partitioning scheme. you only need 1 ext4 partition. and never make ext2/3 ones
did you create a root partition?
find the partition u want linux to install on
then click on 'change' button
set "use as" to ext4 journalling filesystem, and set mountpoint to /
for sda1 click change button, use as ESP make sure format box is not marked
find home partition u want to use for linux personal home files, then click change button
set as ext4, and mountpoint as /home
show final layout before continuing, and try to stretch window big
this is sda5 where my origibnal data was there right?
i think so.
uhm i think i will share screenshot of eaxh step
according to this, it looks like u had main linux on sda5
turn off fast startup in Windows
I hope you followed through with the last post in that chat link I gave, now should be good to go.
any news, @sacred fox ?
Wil be informing soon
This will delete the data in the partition?
If yes, i would like to rearrange my partition
you can do that ahead of running the installer, using the gparted program. it is wise to backup any very important data to an external drive before you do that operation.
So should i copy the whole sda?
naj
just what you need
from both Windows User folder and/or current linux installation's home folder
did you fix the original issue yet?
follow that ticket exactly from beginning to end if you want to have a simple and easy dual-OS setup on one drive.