← Older revision

Revision as of 00:43, 28 August 2026

(3 intermediate revisions by the same user not shown)

Line 14:

               c0t5000CCA02F613ACCd0  ONLINE        0     0     0

               c0t5000CCA02F613ACCd0  ONLINE        0     0     0

               '''c0t5000CCA02D0F6C44d0'''  UNAVAIL       0     0     0

               '''c0t5000CCA02D0F6C44d0'''  UNAVAIL       0     0     0

+

IF the drive is not fully faulted/"UNAVAIL", like this:

+

  # zpool  status

+

    pool: rpool

+

   state: DEGRADED

+

  config:

+

          NAME                       STATE      READ WRITE CKSUM

+

          rpool                      DEGRADED      0     0     0

+

            mirror-0                 DEGRADED      0     0     0

+

              c0t5000CCA02F613ACCd0  ONLINE        0     0     0

+

              '''c0t5000CCA02D0F6C44d0'''  DEGRADED      0     0     0

+

THEN you will need to OFFLINE the disk first, like so:

+

  '''zpool offline rpool''' c0t5000CCA02D0F6C44d0

+

2. Find the device path for the drive you want to remove:

2. Find the device path for the drive you want to remove:

Line 63:

Line 81:

   c4                             scsi-sas     connected    configured   unknown

   c4                             scsi-sas     connected    configured   unknown

   c4::w5000CCA02D0F6C45,0        disk-path    connected    '''unconfigured'''   unknown

   c4::w5000CCA02D0F6C45,0        disk-path    connected    '''unconfigured'''   unknown

+

IF, when you try to unconfigure, you get this error:

+

  # cfgadm -c unconfigure c4::w5000CCA02D0F6C45,0

+

  '''cfgadm: Hardware specific failure: failed to unconfigure SCSI device: I/O error'''

+

Go back to step one and make the disk '''offline''' in the ZFS pool

5. Turn on the Ok to Remove indicator for that drive:

5. Turn on the Ok to Remove indicator for that drive:

← Older revision		Revision as of 00:52, 28 August 2026
Line 34:		Line 34:
	'''Not After : Jun 26 01:04:33 2025 GMT'''		'''Not After : Jun 26 01:04:33 2025 GMT'''

−	Look for the "'''Not After'''" field. If it's in the past, then your "'''Kubernetes Ingress Controller Fake Certificate'''" has expired! This certificate is used for inter Rancher node communication. To make it renew, reboot ~~the~~ node. Wait for it to come back up, then reboot the next node etc. Rancher should be back.	+	Look for the "'''Not After'''" field. If it's in the past, then your "'''Kubernetes Ingress Controller Fake Certificate'''" has expired! This certificate is used for inter Rancher node communication. To make it renew, reboot a node. Wait for it to come back up, then reboot the next node etc. Rancher should be back.

Peter Pap's Technowiki - Recent changes [en]

Rancher Login Page Blank