I'm testing out hotswapping an unassigned drive I use for daily backups.

Overall, it seemed to work. I unmounted the unassigned drive, spun it down, pulled it out, saw that it was gone, then reinstalled it. It then came back and mounted as before. So far, so good.

 

However, in the log after the physical removal, I see this:

Mar 6 10:55:49 server kernel: sd 3:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

 

Should I be concerned with this?

 

Here's the rest of the log during the hotswap event:

Mar 6 10:54:33 server unassigned.devices: Unmounting partition 'sdc1' at mountpoint '/mnt/disks/backup1'...
Mar 6 10:54:33 server unassigned.devices: Synching file system on '/mnt/disks/backup1'.
Mar 6 10:54:33 server unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdc1' 2>&1
Mar 6 10:54:33 server kernel: XFS (sdc1): Unmounting Filesystem
Mar 6 10:54:36 server emhttpd: read SMART /dev/sdc
Mar 6 10:54:36 server unassigned.devices: Successfully unmounted 'sdc1'
Mar 6 10:54:43 server emhttpd: spinning down /dev/sdc
Mar 6 10:55:47 server kernel: sd 3:0:0:0: device_block, handle(0x0009)
Mar 6 10:55:49 server kernel: sd 3:0:0:0: device_unblock and setting to running, handle(0x0009)
Mar 6 10:55:49 server kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Mar 6 10:55:49 server emhttpd: read SMART /dev/sdc
Mar 6 10:55:49 server kernel: sd 3:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Mar 6 10:55:49 server kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221102000000)
Mar 6 10:55:49 server kernel: mpt2sas_cm0: removing handle(0x0009), sas_addr(0x4433221102000000)
Mar 6 10:55:49 server kernel: mpt2sas_cm0: enclosure logical id(0x5d4ae5207ae4de00), slot(1)
Mar 6 10:55:50 server rc.diskinfo[10694]: SIGHUP received, forcing refresh of disks info.
Mar 6 10:59:27 server kernel: scsi 3:0:5:0: Direct-Access ATA WDC WD20EFAX-68F 0A82 PQ: 0 ANSI: 6
Mar 6 10:59:27 server kernel: scsi 3:0:5:0: SATA: handle(0x0009), sas_addr(0x4433221102000000), phy(2), device_name(0x0000000000000000)
Mar 6 10:59:27 server kernel: scsi 3:0:5:0: enclosure logical id (0x5d4ae5207ae4de00), slot(1)
Mar 6 10:59:27 server kernel: scsi 3:0:5:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Mar 6 10:59:27 server kernel: scsi 3:0:5:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
Mar 6 10:59:27 server kernel: sd 3:0:5:0: Power-on or device reset occurred
Mar 6 10:59:27 server kernel: sd 3:0:5:0: Attached scsi generic sg3 type 0
Mar 6 10:59:27 server kernel: end_device-3:5: add: handle(0x0009), sas_addr(0x4433221102000000)
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] 4096-byte physical blocks
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] Write Protect is off
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] Mode Sense: 7f 00 10 08
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 6 10:59:27 server kernel: sdc: sdc1
Mar 6 10:59:27 server kernel: sd 3:0:5:0: [sdc] Attached SCSI disk
Mar 6 10:59:27 server rc.diskinfo[10694]: SIGHUP received, forcing refresh of disks info.
Mar 6 10:59:28 server unassigned.devices: Adding partition 'sdc1'...
Mar 6 10:59:28 server unassigned.devices: Mounting partition 'sdc1' at mountpoint '/mnt/disks/backup1'...
Mar 6 10:59:28 server unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdc1' '/mnt/disks/backup1'
Mar 6 10:59:28 server kernel: XFS (sdc1): Mounting V5 Filesystem
Mar 6 10:59:28 server kernel: XFS (sdc1): Ending clean mount
Mar 6 10:59:28 server kernel: xfs filesystem being mounted at /mnt/disks/backup1 supports timestamps until 2038 (0x7fffffff)
Mar 6 10:59:28 server unassigned.devices: Successfully mounted 'sdc1' on '/mnt/disks/backup1'.

 

Just an error from the controller basically stating "Huh! The drive was here and now it isn't"

Cool. That's what I thought.

Thanks!