Hello,

Ive been trying to get a Filecoin Miner setup for the past week on Ubuntu and I started getting some errors that I can't seem to solve.

The errors involve /dev/sda (a brand new WD 10TB HDD). I started by repartitioning and reformatting the drive. (the first time I followed some bogus directions that had me format the drive /dev/sda instead of the partition /dev/sda1.

I have already run fsck on the file system, it came back clean. I tried running a smartctl short test but it would go to 50% and the test would never finish. I swapped out the SATA cable for another one and it would go to 90% and hang there. Both SATA cables were from an old motherboard box but were in brand new condition. It says the test should take 2 minutes, but I left it running several hours. I moved the drive to a windows machine and ran data lifeguard diagnostic and it passed the short and long tests there.

I'm currently running memtest on the machine to check for memory errors (0 errors so far after 6h 30m).

Anyways, the errors Im getting are as follows:

blk_update_request: I/O error, dev sda sector 217517296 op 0x1WRITE) flags 0x0 phys_seg 88 prio class 0
several other errors similar to the above

Buffer I/O error on device sda1, logical block 271895986
(many more errors like the above but with different logical blocks)

EXT4-fs-error (device sda1): ext4_wait_block_bitmap:517: comm kworker/u256:0: Cannot read block bitmap - block_group = 8304, block_bitmap = 272


sd 2:0:0:0 [sda] tag#29 access beyond end of device

EXT4-fs (sda1) I/O error while writing superblock
EXT4-fs (sda1) Delayed block allocation failed for inode 270532627
EXT4-fs (sda1): This should not happen !! Data will be lost.

Any ideas are much appreciated here. The drive itself seems to be ok, so not sure what to do next.

Thanks!

Are you running a DOS MBR or GPT. GPT supports larger partitions and greater numbers than MBR. Anything over about 3T can be problematic for MBR (doable, but tricky).

Thanks for the reply. I'm using GPT.

Here's the output of print in parted.

Model: ATA WDC WD100EFAX-68 (scsi)
Disk /dev/sda: 10.0TB
Sector Size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 10.0TB 10.0TB ext4 primary



I believe the drive has 9.1TB of usable space (I remember seeing that value somewhere in the process of setting the drive up). Should I be using that value when creating a partition instead of the advertised value of 10TB?

WD big drive errors smell like SMR (shingled) drive errors. I have no experience but keep seeing it mentioned. Especially where WD swore they weren't shipping it, but they were. Linux had some issues supporting the dodgy arrangement initially due to lack of disclosure, but I would expect it to be ok now. What the access pattern of your workload ?.

I kept searching for answers and tried abstracting a bit by searching for drive errors instead of one of the specific error messages I got.

I tried running fsck with the -f option and it’s found what looks to be thousands of errors...
It’s funny though as I had the same errors as in my first post once already and I started over with re-partitioning and re-formatting.

Edit:

I ran fsck on the drive /dev/sda and not the partition /dev/sda1. I’m guessing that’s why it showed a ton of errors... whoops!

So I wrecked the file system by running fsck -f on the whole drive. I reformatted with mk2fs.ext4 and I’m attempting one more time to use this drive.


I’m not sure the access pattern, all I know is that it needs 600GB of free space to run lotus-bench.

Update: it appears my drive uses CMR (and not SMR) according to this page: https://nascompares.com/answer/list-...rd-drives-hdd/

Guess you could see what Ranish says about it.

Ran into the same errors again as in the first post. Not sure why I thought things would be any different this time around.

Reformatting again this time using mkfs.ext4 -cc to check for badblocks.

GPT is nowhere near a limit using this drive, and is the correct choice.

Specifying size in file system formatting can be done using percentage, so you avoid any issues about specifying the wrong size. If you specify the size, it should be using the numbers representing the real formatted blocks, not the advertised drive size. Advertised sizes are for selling hardware, not very specific technical specifications needed for formatting. the difference can be dramatic.

RE: -cc bad block checking. Good thought. If there are bad blocks then marking them out during format will reduce your total usable space but avoid the errors. On the other hand, the total bad blocks should be insignificant compared to the total usable space unless that is a bad drive.

