boot into windows and run a thorough scan on the drive using scandisk. if
all is well then I'd say there is a bug of some sort in the vfat module.
- Matt
----- Original Message -----
From: "Patrick Nelson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 5:54 PM
Subject: RE: new drive
> Emmanuel Seyman wrote:
> ----------------->>>>
> What is the output of "fdisk -l /dev/hdb"?
> Does using "auto" instead of "vfat" solve the problem?
> Does the directory /dosd exist?
> ----------------->>>>
>
> 1. fdisk out:
>
> Disk /dev/hdb: 255 heads, 63 sectors, 14593 cylinders
> Units = cylinders of 16065 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hdb1 * 1 14593 117218241 c Win95 FAT32 (LBA)
>
> 2. auto instead of vfat?
> doesn't matter same error
>
> 3. /dosd exist?
> yes but I tried mounting on other directories as well. same result!
>
> Here is output of messages, first of which happens when I login and second
> when I try to mount:
>
> Mar 3 13:49:34 sol kernel: hda: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Mar 3 13:49:34 sol kernel: hda: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> ...
> Mar 3 14:47:24 sol kernel: VFS: Can't find a valid FAT filesystem on dev
> 03:41.
> Mar 3 14:52:39 sol kernel: VFS: Can't find a valid FAT filesystem on dev
> 03:41.
>
> dmesg shows the same:
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> VFS: Can't find a valid FAT filesystem on dev 03:41.
> VFS: Can't find a valid FAT filesystem on dev 03:41.
>
>
>
>
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
