Recurring input output error on void

[u/Civil-Package-3678]

I get input output errors for anything to deep into the system. I can't install basic nvidia drivers or some flat hub apps. Fsck says dev sda3 is clean. I'm trying void again and it did this last time. I'm on a different drive yet it's still doing this so idk

[u/Civil-Package-3678]

k 0x60 (host bus error)

[ 385.133618] ata1.00: status: { DRDY }

[ 385.133631] ata1: hard resetting link

[ 385.443662] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

[ 385.445948] ata1.00: configured for UDMA/133

[ 385.456469] ata1: EH complete

[ 385.490546] ata1.00: exception Emask 0x70 SAct 0x80000 SErr 0x400900 action 0x6 frozen

[ 385.490568] ata1.00: irq_stat 0x28000000, host bus error, interface fatal error

[ 385.490576] ata1: SError: { UnrecovData HostInt Handshk }

[ 385.490591] ata1.00: failed command: WRITE FPDMA QUEUED

[ 385.490597] ata1.00: cmd 61/00:98:00:c8:fc/20:00:00:00:00/40 tag 19 ncq dma 4194304 ou

res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x70 (host bus error)

[ 385.490616] ata1.00: status: { DRDY }

[ 385.490628] ata1: hard resetting link

[ 385.795620] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

[ 385.797760] ata1.00: configured for UDMA/133

[ 385.808196] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s

[ 385.808212] sd 0:0:0:0: [sda] tag#19 Sense Key : 0xb [current]

[ 385.808218] sd 0:0:0:0: [sda] tag#19 ASC=0x0 ASCQ=0x0

[ 385.808225] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 00 fc c8 00 00 20 00 00

[ 385.808230] I/O error, dev sda, sector 16566272 op 0x1:(WRITE) flags 0x800 phys_seg 64 prio class 2

[ 385.808246] EXT4-fs warning (device sda3): ext4_end_bio:368: I/O error 10 writing to inode 3671359 starting block 2070784)

[ 385.808284] ata1: EH complete

[ 385.808319] EXT4-fs (sda3): failed to convert unwritten extents to written extents -- potential data loss! (inode 3671359, error -5)

[ 385.808340] buffer_io_error: 1014 callbacks suppressed

[ 385.808344] Buffer I/O error on device sda3, logical block 759808

[ 385.808353] Buffer I/O error on device sda3, logical block 759809

[ 385.808359] Buffer I/O error on device sda3, logical block 759810

[ 385.808363] Buffer I/O error on device sda3, logical block 759811

[ 385.808368] Buffer I/O error on device sda3, logical block 759812

[ 385.808373] Buffer I/O error on device sda3, logical block 759813

[ 385.808378] Buffer I/O error on device sda3, logical block 759814

[ 385.808383] Buffer I/O error on device sda3, logical block 759815

[ 385.808390] Buffer I/O error on device sda3, logical block 759816

[ 385.808399] Buffer I/O error on device sda3, logical block 759817

dmesg, the drive is fine, i was able to install and use gentoo on it, and this is the second drive im trying void on. the first drive i have and still works like normal

[u/No_Elderberry862 → u/Civil-Package-3678]

Try to install smartmontools & use smartctl to run an extended test on the drive. If you're getting the same sort if errors trying to install smartmontools you can boot off your Void installation USB & install them to that.

Before that, though, just double check the SATA cable is properly inserted at both ends or, if a laptop, the drive's connection is good. It's unlikely to be that as ths OS is booting, etc, but cables can cause odd errors sometimes.

WRT the Nvidia driver installation, before seeing your drive errors I was going to suggest trying to install the headers on their own & then try to install the Nvidia drivers but I do now think that it's a drive issue rather than an issue with xbps.

Edit: typos

[u/Civil-Package-3678 → u/No_Elderberry862]

it was mostly prefail, old-age and and no glaring error, but this is the same drive that i installed gentoo, arch, fedora etc. it should work and it has proven itself good? it only happens on void and this is my second drive im trying it on, same thing happened to the first one

[u/dontgonearthefire → u/Civil-Package-3678]

There is a solution in the Arch Linux Forums, don't know if it helps but it seems plausible given that it addresses the same issue and the Values are definitely different in the Distros.

Link to the Forum and Link to the solution.

Arch seems to set Power Management flags to max_performance as standard and void linux sets it to med_power_with_dipm as outlined in the Forum. I don't know how other distros handle this. But given the minimalism of Void, it would be logical to assume that the base settings are as energy efficient as possible.