Ominous error messages while booting encrypted install from ssd

[Member Vincent17]

I recently did an encrypted install of antiX17.4 from snapshot on an SSD, leaving 50GB free space for puppylinux 😉
At first, this seemed great, but now I am seeing a growing series of error messages at bootup, after unlocking rootfs. These cause a few seconds’ delay, but so far the boot eventually succeeds.

For almost 2 years this drive had an antiX standard install with ecryptfs-encrypted home. The problems appeared after doing the encrypted install. At this point, I will revert to the ecryptfs-home setup unless someone has ideas for me to try first. Thanks in advance.

Sample error messages:

[   26.384752] ata1: SError: { PHYRdyChg CommWake DevExch }
[   26.384954] ata1.00: failed command: READ FPDMA QUEUED
[   26.385207] ata1.00: cmd 60/08:00:38:11:10/00:00:02:00:00/40 tag 0 ncq dma 4096 in
                        res 40/00:c4:a8:6e:94/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[   26.385764] ata1.00: status: { DRDY }
repeats many times
[   27.880823] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   27.880838] sd 0:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[   27.880851] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unaligned write command
[   27.880865] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 02 10 11 38 00 00 08 00
[   27.880873] blk_update_request: I/O error, dev sda, sector 34607416
repeats for many sector numbers
[   28.856064] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   28.869778] ata1.00: configured for UDMA/133
[   28.880688] ata1: EH complete
[   29.356131] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[   29.361105] ata1: irq_stat 0x00000040, connection status changed
[   29.366082] ata1: SError: { CommWake DevExch }
[   29.370972] ata1: hard resetting link
repeats many times

Similar problem described here was solved by replacing crucial ssd with samsung:
https://forums.linuxmint.com/viewtopic.php?t=247820

trim enabled:
http://worldsmostsecret.blogspot.com/2012/04/how-to-activate-trim-on-luks-encrypted.html

booted from flash drive and checked encrypted fs:

sudo cryptsetup luksOpen /dev/sda2 name
sudo e2fsck /dev/mapper/name
clean

System:

Host: Wind Kernel: 4.9.221-antix.1-486-smp i686 bits: 32 compiler: gcc 
  v: 6.3.0 Desktop: JWM 2.3.6 
  Distro: antiX-17.4.1_386-base Helen Keller 28 March 2019 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Desktop System: MICRO-STAR product: U-100 v: Ver.001 
  serial: <filter> 
  Mobo: MICRO-STAR model: U-100 v: Ver.001 serial: <filter> 
  BIOS: American Megatrends v: 4.6.3 date: 10/06/2008 
Drives:
  Local Storage: total: 111.79 GiB used: 3.77 GiB (3.4%) 
  ID-1: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB 
Partition:
  ID-1: / size: 59.23 GiB used: 3.57 GiB (6.0%) fs: ext4 dev: /dev/dm-0 
  ID-2: /boot size: 486.8 MiB used: 202.9 MiB (41.7%) fs: ext4 
  dev: /dev/sda1 
  ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1

[Member Xecure]

Helpful

Up

0

::

Do you mean you encrypt the partition before performing the installation with the minstaller gui application or are you talking about encrypting a frugal install?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Vincent17]

Helpful

Up

0

::

Sorry, I was not clear. I booted my snapshot from a flash drive, then minstall: step 1a choose the ssd, step 1c Auto-install using entire disk, encrypt, leave free space up to 50000MB

• This reply was modified 2 years, 6 months ago by Vincent17. Reason: clarity

[Member Xecure]

Helpful

Up

0

::

If the snapshot is not recent, before installing try updating/upgrading the live snapshot. I think there was a minstaller update that fixed a encryption problem, but I am not 100% sure if it was also included for antiX 17.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Vincent17]

Helpful

Up

0

::

I have minstall -v 1.0.4.12. After a full upgrade I still have the same version. (I have all the antix repos enabled) Where can I get the latest?
Thanks for the help.

[Member Vincent17]

Helpful

Up

0

::

In antiX 19.3, minstall is version 1.3.3. I made an encrypted install of 19.3 to the SSD and at first, the error messages were absent. Unfortunately, after a few boots they’re back. 🙁

• This reply was modified 2 years, 6 months ago by Vincent17. Reason: update

[Member Xecure]

Helpful

Up

0

::

Vincent17 wrote:

In antiX 19.3, minstall is version 1.3.3. I made an encrypted install of 19.3 to the SSD and at first, the error messages were absent. Unfortunately, after a few boots they’re back.

It is a pitty. The problem may be related to something else, but my experience with encryption is almost zero. Maybe it is even related to the partition format, but this is me shooting in the dark.

Does anyone who uses encryption know or have experienced this behaviour previously and can shine some light on the issue?

Edit: Searching for the posted errors leads to a posible hardware problem or driver problems, but I couldn’t find a lead to indicate this is related to encryption.
Possible reasons found are:
SATA link power management causes disk errors and corruption
Damaged SATA cable
Kernel regression
Firmware regression
BIOS Firmware update needed for high speed SSDs

It may seem some people get it “fixed” by using an updated firmware or using the boot parameter “libata.force=3.0” to change the read/write sata speed.
See this long thread: https://github.com/openzfs/zfs/issues/10094

• This reply was modified 2 years, 6 months ago by Xecure. Reason: Search results

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Hardware issue?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Vincent17]

Helpful

Up

0

::

anticapitalista wrote:

Hardware issue?

smartctl shows “PASSED” plus a bunch of stuff I don’t understand. I have a couple more experiments in mind. I have reinstalled antiX-17.4 encrypted with no free space. If the errors reappear, then I’ll reinstall without encryption. If anything interesting happens, I’ll report back even though I expect this has nothing to do with antiX.

EDIT: Hi Xecure, I missed your message. I checked connections by wiggling and reinserting the ssd. I contacted the SSD manufacturer, but they just said to reinitialize using Disk Management; I should ask about firmware. The bios currently provided by MSI caused all kinds of problems; I’m using the newest one I could find (2008!) that works. The libata.force parameter looks interesting; one thing I noticed in the boot messages was ata1: limiting SATA link speed to 1.5 Gbps so I could try setting that preemptively.

Thanks for the help.

• This reply was modified 2 years, 6 months ago by Vincent17. Reason: added note

[Member Vincent17]

Helpful

Up

0

::

Sorry for the bump, but I want to bring this to a conclusion: the ssd was indeed defective. Guilty of post hoc fallacy: the error messages appeared just after my first encrypted install, but it turns out they also occur with regular install 🙁 Thanks for all the guidance.

By the way, I’m so happy with a frugal encrypted install to SD card that I probably won’t replace the ssd. live-usb-maker is awesome! Thanks BitJam.

[Author]

Posts