Are one of the disks beginning to fail?

These messages appeared in the kern log file the other day:

Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 18 38 ce 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 60 58 ce 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 b8 cf 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command

The disk announces itself as:

ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST500DM002-1BD142 KC45> ATA-8 SATA 3.x device
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6

Elsewhere on the Net I’ve been reading about faulty SATA cables and insufficient power. I doubt the 850 W power supply is to blame, unless there’s a faulty wiring. Maybe it’s a faulty SATA cable. Continue reading Are one of the disks beginning to fail?

Happy nameday, FreeBSD!

FreeBSD is approaching 20 years! I guess it all depends on what you regard as FreeBSD’s true birth. The baptism, the first commit to the CVS repository, the first release, or something else?

The first commit to the CVS repository was done on “Sat Jun 12 14:49:13 1993 UTC”. That’s 20 years and 6 days ago.

On this day, 20 years ago, the name “FreeBSD” was coined by Mr. David Greenman.

Slashdot ran a story on FreeBSD’s 20th birthday, on June 22th, 2013.

On August 28th later this year, I’ll celebrate 15 years of my ever growing experience with this wonderful operating system.

FreeBSD 1.0-RELEASE didn’t appear until November 1st, 1993.

That’s not bad for a free and open source operating system.

By the way, Unix turned 44 years old on April 20th. What’s keeping this big family of operating systems alive when most of their contemporaries have simply gone away?

F2 key not working on your Dell Latitude E6530? Try the F12 key and select BIOS Setup instead

A brand new Dell Latitude E6530 found its way to my office to be prepared for use for one of my coworkers. I was surprised to learn that the F2 key doesn’t allow you to enter the BIOS Setup. The computer simply freezes and the screen remains black. Just moments prior the firmware showed in the upper right corner a promise to enter the BIOS Setup. How rude.

I remembered there is a way to access the BIOS Setup from the boot menu provided by F12 key. Lo and behold, the BIOS Setup is available through this route.

It turns out this computer is running the A11 version of the System BIOS firmware and this version is a bit buggy, so watch out. Hopefully this issue will be resolved by the time A12 is available.

By the way, how come the S.M.A.R.T. feature is turned off by default in the BIOS Settings?

Addendum 2013-08-23

Revision A12 of the System BIOS firmware for Latitude E6530 is available. The aforementioned problem with the F2 key has been removed.

ZFS on NetBSD/amd64 6.0.1

My endeavour with ZFS on NetBSD/amd64 6.0.1 in late February and early March 2013 hasn’t been very positive. The kernel panics every now and then, even during the simplest of operations such as creating a new directory on a ZFS filesystem. The system was installed using UFS for the root filesystem, and the system was rock solid all along until I set up two additional hard drives and a modest mirrored zpool. Maybe the hassle’s due to the fact I use VirtualBox and not real hardware. Besides NetBSD/amd64 seems a bit sluggish when run in VirtualBox, at least compared to FreeBSD/amd64. Continue reading ZFS on NetBSD/amd64 6.0.1