NAS4Free to FreeNAS Transition and hardware upgrade

Status
Not open for further replies.

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Don't modern CPU's just simply throttle down these days even in the event of a failed fan? So you'd just be slow-crawling, but never going down in smokes.

I know back in the day AMDs would go up in smoke(sometimes literally) while Intel's would crash and/or throttle down so badly you'd know something was wrong. I thought I read an article somewhere that its pretty much the opposite now, but I haven't really looked into it.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
They should throttle but with the error below I doubt the cpu throttles in my case.

freenas kernel: hwpstate0: set freq failed, err 6

Here is the cpu info:

[root@freenas ~]# grep -i cpu /var/run/dmesg.boot
CPU: AMD A10-5700 APU with Radeon(tm) HD Graphics (3400.07-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 16
cpu1 (AP): APIC ID: 17
cpu2 (AP): APIC ID: 18
cpu3 (AP): APIC ID: 19
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle2: <ACPI CPU Throttling> on cpu2
acpi_throttle3: <ACPI CPU Throttling> on cpu3
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Is there a way to have an encypted zfs pool come up locked? It once did, but now it comes up unlocked after a reboot.
 

Whattteva

Wizard
Joined
Mar 5, 2013
Messages
1,824
I know back in the day AMDs would go up in smoke(sometimes literally) while Intel's would crash and/or throttle down so badly you'd know something was wrong. I thought I read an article somewhere that its pretty much the opposite now, but I haven't really looked into it.

That was like back in the old days, like early late 90's early 2000's. I highly doubt any CPU vendors these days make them that fragile anymore. I'm pretty sure all of them would throttle and shut themselves off upon detecting extreme temperatures.

Mnemonic: your failed log is probably due to it being a desktop processor. So it probably can't be throttled on-demand (typically it's a laptop function to save power). But I'm pretty sure it will still auto-throttle itself when temperatures get too high.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Of cause it can be throttled on demand. On my windows box containing the same cpu, cpu-z shows 1400mhz when idle. When generating load it goes to 3700mhz.

Upgraded to freenas 9.1.1 release. No change for me.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Is there a way to have an encypted zfs pool come up locked? It once did, but now it comes up unlocked after a reboot.

