Annoying log-messages: (aprobe0:ata1:0:1:0)

[Ganimed]

Hi all,

I have following question. Since I have upgraded from N4F 9.1.0.1 revision 306 to revision 636, I get always following messages in my log, which are annoying and slows down the boot-process:

• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): Error 5, Retry was blocked
• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): CAM status: Command timeout
• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
• Feb 7 21:20:52 nas4free kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): Error 5, Retry was blocked
• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): CAM status: Command timeout
• Feb 7 21:20:52 nas4free kernel: (aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00

Therefore, I was looking more in detail ...

Code: Select all

$ dmesg | grep ata1
ata1: <ATA channel> at channel 1 on atapci0
(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Error 5, Retry was blocked
(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Error 5, Retry was blocked
ada2 at ata1 bus 0 scbus1 target 0 lun 0

Code: Select all

$ dmesg | grep ada2
ada2 at ata1 bus 0 scbus1 target 0 lun 0
ada2: <SanDisk SDCFX3-008G HDX 5.00> CFA-4 device
ada2: 66.700MB/s transfers (UDMA4, PIO 512bytes)
ada2: 3825MB (7835184 512 byte sectors: 16H 63S/T 7773C)
ada2: Previously was known as ad2

and I have found out that these messages maybe caused from my CF-Card on which N4F is installed.
But what does these messages say? Is there some problem with the CF-Card?
How can I get rid of these messages, because they are annoying and slows down the boot process!

Do I have to change something in the BIOS or somewhere else?
I was searching around in Google, but I didn't find anything which matched to that problem.

Has someone an idea to solve that problem?

Thanks in advance!


[hr]1[/hr]Home:
NAS4Free 9.1.0.1 (revision 636) x86-full
VX800 AWRDACPI VIA C7-D Processor 1500MHz 1983MiB RAM
bus=1 hubaddr=1 port=0 devaddr=2 interface=0 VIA VT6202 USB 2.0 controller VIA 83C572 USB controller IP1001 10/100/1000 media interface

[al562]

Hi Ganimed,

These messages usually indicate a communication problem with a disk. You should try to troubleshoot and determine the cause, particularly since you did not see these errors before.
The first step is to try booting with LiveCD or LiveUSB after removing the CF card, see if the messages go away. Then put the CF card back in and boot LiveCD/USB again, see if the messages return. Try a different CF and see if the messages return.
It could indicate your CF is failing or has some errors on it. If it seems to be only that CF, then try a low level format and see if that clears the errors. Naturally you will want to backup your config and/or OS partition first so you can still run the server.

Let us know how it goes,
Al

[rostreich]

After your upgrade the sandisk is maybe shown with the other disks. can you check if smart is off for the sandisk?

[Ganimed]

Thank's for the answers! Yes, I have SMART completely disabled in N4F, since smartd fails to start during the boot process.
But in the configuration of SMART (Disks|Management|S.M.A.R.T.), I have only included my both WD-harddisks (/dev/ada0 & /dev/ada1) ... mhmm.

@Al: I will try in the next few days your hints and let you know what's happened. Maybe the CF-Card has really some errors and a low level format will help. Or else, it is better to replace my SanDisk with an industrial CF which is more resistant against errors and supports SMART. I will see it.

[Ganimed]

I've found out the next problem, why the start of smartd fails. It's the same issue as described in: viewtopic.php?f=57&t=2152.
So when I change the first part of the lines in smartd.conf, i.e. "/dev/ada0 -a -d ata -T permissive -s ..." into "/dev/ada0 -a -d atacam -T permissive -s ...", then when I start smartd by manual, the daemon starts successfully.
But when I reboot the system the changed config will be overwritten by the old config and the start of smartd fails. Which script I have to change, that during the boot process in smartd.conf will be written "atacam" instead of "ata"?
Thank's.


[hr]1[/hr]Home:
NAS4Free 9.1.0.1 (revision 636) x86-full
VX800 AWRDACPI VIA C7-D Processor 1500MHz 1983MiB RAM
bus=1 hubaddr=1 port=0 devaddr=2 interface=0 VIA VT6202 USB 2.0 controller VIA 83C572 USB controller IP1001 10/100/1000 media interface

[al562]

Hi Ganimed,

There was no clear resolution in that other topic unfortunately .

Rather than changing the system in this case I would recommend you start smartd manually at each boot. If you change the system it will not survive an upgrade and you will have to remember to modify the system again. If you do it via a post init script it will still work after an upgrade. Try the following:

1. Save your modified smartd.conf to one of your mount points.
2. In WebGUI Tab> System|Advanced|Command scripts create a post init that loads smartd using -c and specifying your saved, modified config file.

This way it will still work after an upgrade.

This should be fixed in the future, but for right now I am not sure if the problem is with FreeBSD itself or NAS4Free so my recommendation is to not get too creative for something that may be fixed in the next few releases.

Regards,
Al

[RedAntz]

I've found out the next problem, why the start of smartd fails. It's the same issue as described in: viewtopic.php?f=57&t=2152.
So when I change the first part of the lines in smartd.conf, i.e. "/dev/ada0 -a -d ata -T permissive -s ..." into "/dev/ada0 -a -d atacam -T permissive -s ...", then when I start smartd by manual, the daemon starts successfully.
But when I reboot the system the changed config will be overwritten by the old config and the start of smartd fails. Which script I have to change, that during the boot process in smartd.conf will be written "atacam" instead of "ata"?
Thank's.

Hi Ganimed,

Please try this build with S.M.A.R.T. patched :-
viewtopic.php?f=59&t=1868#p13713

[Ganimed]

Hello Al & RedAntz,

thank's for your fast replies! I will try your hints, when I have time. At the moment there is no time for that, since I'm preparing for an important exam. But afterwards, I will inform you both, if the patch works on my system and also if there is really a problem with my CF-Card or a simple low level format for the card is sufficient.

Best regards,
Ganimed.