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
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
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
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
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
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
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
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
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
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
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
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
chown(1), mknod(1), sd(4), mount(8)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)