Find the answer to your Linux question:
Results 1 to 3 of 3
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    May 2004
    Vermont USA

    Fatal error: File too large.

    I am try to save a 20gig fat32 partition off of a failing hard drive.I have used dd_rescue to save an image of it.I would now like to repair the image file.

    I am using Fedora Core4 on a 160gig drive and have put the image file in my root home and I am working with it there.I have used fsck.vfat and g-part to try and repair it.Both error out with the following.

    [root@localhost ~]# fsck.vfat ryan2.img
    dosfsck 2.10, 22 Sep 2003, FAT32, LFN
    open ryan2.img:File too large

    [root@localhost ~]# gpart -g ryan2.img
    *** Fatal error: open(ryan2.img): File too large.

    I have tried googling for examples of file to large.I cannot seem to find a situation similiar to mine.I assume it is one of two things.
    1)Fedora Core4 can not handle large files
    2)the image file is too damaged to fix.

    Could anyone steer me in the right direction?

  2. #2
    This may be to do with the file system

    Look at this
    It shows that only certain file sizes can be used on certain FS.

    Maybe to do with that?!?1

  3. #3
    Just Joined!
    Join Date
    May 2004
    Vermont USA
    I am going to look into that.I need to know more of how the FAT32 system works.I have been doing some digging.I think the image needs to be mounted so it can be treated as a file system, not a single file.I think this is why g_parted and fsck will not work.The problem is the partition was damaged enough that the FAT is not recognized.So when I try to mount I get this.

    [root@localhost ~]# mount -o loop /root/ryan2.img /mnt/rysave/
    ioctl: LOOP_CLR_FD: Device or resource busy
    mount: you must specify the filesystem type
    [root@localhost ~]# mount -t vfat -o loop /root/ryan2.img /mnt/rysave
    mount: wrong fs type, bad option, bad superblock on /dev/loop1,
    missing codepage or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

    [root@localhost ~]# dmesg | tail
    NET: Registered protocol family 10
    Disabled Privacy Extensions on device c03e6820(lo)
    IPv6 over IPv4 tunneling driver
    eth0: no IPv6 routers present
    ISO 9660 Extensions: Microsoft Joliet Level 1
    ISOFS: changing to secondary root
    application mixer_applet2 uses obsolete OSS audio interface
    loop: loaded (max 8 devices)
    FAT: bogus number of reserved sectors
    VFS: Can't find a valid FAT filesystem on dev loop1.
    [root@localhost ~]#

  4. $spacer_open

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts