Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

BTFS Errors on New Configuration

Featured Replies

Hello, i received a notification that one of my cache drives cant be written to, so i checked the system log and see alot of BTRFS errors. 

I also have a duplicate drive in unassigned devices. I have a 60GB drive just for plex metadata.

Currently, that drive is active, and accessible, all seems fine, But i have the same drive with serial number and all, listed in unassigned devices. 

System diagnostics attached. 

All the drives in this system were being used with an older MB/CPU, recently upgraded the MB/CPU to a Asrock Pro RS/i3 12100. Also upgraded power supply from old OEM from a used computer to a EVGA 650W. 

Seems like it all started with this: 

Oct 10 06:02:33 Backup kernel: ata5.00: exception Emask 0x10 SAct 0x20000000 SErr 0x400100 action 0x6 frozen
Oct 10 06:02:33 Backup kernel: ata5.00: irq_stat 0x08000000, interface fatal error
Oct 10 06:02:33 Backup kernel: ata5: SError: { UnrecovData Handshk }
Oct 10 06:02:33 Backup kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Oct 10 06:02:33 Backup kernel: ata5.00: cmd 61/20:e8:60:6b:72/05:00:00:00:00/40 tag 29 ncq dma 671744 out
Oct 10 06:02:33 Backup kernel:         res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Oct 10 06:02:33 Backup kernel: ata5.00: status: { DRDY }
Oct 10 06:02:33 Backup kernel: ata5: hard resetting link
Oct 10 06:02:33 Backup kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 06:02:33 Backup kernel: ata5.00: configured for UDMA/133
Oct 10 06:02:33 Backup kernel: ata5: EH complete


And then turned into this, with the last BRTFS Error just continuing to count up in the "rd" field: 

Oct 10 06:02:56 Backup kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 10 06:02:56 Backup kernel: ata5.00: disable device
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=23s
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 Sense Key : 0x2 [current] 
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 ASC=0x4 ASCQ=0x21 
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 CDB: opcode=0x2a 2a 00 00 72 6b 60 00 05 20 00
Oct 10 06:02:56 Backup kernel: I/O error, dev sdb, sector 7498592 op 0x1:(WRITE) flags 0x1800 phys_seg 164 prio class 0
Oct 10 06:02:56 Backup kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Oct 10 06:02:56 Backup kernel: BTRFS: error (device sdb1) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction)
Oct 10 06:02:56 Backup kernel: ata5: EH complete
Oct 10 06:02:56 Backup kernel: BTRFS info (device sdb1: state E): forced readonly
Oct 10 06:02:56 Backup kernel: BTRFS warning (device sdb1: state E): Skipping commit of aborted transaction.
Oct 10 06:02:56 Backup kernel: BTRFS: error (device sdb1: state EA) in cleanup_transaction:1982: errno=-5 IO failure
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: rejecting I/O to offline device
Oct 10 06:02:56 Backup kernel: ata5.00: detaching (SCSI 5:0:0:0)
Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] Synchronizing SCSI cache
Oct 10 06:02:57 Backup kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 06:02:57 Backup kernel: ata5.00: ATA-9: SanDisk SDSSDP064G, 2.0.0, max UDMA/133
Oct 10 06:02:57 Backup kernel: ata5.00: 125045424 sectors, multi 1: LBA48 NCQ (depth 32)
Oct 10 06:02:57 Backup kernel: ata5.00: configured for UDMA/133
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sdb] Stopping disk
Oct 10 06:02:57 Backup kernel: scsi 5:0:0:0: Direct-Access     ATA      SanDisk SDSSDP06 0    PQ: 0 ANSI: 5
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: Attached scsi generic sg1 type 0
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write Protect is off
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Preferred minimum I/O size 512 bytes
Oct 10 06:02:57 Backup kernel: sde: sde1
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Attached SCSI disk
Oct 10 06:02:59 Backup kernel: BTRFS warning: duplicate device /dev/sde1 devid 1 generation 1932543 scanned by udevd (17894)
Oct 10 06:02:59 Backup unassigned.devices: Disk with ID 'SanDisk_SDSSDP064G_133116400085 (sde)' is not set to auto mount.
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 3, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 4, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 5, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 6, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 7, flush 0, corrupt 0, gen 0
Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 8, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 9, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 10, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 11, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 12, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 13, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 14, flush 0, corrupt 0, gen 0
Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 15, flush 0, corrupt 0, gen 0

 

backup-diagnostics-20221016-0822.zip

Solved by JorgeB

  • Community Expert
  • Solution
4 minutes ago, TurboStreetCar said:
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sdb] Stopping disk
Oct 10 06:02:57 Backup kernel: scsi 5:0:0:0: Direct-Access     ATA      SanDisk SDSSDP06 0    PQ: 0 ANSI: 5
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: Attached scsi generic sg1 type 0
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write Protect is off
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Preferred minimum I/O size 512 bytes

Device dropped offline and reconnected with a different identifier, check/replace cables. then see here for better pool monitoring.

  • Author

@JorgeB So it seems that drive is unwritable currently. After i replace the cables, how do i remove the duplicate drive, and make the drive writable?

  • Author

@JorgeB OK Replaced the SATA cable, and the duplicate drive moved to historical devices after the shutdown/power up.

It appears to be working currently. Interesting if the cable failed. Is that something common?

  • Community Expert
19 hours ago, TurboStreetCar said:

Is that something common?

Connection problems are more common than devices failing.

  • Author

@JorgeB Interesting, Appreciate the help, its been up and running for a while now with no further issues.

Thanks!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.