From: Bradley Alexander <storm@tux.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Can someone _please_ tell me whats going on?
Date: Sun Dec 16 20:56:02 2001 [thread overview]
Message-ID: <1008557869.831.2.camel@defiant> (raw)
Hi all,
I posted last month (Please see message
<20011111194145.A715@sonsofthunder.yi.org>,
<20011112141948.P715@sonsofthunder.yi.org> regarding problems i was
having with lvm. I am working with a 1GHz Athlon machine, with 2 30GB
hard drives. One of the problems that I was seeing seek errors on the
hard drive. Everyone who responded mentioned that it was hardware
problems.
Well, I took that Quantum drive out and put an almost brand new Maxtor
(I took great pleasure in whacking windows on it) identical to my first
drive (Maxtor Maxtor 53073U6). I did the pvcreate, vgcreate and
lvcreate, followed by mkreiserfs. When I rebooted, again, I saw
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: DMA disabled
hdd: DMA disabled
ide1: reset: success
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error
}
hdc: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error
}
hdc: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=211681280,
sector=0
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error
}
I know for a fact that this drive is good, as was the Quantum. However,
the Quantum has since stopped working. Obviously it is not a hardware
issue. Can someone please tell me why whenever I try to turn a second
drive into a logical volume, I get drive errors?
I would appreciate any suggestions on why this is happening and how to
fix it.
--
--Brad
============================================================================
Bradley M. Alexander, CISSP | Co-Chairman,
Beowulf System Admin/Security Specialist | NoVALUG/DCLUG Security SIG
Debian/GNU Linux Developer | storm [at] debian.org
| storm [at] tux.org
============================================================================
If Guns cause Crime, then Matches cause Arson.
next reply other threads:[~2001-12-16 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 20:56 Bradley Alexander [this message]
2001-12-16 21:11 ` [linux-lvm] Can someone _please_ tell me whats going on? Friedrich Lobenstock
2001-12-16 21:41 ` Bradley Alexander
2001-12-17 1:22 ` Bradley Alexander
2001-12-17 2:41 ` Wolfgang Weisselberg
2001-12-17 6:18 ` Friedrich Lobenstock
2001-12-17 11:36 ` Bradley Alexander
2001-12-17 21:56 ` Bradley Alexander
2001-12-18 7:12 ` Benjamin Scott
2001-12-18 7:50 ` Lewis Bergman
2001-12-18 13:07 ` Bradley Alexander
2001-12-16 21:44 ` Steven Lembark
2001-12-17 7:11 ` Bradley Alexander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1008557869.831.2.camel@defiant \
--to=storm@tux.org \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox