1 module remaining error on Manjaro kde

Support
,
1

Hey

So I am trying to install Manjaro KDE on my pc. I torrented using the official torrent, verified hash, used both balena etcher and the DD command, but when I try and open calamares, I get an error saying 1 module remaining (it might not be an error), and the module is partition. Here is the log:

Any help would be appreciated

Thanks

2

A guess - your filesystem cannot be read.

3

so do you mean the usb I’m booting from or my HDD?

4

Yes - the system’s internal disk - it is a guess but from the log your internal cannot be read.

A disk which fails as serious as it appears easily be flawed - but it is impossible to say.

I would open a terminal - then list the devices - check if it is present and take it from there.

Most likely I would - in case of ssd - try to reset flash cells - or try a wipe of the disk - but that is speculative at best.

5

I already have an OS on the hard drive, so it is definitely working

6

boot a live iso - open a terminal an run the command

sudo fdisk -l

Create a code fence like this

```
Then copy the text and paste it inside the fence like this
```

The result should be looking like this

Then copy the text and paste it inside the fence like this
7 
Disk /dev/sda: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: Hitachi HDS5C303
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: FFA21A60-3E6C-E74D-92A6-C5BF4705D93C

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    1128447    1126400  550M EFI System
/dev/sda2  1128448    5322751    4194304    2G Linux swap
/dev/sda3  5322752 5860533134 5855210383  2.7T Linux filesystem


Disk /dev/loop0: 71.03 MiB, 74477568 bytes, 145464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 583.29 MiB, 611622912 bytes, 1194576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.8 GiB, 1932173312 bytes, 3773776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 743.34 MiB, 779452416 bytes, 1522368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 14.59 GiB, 15669919744 bytes, 30605312 sectors
Disk model: Cruzer Blade    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *         64 6788171 6788108  3.2G  0 Empty
/dev/sdb2       6788172 6796363    8192    4M ef EFI (FAT-12/16/32)
8

Nothing looks out of the ordinary - I have no idea why it is stubborn.

If you don’t have data worth saving you could try wiping using either

sgdisk --zap-all /dev/sda

or

wipefs --all /dev/sda