like a more robust check.
Maybe I could test if /dev was a mount point?
Any other ideas?
Maybe checking for a running 'udevd' process?
Frank
--
Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A
Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A
Just because I
Hi again,
I've just seen I still had a wrong superblock in the subject of my
mail. Please just ignore, I fixed that while writing the last mail and
forgot to remove it. :)
Greets,
Frank
signature.asc
Description: Digital signature
On Thu, Feb 16, 2006 at 09:15:27AM -0600, Andrew Nelson wrote:
Feb 14 21:58:36 localhost kernel: hde: dma_timer_expiry: dma status == 0x21
Feb 14 21:58:46 localhost kernel: hde: DMA timeout error
Feb 14 21:58:46 localhost kernel: hde: dma timeout error: status=0x51 {
DriveRea
dy SeekComplete
On Thu, Feb 16, 2006 at 11:31:06AM -0600, Andrew Nelson wrote:
It's probably not your fault - blame /dev/hde! This sounds like a bad
error on the disk - you should really get a new one, and try to copy
/dev/hde to the new disk (with dd_rescue for example). This _might_ save
the data.
Hi,
I have a RAID-5 set up with the following raidtab:
raiddev /dev/md0
raid-level 5
nr-raid-disks 4
nr-spare-disks 0
persistent-superblock 1
parity-algorithmleft-symmetric
chunk-size 256