That means your pool was not setup properly. In essence, FreeNAS has prevented you from being locked out of your own data without a key since you never generated one(or at least haven't generated one since you last clicked the "encryption rekey" button.

You need to do the following without rebooting(and in this order):

1. Click the encryption rekey button
2. Click the "change passphrase" button and enter the password.
3. Download the encryption key via the "Download key" button.
4. Download the recovery key via the "Add Recovery Key" button.
 
J

jkh

Guest
I know back in the day AMDs would go up in smoke(sometimes literally) while Intel's would crash and/or throttle down so badly you'd know something was wrong. I thought I read an article somewhere that its pretty much the opposite now, but I haven't really looked into it.


That has not been true for many years now. In fact, a modern Intel CPU (anything in the Core series, certainly) will only run at max clock for very short periods of time, ever, under load - we're talking microseconds. That's why all CPU benchmarks are now measured in cycles (usually, for crypto / string / memory operations, in cycles-per-byte) because only processor cycles mean anything. Clock speed is almost irrelevant - mythical even. I have done a lot of clock-speed / P-state measurements in real-time and it looks like a race car at full throttle - the "engine" constantly banging off the rev-limiter and revving down, then revving back up, many thousands of times per second. You'd never run a race car like that since you'd be rebuilding the engine every 20 minutes, but modern CPUs run like that all the time, they just call it "thermal management". ;-)
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
That means your pool was not setup properly. In essence, FreeNAS has prevented you from being locked out of your own data without a key since you never generated one(or at least haven't generated one since you last clicked the "encryption rekey" button.

You need to do the following without rebooting(and in this order):

1. Click the encryption rekey button
2. Click the "change passphrase" button and enter the password.
3. Download the encryption key via the "Download key" button.
4. Download the recovery key via the "Add Recovery Key" button.

Thx, cyberjock, that worked.
I had the pool set up correctly once, but I destroyed the pool many time because I wanted to conduct some tests and it seems that the pool I finally used was not encrypted properly.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Swap: 8192M Total, 8192M Free
I got 20GB Ram on a 7.8TB RaidZ1 and my swap always looks like this. Do I really need it?

Does anyone know what performance hit I take for a 4HD Raidz1 to a 5Raidz1? 30%? I could upgrade to a 5 hd, but one thing is for sure: 1hd more means one more point of failure.

Does 9.2 alpha base on Freebsd 9.2? I have heard good things about it in regards of zfs. Additonally a release is scheduled for mid september.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
RAIDZ1 should be avoided. See my link in my sig for why UREs are a real problem. The forum has plenty of threads where they've had significant data loss from RAIDZ1. For those reasons i'd highly recommend you go to a 5 disk RAIDZ2.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Yeah, I learned already that raid is no backup. I heard of companies going out of business because their stupid admins thought raid means everything is safe and sound.

Some years ago, I think I still used freenas 7 two drives died almost at the same time. But I was quite lucky. First, only one drive was completly dead, the other one had a lot of bad sectors. I did not recognize I had two faulty drives in the first place, so I replaced one and the system was resilvering. Freenas told me exactly which files it could not recover. Luckyly I had a backup for all of them. I recopied them and then I found out about the second drive which also explained why freenas could not recover some files. I replaced the second one and everything was o.k. again. But this was a close call. Therefore I try to have a current backup and keep it in another room in case of a fire.

The western digital green drives were a hell in a handbasket. The missing TLER made the situation above a lot worse. The faulty drives slowed the raidz and the whole system dramatically, because they constantly tried their stupid recovery procedure. I have now the red series and I seriously hope that if a drive fails I won't experience those slowdows again.

I still got the green drives I wanted to use them for backup, but I'm still not sure how to do it properly. I got 8 hot plug slots in my 4hu case. If I use 5 for raidz2 I still got three remaining. I want to put them in, do the backup and remove them. Because of their green nature I don't think it's a good idea to built a raid, especially with only three slots remaining. I think I will use them as three single zfs drives.

Is there a way to do the following in freenas:
1. /mnt/Mypool/Mydataset1/Path1toCopy -> /mnt/BackupDrive1
2. /mnt/Mypool/Mydataset1/Path2toCopy -> /mnt/BackupDrive2
3. /mnt/Mypool/Mydataset2/PathtoCopy -> /mnt/BackupDrive3
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Well, I found out rsync does the job, but why do I need a network service to do a simple local copy job? Isn't there a better way?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yes.. cp. LOL
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
i assume there is no way to schedule a cp job in the gui like rsync. If so wouldn't this make sense to add? A nas without a simple local copy in the gui?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
There sure is.. do a cronjob.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
I'm not familar with either rsync or cp. But my first impression is that rsync is much more clever. I don't think I can achieve a proper file sync with cp. I could copy everything evertime but that's not what I had in mind. I think I'll stick on rsync, even it uses the network stack.

I'll order another wd red drive to go for Raidz2. The rsync will do the backup job. Size of my raidz pool is 7.8TB, The three backup drives achieve as single drives combined 8.1TB. That should be enough to swallow the pool data.

Regarding the amdtemp.ko I'm somehow confident that this will be fixed when freenas upgrades to freebsd 9.2 release. Since this is on the horizon I'll stick with my amd hardware for the time being.

Thanks for all the help cyberjock!
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
I wanted to move from a Raidz1 to a raidz2. So I did a backup, killed the raidz1 added an HD and created an Raidz2.

Now I want to move my data back to the new pool. But I get a lot of errors. Are three drives faulty or what? Are some errors o.k. or should they be zero? If an error is reported what's happening in ZFS? Please have a look. All drives are nearly brand new. If they are faulty I'll return them. I don't expect much of consumer (NAS) drives, but enterprise drives are just too expensive.

Code:
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 90 77 4a 40 00 00 00 00 00 00
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 40 78 4a 40 00 00 00 01 00 00
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:26:09 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 d0 f3 74 40 00 00 00 00 00 00
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 80 f4 74 40 00 00 00 01 00 00
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 80 f5 74 40 00 00 00 00 00 00
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 30 f6 74 40 00 00 00 01 00 00
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:05 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 50 6b 79 40 00 00 00 00 00 00
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 00 6c 79 40 00 00 00 01 00 00
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 6d 79 40 00 00 00 00 00 00
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 b0 6d 79 40 00 00 00 01 00 00
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 b0 6e 79 40 00 00 00 00 00 00
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:27:10 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e0 35 ad 40 00 00 00 01 00 00
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 e0 36 ad 40 00 00 00 00 00 00
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 90 37 ad 40 00 00 00 01 00 00
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 90 38 ad 40 00 00 00 00 00 00
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:11 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 46 d0 40 00 00 00 01 00 00
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 d0 47 d0 40 00 00 00 00 00 00
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 80 48 d0 40 00 00 00 01 00 00
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 80 49 d0 40 00 00 00 00 00 00
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 30 4a d0 40 00 00 00 01 00 00
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:28:55 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 a8 51 f9 40 00 00 00 01 00 00
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 a8 52 f9 40 00 00 00 00 00 00
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:29:42 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 c8 1d 7c 40 01 00 00 01 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 c8 1e 7c 40 01 00 00 00 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 78 1f 7c 40 01 00 00 01 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 78 20 7c 40 01 00 00 00 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 28 21 7c 40 01 00 00 01 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 28 22 7c 40 01 00 00 00 00 00
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:32 freenas kernel: (ada2:ahcich2:0:0:0): Retrying command
Sep  4 13:32:49 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 a8 a0 89 40 01 00 00 01 00 00
Sep  4 13:32:49 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:32:49 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 6f af 40 01 00 00 00 00 00
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 b0 6f af 40 01 00 00 01 00 00
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 b0 70 af 40 01 00 00 00 00 00
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:33:41 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 b8 1d c3 40 01 00 00 01 00 00
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b8 b8 1e c3 40 01 00 00 00 00 00
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:34:07 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 30 94 20 40 02 00 00 01 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 30 95 20 40 02 00 00 00 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e0 95 20 40 02 00 00 01 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 e0 96 20 40 02 00 00 00 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 90 97 20 40 02 00 00 01 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 90 98 20 40 02 00 00 00 00 00
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:36:08 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:37:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 b3 4b 40 02 00 00 00 00 00
Sep  4 13:37:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 63 6d 40 02 00 00 01 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 d0 64 6d 40 02 00 00 00 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 80 65 6d 40 02 00 00 01 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 80 66 6d 40 02 00 00 00 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b8 30 67 6d 40 02 00 00 00 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e8 67 6d 40 02 00 00 01 00 00
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:37:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 00 3b ba 40 02 00 00 01 00 00
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 3c ba 40 02 00 00 00 00 00
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 50 3a ba 40 02 00 00 00 00 00
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:39:21 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:39:27 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 78 12 bb 40 02 00 00 01 00 00
Sep  4 13:39:27 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:39:27 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:40:40 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 68 1f fb 40 02 00 00 00 00 00
Sep  4 13:40:40 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:40:40 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 a8 8b 1e 40 03 00 00 00 00 00
Sep  4 13:41:25 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 50 bd 1e 40 03 00 00 00 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 00 be 1e 40 03 00 00 01 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 bf 1e 40 03 00 00 00 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 b0 bf 1e 40 03 00 00 01 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 b0 c0 1e 40 03 00 00 00 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 60 c1 1e 40 03 00 00 01 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b8 60 c2 1e 40 03 00 00 00 00 00
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:41:25 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 f8 6e 49 40 03 00 00 00 00 00
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 a8 6f 49 40 03 00 00 01 00 00
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 a8 70 49 40 03 00 00 00 00 00
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:42:18 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:42:46 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 10 b5 5e 40 03 00 00 01 00 00
Sep  4 13:42:46 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:42:46 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 d7 6b 40 03 00 00 00 00 00
Sep  4 13:43:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 50 cf 80 40 03 00 00 00 00 00
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 00 d0 80 40 03 00 00 01 00 00
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:23 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 a0 3c 9a 40 03 00 00 01 00 00
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 a0 3d 9a 40 03 00 00 00 00 00
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 50 3e 9a 40 03 00 00 01 00 00
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:43:54 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 c8 71 ce 40 03 00 00 01 00 00
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 c8 72 ce 40 03 00 00 00 00 00
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 78 73 ce 40 03 00 00 01 00 00
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 78 74 ce 40 03 00 00 00 00 00
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:01 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 68 c1 d2 40 03 00 00 00 00 00
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 18 c2 d2 40 03 00 00 01 00 00
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b8 18 c3 d2 40 03 00 00 00 00 00
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 d0 c3 d2 40 03 00 00 00 00 00
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:07 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:08 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 68 08 d4 40 03 00 00 00 00 00
Sep  4 13:45:08 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:08 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:45:14 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 00 6e d7 40 03 00 00 00 00 00
Sep  4 13:45:14 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:45:14 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 90 35 27 40 04 00 00 01 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 90 36 27 40 04 00 00 00 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 40 37 27 40 04 00 00 01 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 40 38 27 40 04 00 00 00 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 f0 38 27 40 04 00 00 01 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 b0 f0 39 27 40 04 00 00 00 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 a0 3a 27 40 04 00 00 01 00 00
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep  4 13:46:52 freenas kernel: (ada1:ahcich1:0:0:0): Retrying command
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
So ada0,1, and 2 appear to be having issues. That sounds more like a cabling issue. I'd try replacing the cable that attached those drives. Could be a PSU issue too, but the SATA cables are the easiest to try first.

You can also post the output of smartctl -a /dev/ada0 (and then the same for ada1 and ada2). But either you have 3 bad disks or something in common is wrong with them. You'll get the serial numbers from that command too so you can identify which disks those are.
 

mnemonic

Dabbler
Joined
Apr 6, 2013
Messages
36
Unbelievable. I had to replace four sata cables and "skip" one sata port to get rid of all the error messages. Well, all cables were from the same type, they came with the drive bay. That was strange because I have a second bay of exact same type with the same cables which I bought some years ago which don't have these problems. Never thought that sata cables or ports could be invisibly broken.

The NAS seems o.k. for now, I made the decision to migrate to a solution with ECC Memory support and low level IP-Management. I'll reuse the current cpu+mainboard for another htpc. But that has to wait some time since I need to invest - again.

Best regards
mnemonic
 
Status
Not open for further replies.
Top