<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>mount /dev/sdb1 -t vfat win<BR></DIV>
<DIV><FONT face=Arial size=2>--------------------</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Itamar Reis Peixoto</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>e-mail/msn: <A
href="mailto:itamar@ispbrasil.com.br">itamar@ispbrasil.com.br</A><BR>skype:
itamarjp <BR>icq: 81053601<BR>+55 11 4063 5033</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=garys@email.com href="mailto:garys@email.com">garys@email.com</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=fedora-list@redhat.com
href="mailto:fedora-list@redhat.com">For users of Fedora</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, October 27, 2007 1:24
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: media descriptor issue help
please</DIV>
<DIV><BR></DIV>
<DIV><BR><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid">-----
Original Message -----<BR>From: "Dave Stevens" <GEEK@UNISERVE.COM><BR>To: <A
href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</A><BR>Subject:
media descriptor issue help please<BR>Date: Fri, 26 Oct 2007 16:04:20
-0700<BR><BR><BR>Hi,<BR><BR>I have a F7 box that works fine. Recently a
Windows computer was hit by a<BR>stray 220 volt jolt and the power supply
died. I will in due course replace<BR>the power supply and see if the mobo
is hooped, but for the moment I am<BR>really interested in seeing if I can
recover the data off the drive. I've put<BR>the drive, a Seagate ATA 40 gig
into the F7 drive where it lives alongside<BR>the primary (F7) drive, a
Seagate SATA 320.<BR><BR>The BIOS correctly detects the type and model of
the ATA drive and the dmesg<BR>messages indicate that it is correctly
detected. The BIOS messages state the<BR>capacity and interface correctly
and say that S.M.A.R.T. is enabled and no<BR>errors are detected. If I set
the box to boot from the ATA drive Windows XP<BR>tries to boot and offers a
set of boot options. No matter which one I choose<BR>Windows starts to boot
then acts as if it can't deal with the drastically<BR>different hardware it
finds and reboots.<BR><BR>This leads me to believe that there is recoverable
data on the drive but I<BR>can't mount it in F7. Messages from dmesg read in
part as below:<BR><BR>ata7: PATA max UDMA/133 cmd 0x00000000000101f0 ctl
0x00000000000103f6 bmdma<BR>0x000000000001ffa0 irq 14<BR>ata8: PATA max
UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376
bmdma<BR>0x000000000001ffa8 irq 15<BR>ata7.00: ATA-6: ST340810A, 3.39, max
UDMA/100<BR>ata7.00: 78165360 sectors, multi 16: LBA<BR>ata7.00: configured
for UDMA/100<BR><BR>The drive is jumpered and cabled as primary
master<BR><BR>A mounting attempt onto empty directory /mnt/win gives
:<BR><BR>[root@localhost mnt]# mount /dev/sdb -t vfat win<BR>mount: wrong fs
type, bad option, bad superblock on /dev/sdb,<BR>missing codepage or other
error<BR>In some cases useful info is found in syslog - try<BR>dmesg | tail
or so<BR><BR>[root@localhost mnt]# dmesg | tail<BR>Bluetooth: HIDP (Human
Interface Emulation) ver 1.2<BR>ip6_tables: (C) 2000-2006 Netfilter Core
Team<BR>ip_tables: (C) 2000-2006 Netfilter Core Team<BR>Netfilter messages
via NETLINK v0.30.<BR>nf_conntrack version 0.5.0 (8192 buckets, 65536
max)<BR>eth0: no IPv6 routers present<BR>hfs: unable to find HFS+
superblock<BR>hfs: unable to find HFS+ superblock<BR>FAT: invalid media
value (0xb9)<BR>VFS: Can't find a valid FAT filesystem on dev sdb.<BR><BR>So
it seems that there is an invalid media descriptor on the ATA drive.
But<BR>the information seems to not be conclusive because in fact the
Windows boot<BR>sector is detected and a partial boot into Windows does in
fact take place. I<BR>don't know what to make of this or what to do
next.<BR><BR>Ideas? Diagnostics?<BR><BR>Dave<BR><BR>I have an adapter
ide=usb with power supply ( about $20 US ) for just such a problem - allows
you to read<BR>the disk without booting issues - like a flash drive. Knoppix
is sometimes helpful as well.
----gary<BR></GEEK@UNISERVE.COM></BLOCKQUOTE></DIV><BR>--
<DIV>Want an e-mail address like mine? </B><BR>Get a <B>free e-mail
</B>account today at <A href="http://www.mail.com/Product.aspx"
target=_blank>www.mail.com</A>!</DIV>
<P>
<HR>
<P></P>-- <BR>fedora-list mailing list<BR>fedora-list@redhat.com<BR>To
unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list</BLOCKQUOTE></BODY></HTML>