You are not logged in.
I removed my /dev/sdc disk a while back due to the disk being corrupted. Now when I run os-prober or grub-mkconfig I get the following message (os-prober) https://bpa.st/HP2HW and (grub-mkconfig) https://bpa.st/F5F7A . I'm not sure what file I need to edit to remove /dev/sdc from my system. The output of my disk is listed in the following link: https://bpa.st/VEJEU
Offline
Offline
I don't believe so. https://bpa.st/2ZWRI
Offline
sdc identifiers and friends are randomly assigned, likely some other device has taken the place of your former c and is generating the issues. Did you check the actual path/with fdisk -l or so which device that is now?
Offline
I'm not sure what you're asking and i'm not sure if this is the right command to run, but when I run fdisk -l /dev/sdc I get the following message
fdisk: cannot open /dev/sdc: Input/output error
Offline
Found Windows Boot Manager on /dev/sdd1@/efi/Microsoft/Boot/bootmgfw.efi
Since d comes after c, something™ will be on sdc.
Please post a complete system journal
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
Offline
Jan 28 11:15:22 arch-pc kernel: scsi 2:0:0:0: Direct-Access ATA ST3000NM0033 SN04 PQ: 0 ANSI: 5
Jan 28 11:15:22 arch-pc kernel: sd 2:0:0:0: [sdc] 8089950 512-byte logical blocks: (4.14 GB/3.86 GiB)
Jan 28 11:15:22 arch-pc kernel: sd 2:0:0:0: [sdc] Write Protect is off
Jan 28 11:15:22 arch-pc kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Jan 28 11:15:22 arch-pc kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 28 11:15:22 arch-pc kernel: sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Jan 28 11:15:22 arch-pc kernel: ata3.00: Read log 0x10 page 0x00 failed, Emask 0x1
Jan 28 11:15:22 arch-pc kernel: ata3: failed to read log page 10h (errno=-5)
Jan 28 11:15:22 arch-pc kernel: ata3.00: exception Emask 0x1 SAct 0x4000 SErr 0x0 action 0x0
Jan 28 11:15:22 arch-pc kernel: ata3.00: irq_stat 0x40000001
Jan 28 11:15:22 arch-pc kernel: ata3.00: failed command: READ FPDMA QUEUED
Jan 28 11:15:22 arch-pc kernel: ata3.00: cmd 60/08:70:00:00:00/00:00:00:00:00/40 tag 14 ncq dma 4096 in
res 51/04:70:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
Jan 28 11:15:22 arch-pc kernel: ata3.00: status: { DRDY ERR }
Jan 28 11:15:22 arch-pc kernel: ata3.00: error: { ABRT }
Jan 28 11:15:22 arch-pc kernel: ata3.00: configured for UDMA/133
ST3000NM0033 is a Seagate Constellation ES.3 SATA III 3TB, I'd check the https://wiki.archlinux.org/title/SMART data on that …
Offline
Thanks Seth. I'll take a look at smart.
Offline
I ran the smart tests and I got the following results
smartctl -H /dev/sda === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED
smartctl -l selftest /dev/sda
smartctl -a /dev/sda
Offline
Why do we care about sda? The problem-drive is sdc.
Offline
When I run
smartctl -t long /dev/sdc
I get the following error message:
Read SMART Data failed: scsi error badly formed scsi parameters
Offline
And also an error in dmesg?
(You can "dmesg -w" to track the ringbuffer, then call smartctl in a different terminal)
Sounds like the drive is toast, though.
Offline
Ok. Thanks again for your help!
Offline