Project

General

Profile

/dev/sdX changes to /dev/sdY while installing Parabola on it

Avron - almost 3 years ago -

My olinuxinoLime2 has an HDD that I have not used so far (not partitioned), it shows up as /dev/sda but strangely it sometimes disappears after the machine has been running for days. I am seeing that with lsblk.

More problematic, while I am trying to install a system (for the same board model, but with eMMC) on a micro sd card with a USB card reader, while the filesystem on it is mounted and I am writing to it with pacstrap, it regularly happens that the sdcard suddenly changes from /dev/sdX to /dev/sdY and then of course all reads and writes fail.

I tried to update /etc/fstab after mounting the device, using UUIDs, then the installation of base, libelogind and udev-init-scripts is usually successful (without updating fstab, it usually fails before the end), I could do some configuration and generate locales but then it failed while installing linux-libre-lts, and I could see that at the same time, /dev/sda had disappeared.

My fstab was like this:

# /dev/mmcblk0p1
UUID=1e6fdca4-68bf-4cb3-8d8d-3ff01a17b0a3       /               ext4            rw,relatime     0 1

# /dev/sdb1
UUID=e3d9eacf-f23f-43c1-bf80-1f207cef88ad       /mnt/sdcard     ext4            rw,relatime     0 2

Apparently, the file system I was installing is now corrupted, so I'll try to start it all over (I stopped counting attempts).

I guess I am doing something wrong but I don't know what. I am getting a little desperate.


Replies (3)

RE: /dev/sdX changes to /dev/sdY while installing Parabola on it - oaken-source - almost 3 years ago -

disappearing device nodes while the system is running is generally worrying and can indicate a hardware failure. I would recommend checking dmesg to see if there is any useful output.

RE: /dev/sdX changes to /dev/sdY while installing Parabola on it - Avron - almost 3 years ago -

I tried to make a file system on /dev/sda, it fails and /dev/sda has disappeared.

dmesg says:
[ 4078.401835] ata1.00: exception Emask 0x0 SAct 0x100000 SErr 0x50000 action 0x6 frozen
[ 4078.401859] ata1: SError: { PHYRdyChg CommWake }
[ 4078.401878] ata1.00: failed command: READ FPDMA QUEUED
[ 4078.401902] ata1.00: cmd 60/08:a0:00:6d:70/00:00:74:00:00/40 tag 20 ncq dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 4078.401911] ata1.00: status: { DRDY }
[ 4078.401933] ata1: hard resetting link
[ 4078.716225] ata1: SATA link down (SStatus 0 SControl 300)
[ 4083.749552] ata1: hard resetting link
[ 4084.063989] ata1: SATA link down (SStatus 0 SControl 300)
[ 4089.125318] ata1: hard resetting link
[ 4089.439720] ata1: SATA link down (SStatus 0 SControl 300)
[ 4089.439747] ata1.00: disabled
[ 4089.439855] sd 0:0:0:0: [sda] tag#20 UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 cmd_age=41s
[ 4089.439876] sd 0:0:0:0: [sda] tag#20 Sense Key : 0x2 [current]
[ 4089.439889] sd 0:0:0:0: [sda] tag#20 ASC=0x4 ASCQ=0x21
[ 4089.439907] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x28 28 00 74 70 6d 00 00 00 08 00
[ 4089.439924] blk_update_request: I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 4089.440003] ata1: EH complete
[ 4089.440052] ata1.00: detaching (SCSI 0:0:0:0)
[ 4089.440150] blk_update_request: I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 4089.440168] Buffer I/O error on dev sda, logical block 244190624, async page read
[ 4089.451239] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4089.451517] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[ 4089.451538] sd 0:0:0:0: [sda] Stopping disk
[ 4089.451613] sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00

I'd like to find logs for previous attempts but in /var/log the only things I have, apart from dmesg are pacman.log, rc.log, wtmp and Xorg.0.log there is nothing else, and dmesg starts from last boot. Are there log files elsewhere? Or should I install something like syslog-ng?

If I have similar problems with a SATA disk and a USB SD card reader, is it likely to be a hardware issue or could it be a kernel problem or another software problem?

RE: /dev/sdX changes to /dev/sdY while installing Parabola on it - bill-auger - almost 3 years ago -

that often is a symptom of failing hardware

you did not mention which kernel you are using; but you could
probably determine if it is related to the kernel, by trying
another kernel - eg: linux-libre or linux-libre-lts

you could also try other version like:

sudo pacman -U https://repo.parabola.nu/pool/parabola/linux-libre-4.18.11_gnu-1-x86_64.pkg.tar.xz
or
sudo pacman -U https://repo.parabola.nu/pool/parabola/linux-libre-lts-5.10.19-1-x86_64.pkg.tar.xz

if any other kernel works without the same problem, please opena
bug report about it

    (1-3/3)