[SOLVED] Windows 10 Corrupt LM19 FS
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
[SOLVED] Windows 10 Corrupt LM19 FS
Hello
This weekend I replaced my LM18.3 with LM19. As I dual boot my PC with Windows 10 and LM, I'd just delete/format the old EXT4 LM partition, and installed LM19 on that partition. The install went without any error or warning. After booting, LM19 worked properly and the log's was clean of errors. To check the installation, I rebooted to windows and it started normally, but when I tried to boot LM again, the boot failed and a session of initramfs was shown.
Looking around for some help, I found a post of someone suggesting to check the file system with FSCK after booting from live USB, and it's worked, but now I can't boot from windows without corrupting the EXT4 partition of LM19.
Can anyone has any suggestion about what can be causing this behaviour?
This weekend I replaced my LM18.3 with LM19. As I dual boot my PC with Windows 10 and LM, I'd just delete/format the old EXT4 LM partition, and installed LM19 on that partition. The install went without any error or warning. After booting, LM19 worked properly and the log's was clean of errors. To check the installation, I rebooted to windows and it started normally, but when I tried to boot LM again, the boot failed and a session of initramfs was shown.
Looking around for some help, I found a post of someone suggesting to check the file system with FSCK after booting from live USB, and it's worked, but now I can't boot from windows without corrupting the EXT4 partition of LM19.
Can anyone has any suggestion about what can be causing this behaviour?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Windows 10 Corrupt LM19 FS
Sounds like you installed Linux in a different mode... UEFI or Legacy to the way Windows is installed.
Boot the live version of Linux and run
You're looking for something like in the windows partition.
If you have one with (U)efi re-create your USB with rufus on windows 10 and select the GPT UEFI option.
Re-format the partition for Linux in Gparted and select the advanced install option.
create in your new partition.
/ (30 -40gb )
/swap ( match installed RAM up to 8GB )
/home the remainder.
Point the bootloader to the efi partition and install.
Don't forget to run after you've installed Linux.
Boot the live version of Linux and run
Code: Select all
blkid -o list
Code: Select all
vfat /boot/efi
If you have one with (U)efi re-create your USB with rufus on windows 10 and select the GPT UEFI option.
Re-format the partition for Linux in Gparted and select the advanced install option.
create in your new partition.
/ (30 -40gb )
/swap ( match installed RAM up to 8GB )
/home the remainder.
Point the bootloader to the efi partition and install.
Don't forget to run
Code: Select all
sudo update-grub
Last edited by Mattyboy on Mon Jul 02, 2018 8:11 am, edited 1 time in total.
Re: Windows 10 Corrupt LM19 FS
Thanks for your answer Mattyboy, but it don't seems that we are pointing to the same problem
Here is the output of my blkid -o list
As you may notice Linux is installed on the same HDD used for the Windows OS, and no reference to EFI, UEFI or VFAT.
Here is the output of my blkid -o list
Code: Select all
mint@mint:~$ blkid -o list
device fs_type label mount point UUID
-------------------------------------------------------------------------------
/dev/sda1 ntfs Reservado para el sistema (not mounted) 1E6462E26462BC61
/dev/sda2 ntfs WIN10_C (not mounted) 22F67491F6746747
/dev/sda4 ntfs Backup (not mounted) 0E9E852E79592135
/dev/sda6 ext4 (not mounted) 9e24e842-4d1d-4b55-8745-1ccd94b21711
/dev/sdb1 ntfs ARCHVOL (not mounted) A63021073020E053
/dev/sdc1 ntfs ARCHVOL2 (not mounted) 4300A615783247A3
/dev/sdc2 ext4 (not mounted) bfcece99-e7c7-4bc0-9cf7-1d11f9346e79
/dev/loop0 /rofs
/dev/sda5 [SWAP]
/dev/sdd1 (not mounted)
/dev/sdd2 (not mounted)
Re: Windows 10 Corrupt LM19 FS
Try the following from within a command line in LM19:
mount | grep boot
- and -
cat /etc/fstab | grep boot
do either of those report anything?
mount | grep boot
- and -
cat /etc/fstab | grep boot
do either of those report anything?
Re: Windows 10 Corrupt LM19 FS
Neither "mount | grep boot" nor "cat /etc/fstab | grep boot" shows a result. fstab only has the entries for the LM19 partition and the swap partition.
The FSCK shows this each time I run it
This is quite estrange because if you reboot from LM and start LM19 instead of windows 10 nothing happens, and LM start up without any issue, I mean without the already said FS corruption.
The FSCK shows this each time I run it
Code: Select all
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
/dev/sda6 was not cleanly unmounted, check forced.
Re: Windows 10 Corrupt LM19 FS
So far I have no luck here
I've installed boot repair looking for a deeper inside of the problem, but even it found a "mismatch" in the boot sector, it doesn't fix anything.
The report of Boot Repair was uploaded to http://paste.ubuntu.com/p/VYBQK9YHqx/
The procedure to reproduce my glitch is the following:
1.- Boot LM19 (Clean Boot)
2.- Reboot to LM19 (Clean Boot)
3.- Reboot to Windows 10 (Clean Boot)
4,- Boot again to LM19 (Start up crash showing a BusyBox console which, if you try to exit, says that is not possible to mount the LM19 volume and crash the kernel)
5.- Boot again from the live media and running fsck -y /dev/sda6 shows this output
6.-After cleaning the LM19 boot partition, LM19 boot without any issue and no data is lost.
In any case this is a inxi report of my system
Thanks to you all
I've installed boot repair looking for a deeper inside of the problem, but even it found a "mismatch" in the boot sector, it doesn't fix anything.
The report of Boot Repair was uploaded to http://paste.ubuntu.com/p/VYBQK9YHqx/
The procedure to reproduce my glitch is the following:
1.- Boot LM19 (Clean Boot)
2.- Reboot to LM19 (Clean Boot)
3.- Reboot to Windows 10 (Clean Boot)
4,- Boot again to LM19 (Start up crash showing a BusyBox console which, if you try to exit, says that is not possible to mount the LM19 volume and crash the kernel)
5.- Boot again from the live media and running fsck -y /dev/sda6 shows this output
Code: Select all
fsck -y /dev/sda6
fsck from util-linux 2.31.1
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
/dev/sda6 was not cleanly unmounted, 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
Block bitmap differences: -(1900544--1904771) -(1904896--1904979) -(1905024--1905133)... [b]A LONG LONG LIST OF ELEMENTS[/b] ... -(26156257--26156530) -(26157793--26158882)
Fix? yes
Free blocks count wrong for group #0 (23500, counted=19160).
Fix? yes
...
Free inodes count wrong (6553589, counted=6200600).
Fix? yes
/dev/sda6: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda6: 353000/6553600 files (0.1% non-contiguous), 3796240/26211584 blocks
In any case this is a inxi report of my system
Code: Select all
System: Host: desktop Kernel: 4.15.0-24-generic x86_64 bits: 64
Desktop: Cinnamon 3.8.7 Distro: Linux Mint 19 Tara
Machine: Device: desktop Mobo: ASUSTeK model: P5QC v: Rev 2.xx serial: N/A
BIOS: American Megatrends v: 2103 date: 04/27/2009
CPU: Quad core Intel Core2 Quad Q8200 (-MCP-) cache: 2048 KB
clock speeds: max: 2336 MHz 1: 2003 MHz 2: 2003 MHz 3: 2003 MHz
4: 2003 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
Display Server: x11 (X.Org 1.19.6 )
drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 4.15.0-24-generic, LLVM 6.0.0)
version: 3.3 Mesa 18.0.0-rc5
Audio: Card-1 Advanced Micro Devices [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series]
driver: snd_hda_intel
Card-2 Intel 82801JI (ICH10 Family) HD Audio Controller
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.15.0-24-generic
Network: Card: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
driver: ATL1E
IF: enp2s0 state: up speed: 100 Mbps duplex: full
mac: 00:22:15:6a:ee:5c
Drives: HDD Total Size: 2000.4GB (13.2% used)
ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
ID-2: /dev/sdb model: WDC_WD5000AAKS size: 500.1GB
ID-3: /dev/sdc model: WDC_WD5000LPVX size: 500.1GB
Partition: ID-1: / size: 98G used: 13G (14%) fs: ext4 dev: /dev/sda6
ID-2: swap-1 size: 4.09GB used: 0.00GB (0%)
fs: swap dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 26.0C mobo: 29.0C gpu: 45.5
Fan Speeds (in rpm): cpu: 2008 psu: 0 sys-1: 0 sys-2: 0
Info: Processes: 214 Uptime: 4 min Memory: 757.1/3944.5MB
Client: Shell (bash) inxi: 2.3.56
- catweazel
- Level 19
- Posts: 9763
- Joined: Fri Oct 12, 2012 9:44 pm
- Location: Australian Antarctic Territory
Re: Windows 10 Corrupt LM19 FS
There are mornings, afternoons and evenings?
<note to self: I have to get out of the basement>
Apologies to the OP for the OT post.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.
Re: Windows 10 Corrupt LM19 FS
I've done a couple of test trying to fix this issue.
Test 1: Clean reinstall of LM19. I've deleted LM19 partition's (root and swap), and reinstalled everything from scratch, including fixing the windows booting with sudo lilo -M /dev/sda mbr
Result: Failure. After booting Windows 10, if you try to boot LM19, it shows the Busybox console.
Test 2: Clean install of Manjaro. I've deleted LM19 partitions again, and installed Manjaro.
Result: Failure. Same behaviour. Busybox after booting from Windows
Test 3: Clean install of LM18.3. I've delete the Manajaro partition, and installed LM18.3 on it, including downgrading linux kernel to 4.4.130
Result: Success.
Even I don't have any further details that allow me to make a elaborated conclusion, it seems that maybe Linux kernel 4.15 and/or Grub 2.03 could be the culprits.
Test 1: Clean reinstall of LM19. I've deleted LM19 partition's (root and swap), and reinstalled everything from scratch, including fixing the windows booting with sudo lilo -M /dev/sda mbr
Result: Failure. After booting Windows 10, if you try to boot LM19, it shows the Busybox console.
Test 2: Clean install of Manjaro. I've deleted LM19 partitions again, and installed Manjaro.
Result: Failure. Same behaviour. Busybox after booting from Windows
Test 3: Clean install of LM18.3. I've delete the Manajaro partition, and installed LM18.3 on it, including downgrading linux kernel to 4.4.130
Result: Success.
Even I don't have any further details that allow me to make a elaborated conclusion, it seems that maybe Linux kernel 4.15 and/or Grub 2.03 could be the culprits.
Re: Windows 10 Corrupt LM19 FS
Hello
Finally I've found a solution for this error.
Check this link. It explain why its happening and how to fix it.
https://github.com/matt-wu/Ext3Fsd/issues/6
Solution: Without mounting the booting partition run as root
Finally I've found a solution for this error.
Check this link. It explain why its happening and how to fix it.
https://github.com/matt-wu/Ext3Fsd/issues/6
Solution: Without mounting the booting partition run as root
Code: Select all
tune2fs -O ^metadata_csum,^64bit /dev/sdX