Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Wrong BIOS IDE Settings on a SATA disk (AHCI)? Post 302305419 by septima.pars on Wednesday 8th of April 2009 11:06:30 PM
Old 04-09-2009
Wrong BIOS IDE Settings on a SATA disk (AHCI)?

Hello,

I wanted to share an experience I had today which was quite a learning experience and perhaps useful for others who may run into the issue at some point in the future.


Basically, the scenario involves a OS which was installed on a machine which hardware-wise, had a SATA Drive. The web server Apache for this machine had earlier crashed a website. The machine I could confirm from a remote location was still operational (i.e. responding to ping attempts)

Taking a monitor/keyboard to the location of the server and subsequently plugging in a monitor, I noticed the logs were flooded with messages to the like of:


backlog limit exceeded
backlog limit exceeded
backlog limit exceeded
backlog limit exceeded
backlog limit exceeded
... ... ...



(which maybe points to a hard drive which may be failing.)

Trying next to login, the machine was unresponsive therefore I rebooted.
Next, I was able to console in as root, and noticed that certain log messages were flooding my shell session. They were similiar to the following:


hda failure rewrite_ext
reset succesful
hda failure rewrite_ext
reset succesful
hda failure rewrite_ext
reset succesful
hda failure rewrite_ext
hda failure rewrite_ext
... ... ...


I then had to switch to another console via Ctrl+Alt+F2/F3 to attempt to restart or at least check the status of the Apache service httpd.

I then had more messages which were flooding even my logged in sessions which I had never seen before. (No prompt and no way to enter commands)

____________________


In anycase, I came to the conclusion after searching a bit on google, is that perhaps the backlogs were flooding the hard drive and causing a DoS, which then maybe caused Apache to stop running.

Also searching google, I noticed that certain BIOS settings may contribute to this behavior, as the machine had no IDE drives, only SATA drives yet somehow the settings were entered incorrectly or not changed to "Enhanced" with a particular setting. (AHCI?)

Some of my colleagues thought the hard drive suspect of failing. Just an interesting experience.................... : )
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Using newfs to make file system on a sata disk using Acard adaptor

Hi All: I am using an adaptor between a 1TB SATA hard drive and solaris 8 box with 68 pin scsi. I use the format utility to partition the HD which works fine but when I use newfs, I get some errors. I will place them below. I have blocked and the error message is in red. Anybody got any... (1 Reply)
Discussion started by: mndavies
1 Replies

2. Filesystems, Disks and Memory

shift hard disk from primary IDE channel to secondary IDE channal

Wellcomes All, some times ago I 've installed a Debian ditribution on an Hard Disk who was set as Primary Master. Few days ago, I 've decided to install another Hard Disk with a different Operating System. When I did that, I turned off the old hard disk, and I mouted the new one on the Primary IDE... (1 Reply)
Discussion started by: thekarsillo
1 Replies

3. SCO

SATA AHCI Tape on SCO 5.0.7

Dear all, I'm newbie in SCO. I already purchase SCO 5.0.7 and SATA Tape Drive (not SCSI) for IBM server. not a cheap investment :( my problem is: I can't use my sata tape on sco 5.0.7 for backup my data because sco can't detect any sata tape has been plug into o/s. i already running "mkdev... (7 Replies)
Discussion started by: asumatezuka
7 Replies

4. SCO

SATA Hard Disk support by SCO OpenServer 5.05

Is SATA hard disk is suooprted by SCO OpenServer 5.05? If No, how to couter this problem. If yes, please provide the installation steps. (2 Replies)
Discussion started by: rakeshkumar9919
2 Replies

5. SCO

declare disk driver for IDE hard disk

hi I've a fresh installation of SCO 5.0.7 on the IDE hard disk. For SCSI hard disk I can declare, for example blc disk driver using: # mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies

6. Solaris

Changed to AHCI, can not access disk???

Here is my problem: I have an 1.5TB disk with OpenSolaris (b134, b151a) using non AHCI. I then changed to AHCI in BIOS, which results in severe problems: I can not boot the system. I suspect the problem is because I changed to AHCI. Now I have changed back to non AHCI, but still I can not... (0 Replies)
Discussion started by: kebabbert
0 Replies

7. UNIX for Dummies Questions & Answers

find physical disk type : SAS / SATA

Hi, Is there an easy way to find the disk-type from the command line or with another api ? sdparm works for SAS but not for SATA, hdparm works for SATA but not SAS. Thanks (1 Reply)
Discussion started by: coderd
1 Replies

8. Hardware

Sun fire 4270 reset BIOS settings after reboot