Another option only for use if ext4 still results in errors with bad blocks marked out. You might try a format that handles errors differently. I am thinking about BTRFS.

It has been my experience that when a hard drive has the problems you are describing, part of the problem is in the original low level formatting of the hard drive and part of the problem is in how software is installed. The first problem CAN be repaired, but is time consuming. The second problem can only be repaired after the first problem. AFAIK depending on the software manufacturers design all software and operating systems just write to the next available space on the hard drive in accordance with the software designers layout.

That being said I suggest you download dban 2.2.6 from the dban website, virustotal it and either burn it to a CD or a USB drive. Then you should set aside AT least 24 hours for the software to do its magic. If you are like me it seems to take forever on anything larger than 1200GB The later versions of dban include some included adware etc. It has been my experience after running a one time triple wipe of the hard drive, all of the problems disappear. You will have to re-format your hard drive when it is finished.
Best of luck
Merlin

Thanks Merlin. I will try nwipe next (if I still get errors) once mkfs -cc is finished.
So far it’s 17.5 hours in and is 4% through the reading and comparing phase..

So mkfs -cc (badblocks) finally finished after 4 passes writing and checking different patterns and it came back with zero errors.

I even tried re-making partitions in parted again (using the % method instead of GB values in case that somehow messed things up)

I tried another unused SATA cable again, and tried a different power connector on the same cable to no avail.
Other than grabbing a SATA power cable from a different PC, I think I'm out of ideas.

Here's the output of dmesg (figured out a way to copy it directly to another computer so I could post it here).

