[NTLUG:Discuss] recuse the data

[Gilbert Morrow]

According to my A+ cert manual track 0 is where FAT resides that is
the outer most track of the first sector on the hard disc , so it may
be that FAT is corrupted .
The info saved there is what Windows used for the boot process and I
guess Linux uses the same space ? don't know about that thought.
It is located there so that the read /write head does not have to move
so much to access the data. And also that way the process never needs
to change.

On Wed, 10 Nov 2004 08:11:35 -0600, Terry Henderson <trryhend at gmail.com> wrote:
> On Wed, 10 Nov 2004 13:36:14 +0000, m m <llliiilll at hotmail.com> wrote:
> 
> 
> > Just get the chance to try.
> >
> > I got this error:
> >
> > Could not mount device.
> > The reported error was:
> > mount: wrong fs type, bad option, bad superblock on /dev/hda1 (it was the
> > only hd on the system)
> > or too many mounted file system.
> >
> > Any ideals?
> >
> 
> You've not given us much information to work with.
> What filesystem is on the drive?
> What command did you use to mount it?
> Does it spin up?  (Can you hear it spin up?)
> 
> If it is fat32 or fat16, (win98 or ME), try:
> mount -t vfat /dev/hda1 /mnt/[mountpoint]
> if it is ntfs try:
> mount -t ntfs /dev/hda1 /mnt/[mountpoint]
> 
> Listen to see if it will spin up when you issue mount commands, (just
> out of curiosity, to see if it spin's up), and / or listen to it as
> you boot the computer and see if it spins up on bootup.
> 
> May be that the drive is just not readable anymore, ruined beyond
> point of being able to read it anymore, but just don't know for sure
> at this point, not enough info to make a judgement call for sure, with
> the info you've given us so far.
> 
> 
> 
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
>