Date: Thu, 07 Jan 2016 17:37:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 206008] Cannot detect hot-swapped SATA drives on camcontrol rescan/reset Message-ID: <bug-206008-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206008 Bug ID: 206008 Summary: Cannot detect hot-swapped SATA drives on camcontrol rescan/reset Product: Base System Version: 10.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: kburetta@benaroyaresearch.org CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Using this hardware: =E2=80=A2 Dell PowerEdge R530 o Intel Dual Port 82599EB 10-Gigabit SFP+ Network o Intel Quad Port I350 Gigabit Network Connection o LSI 9201-16e SAS HBA (6 Gbit/s) o 8x 16GB DDR4 RAM =E2=80=A2 SuperMicro SC847E16-RJBOD1 disk shelf o Supermicro PWS-1K41P-1R 1400W power supply =E2=80=A2 SFF-8088 to SFF-8088 external SAS cables =E2=80=A2 HDDs o Seagate ST6000NM024 6TB SATA enterprise HDD =E2=80=A2 SSDs o Samsung 850 Pro MZ-7KE1T0BW 1TB SATA SSD When I have a drive failure and replace said drive (hotswap). The device is= not detected in FreeBSD while the system is hot. Camcontrol rescan/reset all do= es not result in drive detection of the newly attached drive. However, restarting the server does cause the drive to be detected after bo= ot. This is what /var/log/messages looks like at the time of drive failure:: Jan 4 22:15:40 sea-zed-01 kernel: (da75:mps0:0:99:0): WRITE(16). CDB: 8a 0= 0 00 00 00 01 5c 72 9e 08 00 00 00 10 00 00 length 8192 SMID 628 command timeout= cm 0xfffffe0000b8f840 ccb 0xfffff8005d759800 Jan 4 22:15:44 sea-zed-01 kernel: (noperiph:mps0:0:4294967295:0): SMID 1 Aborting command 0xfffffe0000b8f840 Jan 4 22:15:44 sea-zed-01 kernel: (da75:mps0:0:99:0): WRITE(16). CDB: 8a 0= 0 00 00 00 01 5c 72 9e 08 00 00 00 10 00 00 Jan 4 22:15:44 sea-zed-01 kernel: mps0: (da75:mps0:0:99:0): CAM status: Command timeout Jan 4 22:15:44 sea-zed-01 kernel: IOCStatus =3D 0x4b while resetting devic= e 0x20 Jan 4 22:15:44 sea-zed-01 kernel: (da75:mps0:0:99:0): Retrying command Jan 4 22:15:44 sea-zed-01 kernel: da75 at mps0 bus 0 scbus0 target 99 lun 0 Jan 4 22:15:44 sea-zed-01 kernel: da75: <ATA ST6000NM0024-1HT SN02> s/n=20= =20=20=20=20=20=20 Z4D1AEAN detached Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: Crypto WRITE request failed (error=3D6). gpt/b15.eli[WRITE(offset=3D2993143136256, length=3D8192)] Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: g_eli_read_done() failed gpt/b15.eli[READ(offset=3D270336, length=3D8192)] Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: g_eli_read_done() failed gpt/b15.eli[READ(offset=3D5999999328256, length=3D8192)] Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: g_eli_read_done() failed gpt/b15.eli[READ(offset=3D5999999590400, length=3D8192)] Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: Crypto WRITE request failed (error=3D6). gpt/b15.eli[WRITE(offset=3D2993143144448, length=3D131072)] Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: Device gpt/b15.eli destroyed. Jan 4 22:15:44 sea-zed-01 kernel: GEOM_ELI: Detached gpt/b15.eli on last close. Jan 4 22:15:44 sea-zed-01 kernel: (da75:mps0:0:99:0): Periph destroyed Jan 5 07:17:12 sea-zed-01 [sssd[krb5_child[66189]]]: Preauthentication fai= led Jan 5 07:17:12 sea-zed-01 [sssd[krb5_child[66189]]]: Preauthentication fai= led Jan 5 07:17:12 sea-zed-01 sshd[66188]: in openpam_check_error_code(): pam_sm_authenticate(): unexpected return value 16 Jan 5 07:17:12 sea-zed-01 sshd[66185]: error: PAM: authentication error for kburetta from helpdesk0941.brivmrc.org /var/log/messages shows no new entries at the time of drive insertion. To reiterate, restarting the machine will detect the drive. But rescanning = or resetting the bus does not. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206008-6>