Omarchy 3.2.1 can't install. Something about luks.py

[ColtonIdle]

System details

Framework 13

What's wrong?

I've installed omarchy like a billion times (here for alphas, beta, online iso and offline iso etc). its never really stalled out on me. but now it is. i cant easily grab logs. but can take a screenshot and attach it in a comment below

[ColtonIdle]

[ColtonIdle]

tried 3 times in a row. same error each time.

[ColtonIdle]

tried with just arch iso and archinstall. same issue. so i guess its an archinstall root cause?

i tried both with encryption on and off. failed both times.

[ColtonIdle]

maybe my drive is dying. fails in omarchy. fails in regular arch iso. fails installing ubuntu as well.

ubuntu@ubuntu: ~$ sudo dmes | grep -i nvme
1.868209] nme 0000 :bf :00.0: platform quirk: setting simple suspend
1.868269] nume nme0: pci function 0000:bf: 00.0
1.875592] nume nvme0: allocated 8 MiB host memory buffer (1 segment).
1.878639] nume numeo: 8/0/0 default/read/poll queues
1.884841] nyme nme®: Ignoring bogus Namespace Identifiers
1.887082] nvme0n1: p1 p2
36.287667] nme nvme0: using unchecked data buffer
82.239274] block nvme0n1: the capability attribute has been deprecated.
254. 072673] nvne 0n1: p1 p2
254.116039] nvne0n1: p1 p2
254.172000] nvne0n1: p1 p2
254.213090] nvme0n1: p1 p2
255.126246] nvme 0n1: I/0 Cmd(0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
255.126255] critical medium error, dev numeoni, sector 4204544 op 0X0:(READ) flags 0x80700 op OXO: (READ) flags 0x80700 phys _seg 1 prio class 2
255.127115] nvre0n1: I/0 Cmd (0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
255.127117] Oxo: (READ) flags critical medium error, dev numeOni, sector 4204544 op 0X0:(READ) flags Ox0 phys_seg 1 prio class 2
[ 255.127118 Buffer I/0 error on dev nvme0n1p2, logical block 1024, async page read
255.132603| nvme 0n1: I/0 Cmd(0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
255. 132611] critical medium error, dev nvme0n1, sector 4204544 op OX0: (READ) flags 0x80700 phys_seg 1 prio class 2
255. 181479] nvme 0n1: I/0 Cmd(0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
255. 181491] critical medium error, dev nme0n1, sector 4204544 op 0X0:(READ) flags Ox0 phys_seg 1 prio class 2
255.181494] Buffer I/0 error on dev nvme0n1p2, logical block 1024, async page read
255.220330] nvme0n1: p1 p2
255.245711] nvme0n1: p1 p2
255.249583] nvme 0n1: p1 p2
255.780900] nvme0n1: p1 p2
256.300185] nvme0n1: p1 p2
257.318705] nvme0n1:
Г p1 p2
259.338807] nvme0n1: p1
264.357268] p2
nvme0n1: p1 p2
271.438881] nvme0n1: p1 p2
271.464874]
271.464891] nvme 0n1: I/0 Cmd(0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
critical medium error, dev numeOni, sector 4204544 op 0x0: (READ) flags 0x80700 phys_seg 1 prio class 2
271.465699] nvme 0n1: 1/0 Cmd (0x2) @ LBA 4204544, 8 blocks, I/0 Error (sct 0x2 / sc 0x81)
271.465709] critical medium error, dev nmeOn1, sector 4204544 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 2
[ 271.465713] Buffer I/0 error on dev nvme0n1p2, logical block 1024, async page read 271 6042007 O1. 1 na

not sure if my drive is dead or something in omarchy botched it?

[JackTubby]

I don't think it would be anything to do with Omarchy as it looks like it is a physical issue with your drive. I had something similar before replaced my drive and I was okay.

luks.py when writing hit a bad sector (4204544) - it didn't cause it

[ColtonIdle]

thanks. i replaced the drive and everything works, so im guessing thats it. ive never had an ssd go bad on me before. so its definitely weird to me that it happened just now lol