Kernel confused two firewire drives??
From: Daniel Barrett (dbarrett_at_spinky.blazemonger.com)
Date: 07/29/04
- Next message: M Berger: "Re: UPS recommendation"
- Previous message: Jimmy Phillips: "Re: Don't quite understand Samba and file sizes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Jul 2004 04:27:25 GMT
On my Red Hat 9.0 system, I just had a weird situation where the
kernel thought a Firewire hard drive was corrupt when it wasn't. Can
anyone explain why this happened and how to prevent it from happening
again?
Today, the kernel reported that my 80 GB firewire drive (let's call it
drive "A") had a corrupt partition table or superblock. When I
examined the drive, fdisk reported the 80 GB drive was only 20 GB! I
could mount the drive but any access produced errors.
To make a long story short: the kernel was confusing drive A with
another firewire disk I'd used recently (call it drive "B") that was
only 20 GB. The problem went away after I rebooted the machine: Kudzu
appeared and offered to remove the configuration for a 20 GB drive. I
said yes. Now my computer recognized drive A as an 80 GB drive. I
think both drives may have claimed /dev/sda for their use at different
times.
This was a maddening problem that cost me several hours of wasted
effort. (While trying to "repair" drive A, I damaged its partition
table and had to restore it from backups.) Why did this happen, and
how can I make sure it doesn't happen again?
I use the "devlabel" system to detect and mount drive A, if that makes
any difference. I never did successfully mount drive B, but it was
present when I rebooted one day (when Kudzu first recorded its
configuration).
-- Dan Barrett dbarrett@blazemonger.com
- Next message: M Berger: "Re: UPS recommendation"
- Previous message: Jimmy Phillips: "Re: Don't quite understand Samba and file sizes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
