You are not logged in.
Hi there,
Here's the picture. I've got a dualboot system: sda is Archlinux, sdb is Windows 10. Everything worked fine. Then, Windows installed one of those automatic updates and activated Fast Boot without my knowledge. I also have Paragon ExtFS installed and accessed my Linux partitions to open a PDF file (I also accessed boot partition, but made no changes in it). Now, when I try to boot Arch, I get the following message:
error: invalid cluster 0.
Then:
Kernel-panic - not syncing: VFS : Unable to mount root fs on unknown-block(0,0)
I booted Arch using an install image (USB-key). Change-rooted, updated packages and reinstalled Grub. Still the same messages when trying to boot.
Any ideas?
Thanks.
Last edited by dicaiopolis (2019-01-17 21:34:09)
Offline
If you can chroot and update packages the filesystem seems to be fine, at least from a glance.
What is your fstab configured to? if you use /dev/sda and /dev/sdb you really don't want to do that: https://wiki.archlinux.org/index.php/Pe … ice_naming
Last edited by V1del (2019-01-16 17:15:51)
Online
Here's my fstab:
# /dev/sda2 UUID=6181af6a-94ff-4151-b7c7-442a6adb3110 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1 UUID=3564-29EA /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda3 UUID=013931d0-98a4-4714-bfaa-76e43834596d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda4 UUID=ad0166fc-5789-446d-a916-9d55f567e9b7 none swap defaults,pri=-2 0 0
# /dev/sdb2 UUID=90B5-B36F /media/C vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sdb4 UUID=F090BA4090BA0D5A /media/D ntfs-3g rw,relatime,data=ordered 0 2
# /dev/sdc2 UUID=B4D0E24CD0E21500 /media/F ntfs-3g rw,relatime,data=ordered 0 2
# /dev/sdc3 UUID=8e4fece7-b4a5-4572-a69b-2ffa8d587e32 /media/Linux-Dados ext4 rw,relatime,data=ordered 0 2
/home/andre/Iso/Tlg.iso /media/Tlg iso9660 user,loop 0 0
/home/andre/Iso/Phi5.iso /media/Phi iso9660 user,loop 0 0
/home/andre/Iso/Il_Verbo_Greco.iso /media/VerboGreco iso9660 user,loop 0 0
Offline
Ok. I've got a doubt. When change-rooting, I just do
mount /dev/sda2 /mnt
arch-chroot /mnt
Since root and boot are in different partitions (sda2=root and sda1=boot), should I mount sda1 too? How? Or I just do
mount /dev/sda /mnt
and I get everything mounted?
Offline
Tried the following thing:
mount /dev/sda2 /mnt
arch-chroot /mnt
mount /dev/sda1 /boot
Then, reinstalled grub. Still nothing. I have no idea of what's going on. Having searched the forum ant the net, I couldn't get any hint.
I don't wanna reinstall Arch, cause it's completely configured for my needs and I don't wanna spend again the huge amount of time I put into it.
Any help is appreciated.
Thanks.
Offline
Well unless you made a mistake during copying, currently all your entries are commented out. put a newline before the UUID identifiers.
Last edited by V1del (2019-01-17 16:02:47)
Online
I think it was a copy problem. Here's the actual fstab:
# /dev/sda2
UUID=6181af6a-94ff-4151-b7c7-442a6adb3110 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1
UUID=3564-29EA /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda3
UUID=013931d0-98a4-4714-bfaa-76e43834596d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda4
UUID=ad0166fc-5789-446d-a916-9d55f567e9b7 none swap defaults,pri=-2 0 0
# /dev/sdb2
UUID=90B5-B36F /media/C vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sdb4
UUID=F090BA4090BA0D5A /media/D ntfs-3g rw,relatime,data=ordered 0 2
# /dev/sdc2
UUID=B4D0E24CD0E21500 /media/F ntfs-3g rw,relatime,data=ordered 0 2
# /dev/sdc3
UUID=8e4fece7-b4a5-4572-a69b-2ffa8d587e32 /media/Linux-Dados ext4 rw,relatime,data=ordered 0 2
/home/andre/Iso/Tlg.iso /media/Tlg iso9660 user,loop 0 0
/home/andre/Iso/Phi5.iso /media/Phi iso9660 user,loop 0 0
/home/andre/Iso/Il_Verbo_Greco.iso /media/VerboGreco iso9660 user,loop 0 0
Offline
That looks alright, can you fsck your root and boot partitions? You might want to explicitly reinstall the kernel package when in the chroot (ensuring that /boot is properly mounted) I've seen similar with corrupted files on the ESP, did you check that you still have enough free space on the ESP partition to contain the kernel image?
Online
ESP has 490mb of free space.
I'm mounting the boot partition this way, after chrooting:
mount /dev/sda2 /mnt
arch-chroot /mnt
mount /dev/sda1 /boot
Is this the right way?
Offline
Yeah that should be fine, fsck it (needs dosfstools) before mounting, then mount (to be extra sure, manually remove your initramfs and kernel images ) and reinstall the kernel, I faintly remember having this one time, where simply the file name table of the FAT partition was corrupted and the kernel couldn't be located despite the file itself having been written properly.
Last edited by V1del (2019-01-17 16:24:28)
Online
Sorry for my ignorance, but how can I manually remove your initramfs and kernel images? Using pacman -R?
Offline
no just delete them with rm, especially the initramfs is only generated afterwards by mkinitcpio and not tracked by pacman.
But if it's similar to the issue I had, as far as I remember a fsck was enough to fix it.
Online
And where are initramfs and kernel located?
Last edited by dicaiopolis (2019-01-17 16:34:58)
Offline
On the /boot partition...
Online
Well, there was no initramfs. Did a update, installing the new kernel and it worked fine.Thanks for your great help.
Offline