Hello, I am trying to perform Suse 10 SP3 installation via network in 6 Sun Fire 4270 M2 servers. The problem is that even if i set first prio boot device the hard disk the system always try to boot from network.And after the first restart the BIOS setting has been lost(and PXE come first... (2 Replies)
Discussion started by: @dagio
2 Replies

9. Linux

Debian Grub 1.99 alters BIOS (confirmed after formatting hard disk)

Hi, I am a long time Windows user and recently try this Debian Wheezy OS. Burn Debian ISO in Windows environment and then select DVD ROM drive to boot first in BIOS. The first installation of Debian (GNOME) was with multi-boot option that allows booting from hard disk and DVD drive. I then... (4 Replies)
Discussion started by: Linuxmun
4 Replies

10. Hardware

Hitachi SATA hard disk drive password locked

Hi everyone (see attachments) I bought an HP Elitebook 8460p on eBay and it came with a password-locked Hitachi hard drive which I was told is the original hard drive. I don't know the password for the drive and running the diagnostics tools I see the hard drive is healthy. I tried booting... (9 Replies)
Discussion started by: milhan
9 Replies
audit_warn(1M)						  System Administration Commands					    audit_warn(1M)

NAME
audit_warn - audit daemon warning script SYNOPSIS
/etc/security/audit_warn [option [arguments]] DESCRIPTION
The audit_warn utility processes warning or error messages from the audit daemon. When a problem is encountered, the audit daemon, auditd(1M) calls audit_warn with the appropriate arguments. The option argument specifies the error type. The system administrator can specify a list of mail recipients to be notified when an audit_warn situation arises by defining a mail alias called audit_warn in aliases(4). The users that make up the audit_warn alias are typically the audit and root users. OPTIONS
The following options are supported: allhard count Indicates that the hard limit for all filesystems has been exceeded count times. The default action for this option is to send mail to the audit_warn alias only if the count is 1, and to write a message to the machine console every time. It is recommended that mail not be sent every time as this could result in a the saturation of the file system that contains the mail spool directory. allsoft Indicates that the soft limit for all filesystems has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. auditoff Indicates that someone other than the audit daemon changed the system audit state to something other than AUC_AUDITING. The audit dae- mon will have exited in this case. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. ebusy Indicates that the audit daemon is already running. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. getacdir count Indicates that there is a problem getting the directory list or plugin list jjjjkj from audit_control(4). The audit daemon will hang in a sleep loop until the file is fixed. The default action for this option is to send mail to the audit_warn alias only if count is 1, and to write a message to the machine console every time. It is recommended that mail not be sent every time as this could result in a the saturation of the file system that contains the mail spool directory. hard filename Indicates that the hard limit for the file has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. nostart Indicates that auditing could not be started. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. Some administrators may prefer to modify audit_warn to reboot the system when this error occurs. plugin name error count text Indicates that an error occurred during execution of the auditd plugin name. The default action for this option is to send mail to the audit_warn alias only if count is 1, and to write a message to the machine console every time. (Separate counts are kept for each error type.) It is recommended that mail not be sent every time as this could result in the saturation of the file system that contains the mail spool directory. The text field provides the detailed error message passed from the plugin. The error field is one of the follow- ing strings: load_error Unable to load the plugin name. sys_error The plugin name is not executing due to a system error such as a lack of resources. config_error No plugins loaded (including the binary file plugin, audit_binfile(5)) due to configuration errors in audit_control(4). The name string is -- to indicate that no plugin name applies. retry The plugin name reports it has encountered a temporary failure. For example, the audit_binfree.so plugin uses retry to indicate that all directories are full. no_memory The plugin name reports a failure due to lack of memory. invalid The plugin name reports it received an invalid input. failure The plugin name has reported an error as described in text. postsigterm Indicates that an error occurred during the orderly shutdown of the audit daemon. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. soft filename Indicates that the soft limit for filename has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. tmpfile Indicates that the temporary audit file already exists indicating a fatal error. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsr | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ The interface stability is evolving. The file content is unstable. SEE ALSO
audit(1M), auditd(1M), bsmconv(1M), aliases(4), audit.log(4), audit_control(4), attributes(5) NOTES
This functionality is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. If the audit policy perzone is set, the /etc/security/audit_warn script for the local zone is used for notifications from the local zone's instance of auditd. If the perzone policy is not set, all auditd errors are generated by the global zone's copy of /etc/secu- rity/audit_warn. SunOS 5.10 26 May 2004 audit_warn(1M)
All times are GMT -4. The time now is 08:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy