Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

CAM Errors After Pool Switch

ere109

FreeNAS Experienced
Joined
Aug 22, 2017
Messages
145
Thanks
8
#1
The other day I lost about a dozen files from my jails SSD. Not a big deal. I backed up the remaining data, then tried to add a new SSD and resilver - the bad file errors wouldn't allow a resilver, so I manually pulled the old drive, deleted the pool and all data attached to it, then created a new pool on the new disk. However, I keep getting cam status errors on the new SSD, and I think it's ghost data trying to be written back to the old drive. I've already reset, and it didn't change anything. Here's the repeated DMESG data. I've run scrub on the new SSD and it shows no errors. Any thoughts? I've only re-installed one jail, so I could shut down and pull the disk again.

Code:
(ada2:ahcich3:0:0:0): ATA status: 00 ()
(ada2:ahcich3:0:0:0): RES: 00 00 00 00 00 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Timeout on slot 27 port 0
ahcich3: is 00000000 cs f800003f ss f800003f rs f800003f tfd 441 serr 00000000 cmd 00045a17
(ada2:ahcich3:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Error while READ LOG EXT
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 10 a0 99 0c 40 01 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 00 ()
(ada2:ahcich3:0:0:0): RES: 00 00 00 00 00 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Error while READ LOG EXT
(ada2:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 48 50 73 d5 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
 

ere109

FreeNAS Experienced
Joined
Aug 22, 2017
Messages
145
Thanks
8
#2
As an update, I just attempted to update the plex jail and was told it failed because it couldn't locate my old pool (SPARE_SSD) - the one I deleted and built a new pool on a new drive with a new name (SSD)...

Code:
% sudo iocage update plex
Password:
Snapshot: SSD/iocage/jails/plex@ioc_update_11.2-RELEASE-p8 created.
mount: /mnt/SPARE_SSD: No such file or directory
jail: /sbin/mount -t nullfs -o ro /mnt/SPARE_SSD/iocage/releases/11.2-RELEASE/root/bin /mnt/SPARE_SSD/iocage/jails/plex/root/bin: failed
 

ere109

FreeNAS Experienced
Joined
Aug 22, 2017
Messages
145
Thanks
8
#3
I deleted the pool, shut the system down, and moved the disk. It booted fine, but when I created the new pool, same problem again. This leads me to believe that either the brand new disk is bad, or my SSD drive bay is having problems. But I'm probably still missing something.
 

ere109

FreeNAS Experienced
Joined
Aug 22, 2017
Messages
145
Thanks
8
#4
I discovered that two of my VMs, which still pointed to the old pool, were still hanging around. I removed them, restarted the computer, and connected the new SSD pool, with great hopes. Getting Cam status timeouts here, as well... Now I'm also getting umouse and ukeyboard disconnect notices (probably because the VMs they were attached to are gone). Oh well. I'll keep working on it.
 

ere109

FreeNAS Experienced
Joined
Aug 22, 2017
Messages
145
Thanks
8
#5
I deleted all of the VMs, and haven't gotten a warning in about 24 hours. I suspect that the VMs were the ghosts, although I also haven't tried to write anything to the drive in this 24 hours. I just wanted to let it "settle" for a while. I'll make it my iocage drive and re-install a plugin, report back if there's an issue.
 
Top