Announcement

Collapse
No announcement yet.

File System issue on Back-up Drive

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    File System issue on Back-up Drive

    Hello all,

    I'm having an issue getting through an R10 upgrade (Orig 80 gig to 500 gig).

    Following the instructions, I'm attempting to make a backup on a FAT32 partition.

    To do this I have a new 300gig drive that I partitioned under XP using Partition Magic. Initially, I tried simply putting a 196g FAT32 on teh drive.

    No Joy.

    I them deleted everything and tried a 2gig FAT16 and 2 - 150 gig FAT32 partitions. Still no joy.

    Finally, I created a 150 NTFS primary and 150 FAT32 logical.

    And still I get the same response when attempting to mount the FAT partition. In fact, the only partition I have been able to mount successfully is the NTFS partition (in read-only mode ).

    Here is teh error I'm getting:

    weaknees# mount dev/hda2 /mnt
    mount: error while guessing fllesystem type
    FAT: bogus logical sector size 0
    VFS: Can't find a valid FAT filesystem on dev 03:02.
    UMSDOS: msdos_read_super failed, mount aborted.
    FAT: bogus logical sector size 0
    VFS: Can't find a valid FAT filesystem on dev 03:02.
    FAT: bogus logical sector size 0
    VFS: Can't find a valid FAT filesystem on dev 03:02.
    mount: you must specify the filesystem type

    Can somebody please tell me what it is I'm doing wrong? Or what the syntax is for specifying the filesystem type when mounting?

    Thanks.
    Tags: None
  • #2
    Try just making one partition for the backup - just do one FAT32 partition of 10 GB or less.
    Been here a long time . . .

    Comment

    • #3
      Originally posted by WK-Michael View Post
      Try just making one partition for the backup - just do one FAT32 partition of 10 GB or less.
      Tried this. Actually, I wiped it and created a 5.7 gig primary FAT32 and now I'm getting this:

      weaknees# mount /dev/hdal /mnt
      knod: failed to exec Isbin/Nodprobe -s -k nls_cp437, errno = 2
      knod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
      knod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
      knod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
      weaknees#

      Comment

      • #4
        That sounds like incompatible hardware, sorry to say, or possibly a bad drive. Have you tried a different drive?
        Been here a long time . . .

        Comment

        • #5
          Same Problem

          I'm having the same problem as agardk. I'm upgrading a Pioneer 810H from an 80GB to a 300GB drive.

          I've tried many variations of primary, logical, active, passive FAT32 partitions using Partition Magic and I get those exact same error messages when inputting the "mount /dev/hda1 /mnt" command ("Mount: Error while guessing file system type" "FAT: Bogus logical sector size 0" "VFS: Can't find a valid FAT filesystem on dev 03:01"). I've even tried variations on the command, all with no luck. Admittedly I haven't tried a partition under 10GB so I'll do that now and update if it does the trick.

          Is this potentially an issue with the way Partition Magic partitions the drives? Do the drives need to be unmounted while partitioning? Any help tremendously appreciated... I miss my TiVo!

          Comment

          • #6
            PS - Does the cluster size matter? And what exactly should the partition be? "Active Logical", "Active Primary", "Passive"? Sorry if I sound uninformed, I'm new to hacking. It seems like this forum is a bit more friendly to *gulp* newbies...
            Last edited by tmichutka; 07-26-2007, 05:50 PM.

            Comment

            • #7
              I had the same problem and tracked it down to a typo on my behalf.

              The mount command is: mount /dev/hdW1 /mnt
              where you substitute the correct drive for "W"
              I left the "1" out, originally substituting "/hda" for "/hdW1",

              When I correctly used "/hda1" everything worked well.

              Comment

              Previous template Next
              Working...
              X