Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 38

Thread: A error occurred while mounting 0

  1. #21
    Join Date
    Apr 2010
    Location
    England
    Beans
    3,286

    Re: A error occurred while mounting 0

    blkid just tells you what's available on your computer, nothing more. In most cases it list something that isn't in your fstab, this is no cause for concern. If you want, post your fstab file and blkid output here, and we can take a look at it. Also, if you can run
    Code:
    sudo mount -a
    in a terminal, it may give some indication as to what's happening. (If it just appears to do nothing, then that means it hasn't found a problem)
    http://xkcd.com/293/
    There are 10 kinds of people in this world: Those who understand ternary, those who don't, and those who confuse it with binary.

  2. #22
    Join Date
    Dec 2010
    Beans
    12

    Re: A error occurred while mounting 0

    Thanks, I figured out the problem. The fstab retained two lines,
    "/dev/sdb1" and
    "/dev/sdb5",

    along with the new version UUID=xxxx lines. Those old /dev lines did not get the treatment I've seen elsewhere in this post i.e. "/dev/sdb1 was previously blah, blah" preceded by comment #. I assume the update process was supposed to do that.

    Anyway, I deleted those two lines and it booted up fine. Now to see what other remnants are laying around!

    Even though I figured out my issue, I want to thank every one who takes the time to post. I got many clues from previous postings, and like the other person said, I hope to get good enough with linux to be able to contribute to the forums. Thanks for making it a little bit easier to get from underneath windows.

  3. #23
    Join Date
    Dec 2010
    Beans
    2

    Re: A error occurred while mounting 0

    Hello, I am experiencing a similar problem. I tried to set up quota for users and cannot mount.......

    Result of blkid
    /dev/sda2: UUID="5E2EAF392EAF08DB" LABEL="OS" TYPE="ntfs"
    /dev/sda5: UUID="78eeaf6c-e21c-4b9f-a1b2-148613469ef4" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda6: UUID="7313d237-2125-4abd-829e-d2320ac83d81" TYPE="swap"
    /dev/sda7: UUID="a4554dae-700d-4cbc-88f8-b8b96b78508b" TYPE="ext4"
    /dev/sda8: UUID="bbd6a0ed-78c1-46ee-9d83-e651bfcd4f11" TYPE="ext4"
    /dev/sda9: UUID="141dfdbb-3f07-4ea3-82be-b5e1c9ad0477" TYPE="ext4"

    /etc/fstab:
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda9 during installation
    UUID=141dfdbb-3f07-4ea3-82be-b5e1c9ad0477 / ext4 errors=remount-ro,usrquota=aquota.usr,grpquota=aquota.grp,jqfmt=v fsv0 0 1
    # swap was on /dev/sda6 during installation
    UUID=7313d237-2125-4abd-829e-d2320ac83d81 none swap sw 0 0


    Please, could you check a see where the problem lies?
    Thanks,

    sakoto

  4. #24
    Join Date
    Apr 2010
    Location
    England
    Beans
    3,286

    Re: A error occurred while mounting 0

    Quote Originally Posted by sakoto View Post
    Hello, I am experiencing a similar problem. I tried to set up quota for users and cannot mount.......

    Result of blkid
    /dev/sda2: UUID="5E2EAF392EAF08DB" LABEL="OS" TYPE="ntfs"
    /dev/sda5: UUID="78eeaf6c-e21c-4b9f-a1b2-148613469ef4" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda6: UUID="7313d237-2125-4abd-829e-d2320ac83d81" TYPE="swap"
    7313d237-2125-4abd-829e-d2320ac83d81
    /dev/sda7: UUID="a4554dae-700d-4cbc-88f8-b8b96b78508b" TYPE="ext4"
    /dev/sda8: UUID="bbd6a0ed-78c1-46ee-9d83-e651bfcd4f11" TYPE="ext4"
    /dev/sda9: UUID="141dfdbb-3f07-4ea3-82be-b5e1c9ad0477" TYPE="ext4"
    141dfdbb-3f07-4ea3-82be-b5e1c9ad0477
    /etc/fstab:
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda9 during installation
    UUID=141dfdbb-3f07-4ea3-82be-b5e1c9ad0477 / ext4 errors=remount-ro,usrquota=aquota.usr,grpquota=aquota.grp,jqfmt=v fsv0 0 1
    # swap was on /dev/sda6 during installation
    UUID=7313d237-2125-4abd-829e-d2320ac83d81 none swap sw 0 0


    Please, could you check a see where the problem lies?
    Thanks,

    sakoto
    I'm no expert at setting up disk quotas, but from what I've read, you seem to be mixing journalled and unjournalled mount options. Also, I don't know if using quotas on the root (/) partition is a good idea, the info I've found seems to be focusing on /home partitions, but like I said, I'm no expert here, so I'll assume you know what you're doing.

    If you want unjournalled, use the following in fstab:
    Code:
    UUID=141dfdbb-3f07-4ea3-82be-b5e1c9ad0477 /               ext4    errors=remount-ro,usrquota,grpquota 0       1
    If you want journalled, use the following in fstab:
    Code:
    UUID=141dfdbb-3f07-4ea3-82be-b5e1c9ad0477 /               ext4    errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.grp,jqfmt=vfsv0 0       1
    Just to make sure you can tell the difference, the unjounalled entry uses "usrquota", and the journalled entry uses "usrjquota" and an argument as well as the extra part "jqfmt=vfsv0". You were mixing the two, which may have caused the problem.
    http://xkcd.com/293/
    There are 10 kinds of people in this world: Those who understand ternary, those who don't, and those who confuse it with binary.

  5. #25
    Join Date
    Dec 2010
    Beans
    2

    Re: A error occurred while mounting 0

    Thanks WorMzy, you're great!

  6. #26
    Join Date
    Feb 2011
    Beans
    2

    Re: A error occurred while mounting 0

    I also get that error message. Not sure what's going on. Any help would be appreciated :

    ben@ben-System-Product-Name:~$ sudo more /etc/fstab
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    /dev/sda2 / ext4 errors=remount-ro 0 1
    /dev/sda3 none swap sw 0 0
    /dev/sdb1 /media/sdb1 ntfs defaults 0 0
    /dev/sda4 /media/sda4 ntfs defaults 0 0
    //CINEMA/ntfs-sda3-cave /media/ntfs-sda3-cave cifs credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_
    mode=0777 0 0

    +++

    ben@ben-System-Product-Name:~$ sudo blkid
    /dev/sda1: UUID="A2DC7608DC75D6CF" TYPE="ntfs"
    /dev/sda2: UUID="0190847f-fd0e-4214-9eb0-a9c929b15128" TYPE="ext4"
    /dev/sda3: UUID="28799df0-ad3b-4474-88c3-5d9c4fb409ab" TYPE="swap"
    /dev/sda4: LABEL="forbackups" UUID="1EB039BB471567D1" TYPE="ntfs"
    /dev/sdb1: LABEL="blank_lucien" UUID="172BCD61BB3F75F7" TYPE="ntfs"

    +++

    ben@ben-System-Product-Name:~$ sudo fdisk -l

    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 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: 0xff25cd07

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 4462 35839968+ 7 HPFS/NTFS
    /dev/sda2 4462 5741 10268672 83 Linux
    /dev/sda3 5741 5773 262144 82 Linux swap / Solaris
    /dev/sda4 5773 60802 442015744 7 HPFS/NTFS

    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 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: 0x3c43e02e

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 60801 488384001 7 HPFS/NTFS

  7. #27
    Join Date
    Apr 2010
    Location
    England
    Beans
    3,286

    Re: A error occurred while mounting 0

    Quote Originally Posted by dooda View Post
    I also get that error message. Not sure what's going on. Any help would be appreciated :

    ben@ben-System-Product-Name:~$ sudo more /etc/fstab
    ...
    //CINEMA/ntfs-sda3-cave /media/ntfs-sda3-cave cifs credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_
    mode=0777 0 0
    The problem lies here. There is a line break after "dir_" which should not be there. Delete the line break so it looks like this:

    Code:
    //CINEMA/ntfs-sda3-cave    /media/ntfs-sda3-cave        cifs    credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
    http://xkcd.com/293/
    There are 10 kinds of people in this world: Those who understand ternary, those who don't, and those who confuse it with binary.

  8. #28
    Join Date
    Feb 2011
    Beans
    2

    Re: A error occurred while mounting 0

    Quote Originally Posted by WorMzy View Post
    The problem lies here. There is a line break after "dir_" which should not be there. Delete the line break so it looks like this:

    Code:
    //CINEMA/ntfs-sda3-cave    /media/ntfs-sda3-cave        cifs    credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
    Thanks, that did the trick.

  9. #29
    Join Date
    Mar 2011
    Beans
    2

    Re: A error occurred while mounting 0

    I am having the same problem, but mine occurred after a power outage while the machine was still running.

    blkid

    jacob@Carbon:~$ blkid
    /dev/sda1: UUID="ed557c15-b445-46d9-a878-b07a889c3589" TYPE="ext2"
    /dev/sda5: UUID="F0oPZr-ARmJ-47bw-0Aq0-6joo-CHKT-9AQZ2D" TYPE="LVM2_member"
    /dev/sdb1: UUID="8d277fb8-67c2-43bf-970b-5735d0b7d6db" TYPE="ext3"
    /dev/sdc1: UUID="2e8b6d04-361a-4a12-908c-5bc20fa47822" TYPE="ext2"
    /dev/mapper/Carbon-root: UUID="a682d64e-c36f-4713-8fcd-7fcdc339bc15" TYPE="ext4"
    /dev/mapper/Carbon-swap_1: UUID="e16b4021-6540-4647-8259-d535971a6dde" TYPE="swap"

    sudo nano /etc/fstab

    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    /dev/mapper/Carbon-root / ext4 errors=remount-ro 0 1
    # /boot was on /dev/sda1 during installation
    UUID=ed557c15-b445-46d9-a878-b07a889c3589 /boot ext2 defaults 0 2
    /dev/mapper/Carbon-swap_1 none swap sw 0 0
    /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
    # /dev/sdb1
    UUID=8d277fb8-67c2-43bf-970b-5735d0b7d6db /home/jacob/media ext3 defaults 0 2
    # /dev/sdc1
    UUID=2e8b6d04-361a-4a12-908c-5bc20fa47822 /home/jacob/video ext2 defaults 0 2
    #nfs
    /home/jacob /export/jacob none bind 0 0


    Thanks for any help in advance!

  10. #30
    Join Date
    Mar 2011
    Beans
    2

    Re: A error occurred while mounting 0

    Too expand on my previous post, I am also getting the following errors:

    /dev/sdc1 was not cleanly unmounted, check forced.
    /dev/mapper/Carbon-root: clean, 178619/2334720 files, 922399/9325568 blocks
    /dev/sdb1: clean, 33944/61054976 files, 131471098/244190000 blocks
    /dev/sda1: clean, 237/124496 files, 112072/248832 blocks
    init: ureadahead-other main process (879) terminated with status 4
    An error occurred while mounting /export/jacob
    mount: mount point /export/jacob does not exist
    mountall: mount /export/jacob [889] terminated with status 32
    mountall: Filesystem could not be mounted: /export/jacob
    Press S to skip mounting or M for manual recovery
    Last edited by jake91; March 31st, 2011 at 03:26 AM.

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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