[ 797.159079] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[27387.952088] ahci 0000:45:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x003b address=0x7ffffe00000 flags=0x0000]
[27418.225736] ata2.00: exception Emask 0x0 SAct 0x407fffc7 SErr 0x0 action 0x6 frozen
[27418.227068] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.228185] ata2.00: cmd 61/00:00:00:b2:0b/0a:00:3b:00:00/40 tag 0 ncq dma 1310720 ou
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.230460] ata2.00: status: { DRDY }
[27418.231620] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.232783] ata2.00: cmd 61/00:08:00:bc:0b/0a:00:3b:00:00/40 tag 1 ncq dma 1310720 ou
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.235149] ata2.00: status: { DRDY }
[27418.236342] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.237534] ata2.00: cmd 61/00:10:00:c6:0b/02:00:3b:00:00/40 tag 2 ncq dma 262144 out
res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.239968] ata2.00: status: { DRDY }
[27418.241201] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.242427] ata2.00: cmd 61/00:30:00:26:0f/0a:00:3b:00:00/40 tag 6 ncq dma 1310720 ou
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.244956] ata2.00: status: { DRDY }
[27418.246237] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.247493] ata2.00: cmd 61/00:38:00:30:0f/0a:00:3b:00:00/40 tag 7 ncq dma 1310720 ou
res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.250080] ata2.00: status: { DRDY }
[27418.251381] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.252669] ata2.00: cmd 61/f8:40:00:3a:0f/08:00:3b:00:00/40 tag 8 ncq dma 1175552 ou
res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.252670] ata2.00: status: { DRDY }
[27418.252671] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.252678] ata2.00: cmd 61/08:48:f8:42:0f/05:00:3b:00:00/40 tag 9 ncq dma 659456 out
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.260792] ata2.00: status: { DRDY }
[27418.260793] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.260796] ata2.00: cmd 61/00:50:00:48:0f/0a:00:3b:00:00/40 tag 10 ncq dma 1310720 ou
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.260799] ata2.00: status: { DRDY }
[27418.267838] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.267841] ata2.00: cmd 61/00:58:00:52:0f/0a:00:3b:00:00/40 tag 11 ncq dma 1310720 ou
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.267842] ata2.00: status: { DRDY }
[27418.267843] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.267846] ata2.00: cmd 61/00:60:00:5c:0f/0a:00:3b:00:00/40 tag 12 ncq dma 1310720 ou
res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.267847] ata2.00: status: { DRDY }
[27418.267848] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.267851] ata2.00: cmd 61/00:68:00:66:0f/0a:00:3b:00:00/40 tag 13 ncq dma 1310720 ou
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.267854] ata2.00: status: { DRDY }
[27418.285720] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.285723] ata2.00: cmd 61/00:70:00:70:0f/0a:00:3b:00:00/40 tag 14 ncq dma 1310720 ou
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.285724] ata2.00: status: { DRDY }
[27418.285726] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293554] ata2.00: cmd 61/18:78:00:7a:0f/05:00:3b:00:00/40 tag 15 ncq dma 667648 out
res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293555] ata2.00: status: { DRDY }
[27418.293556] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293559] ata2.00: cmd 61/e8:80:18:7f:0f/08:00:3b:00:00/40 tag 16 ncq dma 1167360 ou
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293560] ata2.00: status: { DRDY }
[27418.293561] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293564] ata2.00: cmd 61/00:88:00:88:0f/0a:00:3b:00:00/40 tag 17 ncq dma 1310720 ou
res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293565] ata2.00: status: { DRDY }
[27418.293565] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293568] ata2.00: cmd 61/00:90:00:92:0f/0a:00:3b:00:00/40 tag 18 ncq dma 1310720 ou
res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293569] ata2.00: status: { DRDY }
[27418.293570] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293573] ata2.00: cmd 61/00:98:00:9c:0f/0a:00:3b:00:00/40 tag 19 ncq dma 1310720 ou
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293574] ata2.00: status: { DRDY }
[27418.293574] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293577] ata2.00: cmd 61/00:a0:00:a6:0f/0a:00:3b:00:00/40 tag 20 ncq dma 1310720 ou
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293578] ata2.00: status: { DRDY }
[27418.293579] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.293582] ata2.00: cmd 61/00:a8:00:b0:0f/0a:00:3b:00:00/40 tag 21 ncq dma 1310720 ou
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.293585] ata2.00: status: { DRDY }
[27418.339094] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.339098] ata2.00: cmd 61/38:b0:00:ba:0f/03:00:3b:00:00/40 tag 22 ncq dma 421888 out
res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.339101] ata2.00: status: { DRDY }
[27418.345849] ata2.00: failed command: WRITE FPDMA QUEUED
[27418.345853] ata2.00: cmd 61/00:f0:00:a8:0b/0a:00:3b:00:00/40 tag 30 ncq dma 1310720 ou
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[27418.345853] ata2.00: status: { DRDY }
[27418.345857] ata2: hard resetting link
[27418.825759] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[27424.069950] ata2.00: qc timeout (cmd 0xec)
[27424.069963] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[27424.069965] ata2.00: revalidation failed (errno=-5)
[27424.071807] ata2: hard resetting link
[27434.071060] ata2: softreset failed (1st FIS failed)
[27434.073276] ata2: hard resetting link
[27444.070849] ata2: softreset failed (1st FIS failed)
[27444.072658] ata2: hard resetting link
[27479.072203] ata2: softreset failed (1st FIS failed)
[27479.073979] ata2: limiting SATA link speed to 3.0 Gbps
[27479.073980] ata2: hard resetting link
[27484.072289] ata2: softreset failed (1st FIS failed)
[27484.073973] ata2: reset failed, giving up
[27484.075544] ata2.00: disabled
[27484.075836] ata2: EH complete
[27484.075883] sd 1:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.075888] sd 1:0:0:0: [sda] tag#1 CDB: Write(16) 8a 00 00 00 00 00 3b 0b a8 00 00 00 0a 00 00 00
[27484.075891] blk_update_request: I/O error, dev sda, sector 990619648 op 0x1WRITE) flags 0x4000 phys_seg 51 prio class 0
[27484.075918] sd 1:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077518] sd 1:0:0:0: [sda] Sense not available.
[27484.077535] sd 1:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077536] sd 1:0:0:0: [sda] Sense not available.
[27484.077543] sd 1:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077545] sd 1:0:0:0: [sda] tag#2 CDB: Write(16) 8a 00 00 00 00 00 3b 0f ba 00 00 00 03 38 00 00
[27484.077546] blk_update_request: I/O error, dev sda, sector 990886400 op 0x1WRITE) flags 0x0 phys_seg 39 prio class 0
[27484.077552] sd 1:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[27484.077553] sd 1:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077554] sd 1:0:0:0: [sda] 4096-byte physical blocks
[27484.077555] sd 1:0:0:0: [sda] tag#3 CDB: Write(16) 8a 00 00 00 00 00 3b 0f b0 00 00 00 0a 00 00 00
[27484.077557] blk_update_request: I/O error, dev sda, sector 990883840 op 0x1WRITE) flags 0x4000 phys_seg 44 prio class 0
[27484.077562] sd 1:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077564] sd 1:0:0:0: [sda] tag#4 CDB: Write(16) 8a 00 00 00 00 00 3b 0f a6 00 00 00 0a 00 00 00
[27484.077565] blk_update_request: I/O error, dev sda, sector 990881280 op 0x1WRITE) flags 0x4000 phys_seg 44 prio class 0
[27484.077571] sd 1:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077572] sd 1:0:0:0: [sda] tag#5 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 9c 00 00 00 0a 00 00 00
[27484.077573] blk_update_request: I/O error, dev sda, sector 990878720 op 0x1WRITE) flags 0x4000 phys_seg 44 prio class 0
[27484.077578] sd 1:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077580] sd 1:0:0:0: [sda] tag#6 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 92 00 00 00 0a 00 00 00
[27484.077581] blk_update_request: I/O error, dev sda, sector 990876160 op 0x1WRITE) flags 0x4000 phys_seg 44 prio class 0
[27484.077583] sda: detected capacity change from 10000831348736 to 0
[27484.077586] sd 1:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.077588] sd 1:0:0:0: [sda] tag#7 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 88 00 00 00 0a 00 00 00
[27484.077589] blk_update_request: I/O error, dev sda, sector 990873600 op 0x1WRITE) flags 0x4000 phys_seg 44 prio class 0
[27484.077593] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3061841920 size 8032256 starting block 123860903)
[27484.077597] Buffer I/O error on device sda1, logical block 123858944
[27484.077604] Buffer I/O error on device sda1, logical block 123858945
[27484.077605] Buffer I/O error on device sda1, logical block 123858946
[27484.077606] Buffer I/O error on device sda1, logical block 123858947
[27484.077606] Buffer I/O error on device sda1, logical block 123858948
[27484.077607] Buffer I/O error on device sda1, logical block 123858949
[27484.077608] Buffer I/O error on device sda1, logical block 123858950
[27484.077609] Buffer I/O error on device sda1, logical block 123858951
[27484.077610] Buffer I/O error on device sda1, logical block 123858952
[27484.077611] Buffer I/O error on device sda1, logical block 123858953
[27484.078224] sd 1:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.078226] sd 1:0:0:0: [sda] tag#8 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 7f 18 00 00 08 e8 00 00
[27484.078227] blk_update_request: I/O error, dev sda, sector 990871320 op 0x1WRITE) flags 0x0 phys_seg 40 prio class 0
[27484.078229] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3053453312 size 8388608 starting block 123859200)
[27484.078327] sd 1:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.078328] sd 1:0:0:0: [sda] tag#9 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 7a 00 00 00 05 18 00 00
[27484.078330] blk_update_request: I/O error, dev sda, sector 990870016 op 0x1WRITE) flags 0x4000 phys_seg 23 prio class 0
[27484.078334] sd 1:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27484.078335] sd 1:0:0:0: [sda] tag#10 CDB: Write(16) 8a 00 00 00 00 00 3b 0f 70 00 00 00 0a 00 00 00
[27484.078336] blk_update_request: I/O error, dev sda, sector 990867456 op 0x1WRITE) flags 0x4000 phys_seg 45 prio class 0
[27484.078462] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3053453312 size 8388608 starting block 123858915)
[27484.079001] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3045064704 size 8388608 starting block 123857152)
[27484.079060] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3045064704 size 8388608 starting block 123856991)
[27484.079610] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3040870400 size 4194304 starting block 123828480)
[27484.079926] sd 1:0:0:0: [sda] tag#23 access beyond end of device
[27484.079994] sd 1:0:0:0: [sda] tag#31 access beyond end of device
[27484.079996] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3061841920 size 8388608 starting block 123861160)
[27484.080107] sd 1:0:0:0: [sda] tag#0 access beyond end of device
[27484.080109] EXT4-fs warning (device sda1): ext4_end_bio:309: I/O error 10 writing to inode 105447474 (offset 3061841920 size 8388608 starting block 123861248)
[27484.080201] JBD2: Detected IO errors while flushing file data on sda1-8
[27484.080204] sd 1:0:0:0: [sda] tag#1 access beyond end of device
[27484.080213] Aborting journal on device sda1-8.
[27484.080222] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5946: Journal has aborted
[27484.080223] sd 1:0:0:0: [sda] tag#2 access beyond end of device
[27484.080225] Buffer I/O error on dev sda1, logical block 1220575232, lost sync page write
[27484.080228] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[27484.080235] EXT4-fs (sda1): ext4_writepages: jbd2_start: 18432 pages, ino 105447474; err -30
[27484.080293] sd 1:0:0:0: [sda] tag#3 access beyond end of device
[27484.080299] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[27484.080332] sd 1:0:0:0: [sda] tag#4 access beyond end of device
[27484.080333] EXT4-fs (sda1): previous I/O error to superblock detected
[27484.080335] Buffer I/O error on dev sda1, logical block 59, lost async page write
[27484.080344] sd 1:0:0:0: [sda] tag#5 access beyond end of device
[27484.080346] Buffer I/O error on dev sda1, logical block 123207688, lost async page write
[27484.080349] Buffer I/O error on dev sda1, logical block 123207689, lost async page write
[27484.080350] Buffer I/O error on dev sda1, logical block 123207690, lost async page write
[27484.080352] Buffer I/O error on dev sda1, logical block 123207691, lost async page write
[27484.080353] Buffer I/O error on dev sda1, logical block 123207692, lost async page write
[27484.080355] Buffer I/O error on dev sda1, logical block 123207693, lost async page write
[27484.080356] Buffer I/O error on dev sda1, logical block 123207694, lost async page write
[27484.080361] sd 1:0:0:0: [sda] tag#6 access beyond end of device
[27484.080370] EXT4-fs (sda1): I/O error while writing superblock
[27484.080372] EXT4-fs (sda1): I/O error while writing superblock
[27484.080373] EXT4-fs error (device sda1): ext4_journal_check_start:61: Detected aborted journal
[27484.080376] EXT4-fs error (device sda1) in ext4_dirty_inode:6145: Journal has aborted
[27484.080377] EXT4-fs (sda1): Remounting filesystem read-only
[27484.080388] sd 1:0:0:0: [sda] tag#7 access beyond end of device
[27484.080415] EXT4-fs (sda1): previous I/O error to superblock detected
[27484.080425] sd 1:0:0:0: [sda] tag#3 access beyond end of device
[27484.080438] EXT4-fs (sda1): I/O error while writing superblock
[27484.081028] EXT4-fs (sda1): ext4_writepages: jbd2_start: 1024 pages, ino 105447473; err -30
[28823.847190] scsi_io_completion_action: 11 callbacks suppressed
[28823.847197] sd 1:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[28823.847201] sd 1:0:0:0: [sda] tag#18 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[30623.915939] sd 1:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[30623.915943] sd 1:0:0:0: [sda] tag#19 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[32423.985165] sd 1:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[32423.985169] sd 1:0:0:0: [sda] tag#20 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[34224.056759] sd 1:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[34224.056763] sd 1:0:0:0: [sda] tag#21 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[36024.124386] sd 1:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[36024.124390] sd 1:0:0:0: [sda] tag#22 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[37824.197663] sd 1:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[37824.197667] sd 1:0:0:0: [sda] tag#23 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[39624.270651] sd 1:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[39624.270655] sd 1:0:0:0: [sda] tag#24 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[41424.343370] sd 1:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[41424.343374] sd 1:0:0:0: [sda] tag#25 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[43224.416195] sd 1:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[43224.416199] sd 1:0:0:0: [sda] tag#26 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[45024.485379] sd 1:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[45024.485383] sd 1:0:0:0: [sda] tag#27 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00