Failing to mount drive at boot, can mount later

mortoray · 12-02-2022, 01:49 AM

My one internal drive is failing to mount at boot time after I upgraded to Ubuntu 22.04. In 18.04 it never had an issue. If I mount after boot completes it mounts without a problem (mount -a).

From dmesg the most I could find is this:

Code:

[    6.929181] sd 4:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[    6.929184] sd 4:0:0:0: [sda] tag#31 Sense Key : Medium Error [current] 
[    6.929186] sd 4:0:0:0: [sda] tag#31 Add. Sense: Unrecovered read error - auto reallocate failed
[    6.929189] sd 4:0:0:0: [sda] tag#31 CDB: Read(10) 28 00 2b b6 dc 80 00 00 08 00
[    6.929190] blk_update_request: I/O error, dev sda, sector 733404288 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.929195] Buffer I/O error on dev sda1, logical block 91675280, async page read

I already modified my fstab to prevent the system from failing to boot, but now it boots without mounting, and fails to retry to mount. I'd be happy if it simply kept trying to mount, but didn't block boot.

Code:

UUID=db01e20b-80b1-4095-a9fc-7e0b28f99561 /drives/extratb ext4 defaults,nofail,x-systemd.device-timeout=9 0 2

I've run fsck on the drive. It did fix one issue, but that didn't solve the problem. I've also experience no issues with the drive once it's mounted.

I feel like this might be some setting that's changed that causes a conflict with this drive, but unsure what it might be, or how to fix it. If no fix is easy, then at least a way to keep trying to mount the drive. It only really needs to be mounted by the time my desktop (KDE) starts up.

mrmazda · 12-02-2022, 02:14 AM

Those read errors suggest the drive has issues that need to be investigated. Start by using smartctl -x /dev/sda.

mortoray · 12-02-2022, 02:31 AM

The command output is attached. It's self test says PASSED, but it has records of errors, though I'm not sure how to interpret them.

beachboy2 · 12-02-2022, 03:15 AM

mortoray,

You have carried out the short (2 minutes) test.

Try running the Extended Test.

mortoray · 12-02-2022, 04:11 AM

I ran `smartctl -t long /dev/sda` and it says it'll copmlete in 182 minutes.

Where does the output go?

mortoray · 12-02-2022, 05:14 AM

I think it's done. Some more errors found.

mortoray · 12-02-2022, 05:15 AM

`fsck -f /dev/sda1` reports no indication of errors.

```
e2fsck 1.46.5 (30-Dec-2021)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 238196/61054976 files (4.1% non-contiguous), 227705537/244190720 blocks
```

The errors from the smartctl log do seem to indicate it happens at power up.

mortoray · 12-02-2022, 05:17 AM

Looking at dmesg again, I think the smartlctl test was generating the below type of error:

```
[ 9038.990038] ata5.00: exception Emask 0x0 SAct 0x4080000 SErr 0x0 action 0x0
[ 9038.990051] ata5.00: irq_stat 0x40000008
[ 9038.990057] ata5.00: failed command: READ FPDMA QUEUED
[ 9038.990061] ata5.00: cmd 60/80:98:68:87:23/00:00:2c:00:00/40 tag 19 ncq dma 65536 in
res 41/40:00:68:87:23/00:00:2c:00:00/00 Emask 0x409 (media error) <F>
[ 9038.990077] ata5.00: status: { DRDY ERR }
[ 9038.990081] ata5.00: error: { UNC }
[ 9038.996538] ata5.00: configured for UDMA/133
[ 9038.996563] sd 4:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 9038.996570] sd 4:0:0:0: [sda] tag#19 Sense Key : Medium Error [current]
[ 9038.996574] sd 4:0:0:0: [sda] tag#19 Add. Sense: Unrecovered read error - auto reallocate failed
[ 9038.996579] sd 4:0:0:0: [sda] tag#19 CDB: Read(10) 28 00 2c 23 87 68 00 00 80 00
[ 9038.996582] blk_update_request: I/O error, dev sda, sector 740525928 op 0x0

READ) flags 0x80700 phys_seg 1 prio class 0
[ 9038.996605] ata5: EH complete
```

mrmazda · 12-02-2022, 09:44 AM

The output shows 22,069 hours uptime, yet earlier failures were at nearly three times that, indicating bogus data in the history.

Code:

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Fatal or unknown error        90%     22069         0

is worrisome, along with the media errors, DRDY ERR, auto reallocate failure, etc., suggesting it's time to contact the device maker's warranty/RMA department.

mortoray · 12-02-2022, 10:59 AM

Okay, thanks. I'll look to replace the drive then to ensure my data is safe.