Find the answer to your Linux question:
Results 1 to 4 of 4
Ok, round 2xxx and something. I installed Kubuntu 11.04 on the system you see the specs of in my signature. It was running fine and so I decided to Ghost ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux User SkittleLinux18's Avatar
    Join Date
    Dec 2007
    Location
    Mesa, AZ
    Posts
    312

    Kubuntu 11.04 Install "Uncleanly Mounting"


    Ok, round 2xxx and something.

    I installed Kubuntu 11.04 on the system you see the specs of in my signature. It was running fine and so I decided to Ghost the drive using BartPE. I could not ghost it, though, because Ghost gave me an error message saying that the image creation failed, most likely due to the "partition unmounting cleaning." It then told me I could probably trying fixing it by running fsck. Well, I booted back into Kubuntu and ran the command but got a warning from the terminal saying,

    ...the filesystem is mounted and continuing can cause ***SEVERE*** file damage.

    Do you really wish to continue? (y/n)?
    So, I clicked no and came straight here. Would anybody care to clue me in as to what I have going on here? Thank you, in advanced.


    sudo fdisk -l output:
    Disk /dev/sda: 40.0 GB, 40020664320 bytes
    255 heads, 63 sectors/track, 4865 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0000675f

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 4866 39080960 83 Linux
    Linux user since: June 2007
    Current distro: kubuntu-14.04
    Specs: AMD Atholon 64 X2 3.2 Ghz, 4GB RAM, GeForce GTS 250 1GB VRAM
    High five if you saw the linux computers 24 used on their CTU sets.

  2. #2
    Administrator jayd512's Avatar
    Join Date
    Feb 2008
    Location
    Kentucky
    Posts
    5,025

    Talking

    So you ran an fsck on Kubuntu while you were booted to Kubuntu? And got that error?
    That's normal, bro. It's mounted at that point, and fsck can hurt a mounted file-system.

    Run fsck from a LiveCD.
    Jay

    New users, read this first.
    New Member FAQ
    Registered Linux User #463940
    I do not respond to private messages asking for Linux help. Please keep it on the public boards.

  3. #3
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    ^^
    Agreed, run fsck from a LiveCD and never run it on a mounted partition.
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux User SkittleLinux18's Avatar
    Join Date
    Dec 2007
    Location
    Mesa, AZ
    Posts
    312
    Thanks guys. I'm glad I didn't run the fsck then. So, I booted into the Natty LiveCD and opened a terminal. Following the instructions of post #2 on this Ubuntu thread, I ran a series of codes:

    ubuntu@ubuntu:~$ sudo e2fsck -C0 -p -f -v /dev/sda1
    152619 inodes used (6.24%)
    194 non-contiguous files (0.1%)
    222 non-contiguous directories (0.1%)
    # of inodes with ind/dind/tind blocks: 0/0/0
    Extent depth histogram: 143732/36
    1894163 blocks used (19.39%)
    0 bad blocks
    1 large file

    129851 regular files
    13291 directories
    59 character device files
    26 block device files
    0 fifos
    392 links
    9381 symbolic links (8754 fast symbolic links)
    2 sockets
    --------
    153002 files
    ubuntu@ubuntu:~$
    ubuntu@ubuntu:~$ sudo fsck /dev/sda1
    fsck from util-linux-ng 2.17.2
    e2fsck 1.41.14 (22-Dec-2010)
    /dev/sda1: clean, 152619/2444624 files, 1894163/9770240 blocks
    ubuntu@ubuntu:~$
    ubuntu@ubuntu:~$ sudo e2fsck -y -f -v /dev/sda1
    e2fsck 1.41.14 (22-Dec-2010)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information

    152619 inodes used (6.24%)
    194 non-contiguous files (0.1%)
    222 non-contiguous directories (0.1%)
    # of inodes with ind/dind/tind blocks: 0/0/0
    Extent depth histogram: 143732/36
    1894163 blocks used (19.39%)
    0 bad blocks
    1 large file

    129851 regular files
    13291 directories
    59 character device files
    26 block device files
    0 fifos
    392 links
    9381 symbolic links (8754 fast symbolic links)
    2 sockets
    --------
    153002 files
    Now, I am no linux expert, but this would appear to me that there is nothing wrong with my partition?

    ***EDIT***

    Ok, I just tried to run Ghost from my BartPE disk again and got the same result. The exact error message is:

    Ghost has detected problems with a Linux volume. The volume was most probably not unmounted cleanly. We recommend that you quit Ghost and correct the problem by running fsck on this volume.
    Alternatively, you may also continue normally.
    So I click continue and it just says the image creation was completed successfully at 100% with 0 MB copied.
    Last edited by SkittleLinux18; 06-07-2011 at 03:14 PM.
    Linux user since: June 2007
    Current distro: kubuntu-14.04
    Specs: AMD Atholon 64 X2 3.2 Ghz, 4GB RAM, GeForce GTS 250 1GB VRAM
    High five if you saw the linux computers 24 used on their CTU sets.

Posting Permissions

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