SOLVED Can't Replace a Drive in a Pool, Error - [eservicestartfailure]

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
I'm attempting to replace a questionable drive in a pool and am having trouble. From Pool Status if I select the questionable drive and attempt to Replace it and get an error message - [eservicestartfailure] and it won't let me replace the drive. I get the same failure message if I take the drive Offline first and then try to add the new drive. I ended up reattaching the original questionable drive and the pool is Healthy....... for now.

I just when through this process a few days ago on another pool and it was a total no-brainier! :-/

This pool consists of a 6 drive RAIDZ2 vdev.
 
Last edited:
D

dlavigne

Guest
Which messages appear in /var/log/messages when you attempt to offline? If there aren't any messages there, they maybe in /var/log/middlewared.log instead.
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
@dlavigne attached is the section of /var/log/messages from today.

-Thnx
 

Attachments

  • messages_eservicestartfailure_TAC.txt
    34.1 KB · Views: 239

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
@dlavigne I did get the message asking if I wanted to clear the disk before using it and I said no.

Per this thread maybe I'll try again and say yes.
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
Thought I'd fish for some input before trying random options. I'll try the 'yes' option when I get a chance and let you know.
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
@dlavigne I went back in and selected Replace on the da7 disk, selected the replacement ada0 disk, checked the Force box and the system took off with no complaints...... go figure. Currently at 3% resilvering, so far so good.
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
@dlavigne since resilvering kept resetting to 1% I ended physically unplugging drive da7 and then resilvering completed with no more resets. Iisted below is a portion of the log file that appears to show serious problems with drive da7.

Side note, I thought was interesting that the FreeNAS Dashboard did not report my pool as DEGRADED when REPLACING the the da7 drive. As expected, when I physically unplugged the da7 drive the pool was reported as DEGRADED.

Code:
reenas.local kernel log messages:
> mps0: mpssas_prepare_remove: Sending reset for target ID 8
> da7 at mps0 bus 0 scbus0 target 8 lun 0
> da7: <ATA HGST HDN726040AL W7JH> s/n K7GVZNGL             detached
>       (da7:mps0:0:8:0): WRITE(10). CDB: 2a 00 03 79 e1 10 00 00 08 00 length 4096 SMID 967 terminated ioc 804b loginfo 31110d00 scsi 0 state c xfer 0
> (da7:mps0:0:8:0): WRITE(10). CDB: 2a 00 03 79 e1 10 00 00 08 00
> (da7:mps0:0:8:0): CAM status: CCB request completed with an error
> (da7:mps0: mps0:0:Unfreezing devq for target ID 8
> 8:0): Error 5, Periph was invalidated
> (da7:mps0:0:8:0): Periph destroyed
> mps0: SAS Address for SATA device = 2e474d678f67828f
> mps0: SAS Address from SATA device = 2e474d678f67828f
> da7 at mps0 bus 0 scbus0 target 8 lun 0
> da7: <ATA HGST HDN726040AL W7JH> Fixed Direct Access SPC-4 SCSI device
> da7: Serial Number K7GVZNGL           
> da7: 600.000MB/s transfers
> da7: Command Queueing enabled
> da7: 3815447MB (7814037168 512 byte sectors)
> mps0: mpssas_prepare_remove: Sending reset for target ID 8
> da7 at mps0 bus 0 scbus0 target 8 lun 0


1564415714590.png
 
Top