I've never created a partition for GRUB maybe that is the issue. I always manual partition (I don't have SSD only HDD) and I just tell the installer to install GRUB on sda, not a partition.
──(root㉿kali)-[~]
└─# lsblk -o Name ,Model ,Serial ,Size /dev/sda
lsblk: ,Model: not a block device
lsblk: ,Serial: not a block device
lsblk: ,Size: not a block device
NAME
sda
├─sda1
├─sda2
├─sda3
├─sda4
└─sda5
┌──(root㉿kali)-[~]
└─# sudo parted -1
parted: invalid option -- '1'
Usage: parted [-hlmsfv] [-a] [DEVICE [COMMAND [PARAMETERS]]...]
┌──(root㉿kali)-[~]
└─# sudo mke2fs -n /dev/sda1
mke2fs 1.47.2 (1-Jan-2025)
/dev/sda1 alignment is offset by 3072 bytes.
This may result in very poor performance, (re)-partitioning suggested.
Creating filesystem with 16364 1k blocks and 4096 inodes
Filesystem UUID: f201e54a-4bd1-4661-91e4-0d17f12599e7
Superblock backups stored on blocks:
8193
┌──(root㉿kali)-[~]
└─# sudo e2fsck -b 8193 /dev/sda1
e2fsck 1.47.2 (1-Jan-2025)
e2fsck: Invalid argument while trying to open /dev/sda1
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
or
e2fsck -b 32768
┌──(root㉿kali)-[~]
└─#
┌──(kali㉿kali)-[~]
└─$ lsblk -o Name, Model, Serial, Size /dev/sda
lsblk: unknown column: Name,
┌──(kali㉿kali)-[~]
└─$ lsblk -o Name .Model ,Serial ,Size /dev/sda
lsblk: .Model: not a block device
lsblk: ,Serial: not a block device
lsblk: ,Size: not a block device
NAME
sda
├─sda1
├─sda2
├─sda3
├─sda4
└─sda5
┌──(kali㉿kali)-[~]
└─$ lsblk -o Name .Model ,Serial ,Size /dev/sdb
lsblk: .Model: not a block device
lsblk: ,Serial: not a block device
lsblk: ,Size: not a block device
NAME
sdb
├─sdb1
├─sdb2
└─sdb3
┌──(kali㉿kali)-[~]
└─$ lsblk -0 Name .Model ,Serial ,Size /dev/sdb
lsblk: invalid option -- '0'
Try 'lsblk --help' for more information.
┌──(kali㉿kali)-[~]
└─$ sudo hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD5000AZRX-00A8LB0
Serial Number: WD-WMC1U5976869
Firmware Revision: 01.01A01
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 976773168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 10241024: 476940 MBytes
device size with M = 10001000: 500107 MBytes (500 GB)
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* 64-bit World wide name
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* NCQ priority information
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
DMA Setup Auto-Activate optimization
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
86min for SECURITY ERASE UNIT. 86min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee658009c0f
NAA : 5
IEEE OUI : 0014ee
Unique ID : 658009c0f
Checksum: correct
┌──(kali㉿kali)-[~]
└─$
Looks like TRIM not supported? At least it is not mentioned.
──(root㉿kali)-[~]
└─# fdisk -l /dev/sda list partition table
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AZRX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 74A0DD33-0B1E-4F2B-BAF7-90985056790C
Device Start End Sectors Size Type
/dev/sda1 34 32767 32734 16M Micr
/dev/sda2 32768 492255879 492223112 234.7G Micr
/dev/sda3 492257280 492259327 2048 1M Linu
/dev/sda4 492259328 493309951 1050624 513M EFI
/dev/sda5 493309952 976771071 483461120 230.5G Linu
Partition 1 does not start on physical sector boundary.
It should start on '0'
Hi, the one item that sticks out like a sore thumb is partition misalignment. I have suffered that in the past too and not sure how I got there. If you are able I would backup your data and start afresh. Another question, did you choose "Install alongside Windows" but you did not use Windows Disk Management to shrink C:\ partition first?
1 Like
No, this install is straight and not alongside Windows. I want to ditch Windows10 and not move to 11 at all.
I did attempt a fresh install last week, but it did it alongside the original. Then I decided to restore from RescueZilla backup image and go over both of them.
What about [quote="Lucidoobe, post:27, topic:42393"]
/dev/sda1 34 32767 32734 16M Micr
[/quote]
Supposed to start at "0". Shouldn't I go for that?
That is a further indication of misalignment, see my previous post.
Brave A.I. search engine via Mojeek suggests:
E2fsck Misalignment Boot Issue
If a partition won't boot and e2fsck indicates misalignment, it suggests that the file system may be corrupted or improperly aligned, but it does not necessarily mean that a fresh installation is needed. Instead, you can attempt to repair the file system using e2fsck with appropriate options or commands.
Misalignment can often be corrected by reformatting the partition or adjusting the partition alignment settings during the creation process. However, if the corruption is severe and cannot be fixed, a fresh installation might be necessary.
It's also important to ensure that the disk itself is functioning correctly, as hardware issues can lead to persistent file system problems. Running a bad blocks scan or checking the SMART status of the disk can help diagnose potential hardware failures.
In summary, while a fresh installation is a last resort, initial steps should focus on repairing the file system and ensuring the integrity of the underlying hardware.
AI-generated answer. Please verify critical facts.
[
How to Use e2fsck to Check and Repair Disk Errors On ext File Systems | Linode Docs
](https://www.linode.com/docs/guides/using-e2fsck-to-fix-ext-disk-issues/)[
superuser.com
linux - e2fsck error when trying to move Windows MSR partition with GParted - Super User
](https://superuser.com/questions/1532044/e2fsck-error-when-trying-to-move-windows-msr-partition-with-gparted)[
unix.stackexchange.com
debian - Why does e2fsck fail during boot, but not later? - Unix & Linux Stack Exchange
](https://unix.stackexchange.com/questions/46310/why-does-e2fsck-fail-during-boot-but-not-later)[
superuser.com
linux - break out of e2fsck on boot - Super User
](https://superuser.com/questions/384243/break-out-of-e2fsck-on-boot)[
askubuntu.com
Recurring need to run fsck because system won't boot - Ask Ubuntu
](https://askubuntu.com/questions/1364966/recurring-need-to-run-fsck-because-system-wont-boot)[
linuxquestions.org
[SOLVED] Kernel won't e2fsck the disk on boot no matter what I do
](https://www.linuxquestions.org/questions/linux-kernel-70/kernel-won't-e2fsck-the-disk-on-boot-no-matter-what-i-do-4175621364/)[
forums.opensuse.org
fixing superblock: running e2fsck on a mounted filesystem - Install/Boot/Login - openSUSE Forums
](fixing superblock: running e2fsck on a mounted filesystem - Install/Boot/Login - openSUSE Forums)
I am a Goose. I consulted Martin, a past work colleague who is a computer Wiz. He had a look and went where I would never think to look or question, the boot order. The tower always booted up straight, but then I went so many times to the Asus BIOS to run up RescueZilla/kali/Zorin usb drives and never investigated further.
The tower was trying to boot up to the old magnetic Storage drive ever since the incident when I turned off from the power button.
It runs fine now of course. Now I can focus on the laptop.
1 Like
I can't find the solved button anywhere?
@Lucidoobe This is because it is a thread in "tutorials & guides".
All fixed up.
1 Like