Cache Drive disappeared & then reappeared


soong

Recommended Posts

I was trying to preclear a couple of disks and when I mounted the 2nd one (I think I had a total of 4 unassigned drives mounted at that point) my cache disk disappeared (I didn't notice at that point). The next morning when I noticed, I rebooted and it didn't come back I feared it was dead... I then rebooted again but removed all the unassigned drives and it showed back up... and it works fine. Any ideas?

 

10/09 - 19:54 - Mounted Drive
10/09 - 19:55 - Started getting BTRFS errors - Around the same time I got a notification about my Cache drive missing but I didn't see the notification
10/09 - 19:56 - Started Preclear (already had one running)
10/10 - 08:55 - Noticed Cache drive is missing - Stoped Array
10/10 - 08:55 - Rebooted - Cache drive is not listed
10/10 - 08:57 - Rebooted - Cache drive is still not listed
10/10 - 08:58 - Rebooted - Cache drive is still not listed
10/10 - 09:10 - Shutdown - Remove all non-array drives from system - Power On - Cache Drive shows up (Samsung_SSD_860_QVO_1TB)
10/10 - 09:14 - Rebooted - Cache drive still shows up

log.txt

Edited by soong
typo
Link to comment

Are you hot swapping any devices? Several devices disconnecting/reconnecting, cache device (ATA2) dropped offline at that time:

 

Oct 12 14:04:53 Soong kernel: ata1: SATA link down (SStatus 0 SControl 300)
### [PREVIOUS LINE REPEATED 2 TIMES] ###
Oct 12 14:05:04 Soong kernel: ata1.00: disabled
Oct 12 14:05:04 Soong kernel: ata1.00: detaching (SCSI 2:0:0:0)
Oct 12 14:05:04 Soong kernel: sd 2:0:0:0: [sdh] Synchronizing SCSI cache
Oct 12 14:05:04 Soong kernel: sd 2:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Oct 12 14:05:04 Soong kernel: sd 2:0:0:0: [sdh] Stopping disk
Oct 12 14:05:04 Soong kernel: sd 2:0:0:0: [sdh] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Oct 12 14:05:04 Soong rc.diskinfo[10491]: SIGHUP received, forcing refresh of disks info.
Oct 12 14:05:04 Soong kernel: ata3: SATA link down (SStatus 0 SControl 300)
### [PREVIOUS LINE REPEATED 2 TIMES] ###
Oct 12 14:05:16 Soong kernel: ata3.00: disabled
Oct 12 14:05:16 Soong kernel: ata3.00: detaching (SCSI 4:0:0:0)
Oct 12 14:05:16 Soong kernel: sd 4:0:0:0: [sdj] Synchronizing SCSI cache
Oct 12 14:05:16 Soong kernel: sd 4:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Oct 12 14:05:16 Soong kernel: sd 4:0:0:0: [sdj] Stopping disk
Oct 12 14:05:16 Soong kernel: sd 4:0:0:0: [sdj] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Oct 12 14:05:16 Soong rc.diskinfo[10491]: SIGHUP received, forcing refresh of disks info.
Oct 12 14:05:24 Soong kernel: ata2: SATA link down (SStatus 0 SControl 300)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Oct 12 14:05:34 Soong kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 12 14:05:34 Soong kernel: ata1.00: ATA-10: ST4000DM004-2CV104,             ZFN1JR8M, 0001, max UDMA/133
Oct 12 14:05:34 Soong kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 12 14:05:35 Soong kernel: ata1.00: configured for UDMA/133
Oct 12 14:05:35 Soong kernel: scsi 2:0:0:0: Direct-Access     ATA      ST4000DM004-2CV1 0001 PQ: 0 ANSI: 5
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] 4096-byte physical blocks
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] Write Protect is off
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] Mode Sense: 00 3a 00 00
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: Attached scsi generic sg7 type 0
Oct 12 14:05:35 Soong kernel: sdh: sdh1
Oct 12 14:05:35 Soong kernel: sd 2:0:0:0: [sdh] Attached SCSI disk
Oct 12 14:05:35 Soong kernel: ata2: SATA link down (SStatus 0 SControl 300)
Oct 12 14:05:35 Soong kernel: ata2.00: disabled
Oct 12 14:05:35 Soong kernel: ata2.00: detaching (SCSI 3:0:0:0)

 

Link to comment

Yea, I think the hot-swapping is what's causing the issue. Although I'm surprised I haven't had more trouble with this.

 

My main array drives are connected via a SAS controller. My backup drives (which I hot swap) and the cache drive are connected to the motherboard SATA ports. It looks like my motherboard (from a ThinkServer TS140) doesn't support hot swapping so I guess that is causing issues... I've been meaning to order a SAS expender card.

 

If all the drives are connected via a SAS controller it should be safe to hot swap them?

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.