Pool Missing when replacing drive

[NasKar]

I have a drive that is going bad so I purchased another replacement and ran the burnin script on the new drive from spearfoot. After the drive passed I clicked offline on the bad drive and rebooted the system. Now I can't import the pool. I'm running raid Z2. I tried to reload my config file and still no luck after replacing the failed drive in the system.

Code:

Error: SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at e.t.json (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:1952335)
    at e.t.handleError [as selector] (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:1963205)
    at e.error (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:1842088)
    at e._error (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:3737084)
    at e.error (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:3736778)
    at XMLHttpRequest.a (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:1954495)
    at XMLHttpRequest.i (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:853535)
    at t.invokeTask (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:44121)
    at Object.onInvokeTask (http://192.168.5.48/ui/main.5e0d25dfb19b1248661c.bundle.js:1:2610127)
    at t.invokeTask (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:44042)
    at n.runTask (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:39299)
    at n.invokeTask [as invoke] (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:45211)
    at m (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:55907)
    at XMLHttpRequest.b (http://192.168.5.48/ui/polyfills.4e42ab25a6112b333361.bundle.js:1:56137)

Are there any option short of staring from scratch?

 

[NasKar]

I don't know why but the pool is there now and I'm resilvering the drive. I'm not sure what I did incorrectly but I'm happy I don't have to start over. That was scary.

 

[Heracles]

Hey NasKar,

FreeNAS just gave you a gift many users will envy. FreeNAS reminded you the importance of doing actual backups and for you, that reminder came without the loss of any data.

I just hope you got the point and understood how important it is to have actual backups of your data...

 

[NasKar]

Hey NasKar,

FreeNAS just gave you a gift many users will envy. FreeNAS reminded you the importance of doing actual backups and for you, that reminder came without the loss of any data.

I just hope you got the point and understood how important it is to have actual backups of your data...

I do have a backup but was not looking forward to the down time to do the restore. Any idea on what I did incorrectly to cause the problem. My best guess is I should have rebooted the server before taking the disk offline to clear out the kernel command I used to burnin the HDD.

 

[Heracles]

Hi again,

Good for you that you have a backup. Thanks to that, you will be able to recover of an incident like the loss of your pool.

As for what happened, I can only guess. Considering you said your pool is RaidZ2 and that you offlined only a single drive, the pool should have loaded properly even without a replacement drive. A poor contact in the cable may be part of the problem. In this case, a single poor contact in the cable may impact more than 1 drive. But this is pure speculation...

So I can not really tell you what happened. But FreeNAS itself being very robust, the hardware is the problem more often than not.

 

[pro lamer]

Anyway you may check your config backup for consistency... That Unexpected token < looks...

Sent from my phone