Fsck on root partition without live CD

Hi,
For some unknown reason, I have to manually repair the root filesystem, but obviously every time I try, fsck tells me that the partition is mounted.
I know I could use some live CD, or pendrive, but turns out my live CD is VERY scratched, and my BIOS can't boot from a pendrive. Of course I could go and buy another cd, but there must be another way, so here I am.
Back in the old days, with sysv init, the only thing I had to do was enter the single-user-mode, and do the repair. Now, it is impossible, because "/" is always mounted. I've tried "systemd.unit=rescue.target" from grub, and "mount -o remount,ro /", I also prayed to my computer, but none of these things worked.
So, is there any way to fsck the root partition without using a pendrive or live cd?
Thank you.

You may not be able to directly boot from a pendrive, but you can boot to your bootloader.  From the bootloader, it should be possible to start Arch from the pendrive.  I am not at my Arch machine right now, and ssh'ing into it won't let me play in Grub, but I think Grub should be able to handle USB drives out-of-the-box.  If not, I know the correct drivers can be installed to the boot partition.
https://wiki.archlinux.org/index.php/Gr … _From_GRUB talks of how to modify the Grub menu to do this, but you should be able to hand-fly Grub by adapting this.

Similar Messages

  • Corrupted root partition - a possible rescue?

    Hello everyone, and thanks in advance for your help.
    I have an Arch box which since a few hours ago contained also Ubuntu. Then I decided to increase the size of my Arch /home partition to solve a space issue, and since I didn't use Ubuntu anymore since I installed Arch, I thought I could remove the Ubuntu partitions to make some room for my /home.
    So booted from an Ubuntu live cd and used gparted to remove the unwanted partitions. After the removal my partition table looked like this:
    /dev/sda5  /
    /dev/sda6  /boot
    /dev/sda7  /home
    /dev/sda8  /swap
    /dev/sda9   /var
    /dev/sda10 /tmp
    /dev/sda11 /usr
    /dev/sda12 /opt
    All of the above partitions used by Arch.
    Since the Ubuntu partitions were on the left of my Arch partitions, the / and /boot partitions had to be moved to the left in order for the /home partition to be grown.
    So here's the problem: while moving the root partition the system froze. I had to reboot. Then, Grub wouldn't load Arch anymore, and obviously Ubuntu did no longer exist. I loaded the Ubuntu live CD again and checked the root partition via gparted, and found that it was corrupted and not even mountable.
    And the question is: since all the other Arch partitions were left untouched, is there a possible way to reinstall only the needed files in the root partition?  Unfortunately, I didn't backup the partitions, so yes, I think I pretty much screwed it beyond repair, but I figure asking doesn't hurt.
    So thanks again for any help, and I hope I didn't miss any obvious wiki page or something. And sorry for my bad english too.

    I'd boot up a LiveCD and fsck the partition if you haven't already.
    If you have no luck there.  I've not tried it, but I can't see any reason why you couldn't:
    1) mkfs /dev/sda5 and mount it then unpack pacman and it's dependencies
    2) mount /dev/sda9 ro (or under something other than /var to preserve it and point pacman to the path of the syncdb) and mount proc, sys and dev from the livecd.
    3) chroot and 'pacman -S $(pacman -Qq)'
    4) prune the contents of directories for which a mountpoint exists
    Keep in mind that if you choose to go this way you could very well have two separate versions of packages installed (the latest under /, a previous version elsewhere).  Unless you confirm that all versions are identical to that which was installed previously, you're likely to run into trouble.
    Unless you have a reason not to, I think it would be better to have all partitions on their correct mountpoint before reinstalling packages.

  • Encrypted root fails without udev in initramfs

    I'm trying to decrease my boot time on my new machine. After testing, I found the two biggest time-wasters on my system were Xorg and the initramfs. I can't do much about X, because I'm by no means highly skilled with code and I'd rather not use my inexpert skills to dissect and strip the Xorg binary. My focus, therefore, has been on removing udev from the initramfs to make it load faster.
    I have tried this before, manually specifying the drivers and modules I need in the MODULES array and removing all hooks except base, encrypt, and fsck. My root partition is encrypted, but I may not even need the encrypt hook since I specify the dm_crypt and cryptsetup module/binary in the proper arrays. When I try and boot this, however, it hangs and then drops me to a prompt with the error "/dev/mapper/root not found." Here is my mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES="sd_mod ata_piix jfs dm_crypt"
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES="fsck.jfs fsck cryptsetup"
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev modconf keyboard encrypt fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    COMPRESSION="cat"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    I'm assuming udev is needed to scan for the root device and/or find the encrypted partition for cryptsetup to unlock. Is there a way around this? I'd like to cut out udev, as it is the biggest time hog within initramfs.
    I heard something about static /dev folders, but I'm not entirely sure how to go about setting that up or if it will work with an encrypted root...
    EDIT:
    I looked more closely at the initramfs shell on my latest test. Without udev, the /dev folder is still populated with my drive partitions and cryptsetup (when run manually from within initramfs) will unlock my root partition just fine. It seems to me that cryptsetup is failing to run initially for some reason. Thoughts?
    Last edited by ParanoidAndroid (2013-06-18 21:51:11)

    The encrypt hook requires the udev hook.  If you had taken a look at the actual install file for the encrypt mkinitpcio hook, you would have seen that it functions by pulling in a few udev rules which are activated when the init script calles "udevadm trigger".  If you want your initramfs to decrypt your filesystem without udev, you are going to have to write your own hook.
    As a side note, I have tried using mdadm vs mdadm_udev, as well as udev vs no-udev/btrfs in my initramfs, and having udev is always faster.  I think if you are so concerned about boot time, the best way to do that is to use a mush more simplified set up.  But since you use encryption, it would seem that security must have some signifigance to you, so that may not be an option.  You have to understand that the time spend in the initramfs also includes the time it takes for you to enter your password to decrypt your partition (if you use a password). 
    One non-obvious thing you can do to potentially speed up your initramfs load time is to not compress it.  As far as compression is concerned, lzo is the fastest, and 3.9 brought some not insignifigant speed improvments.  But having it just read the whole thing uncompressed I have foudn to be consistently faster.
    Really though, I think the whole idea of speeding up boot time is not really something worth pursuing unless you have something that is making it horribly slow. What kind of time is systemd-analyze repotying anyway?  (BTW, systemd-analyze is not really a true representation of experienced boot time as it only records time it takes to get to userspace, which is not what most people think it is)

  • [solved] Encrypted root partition decrypts, not recognised on boot

    Hello everyone
    As per the wiki entry on system encryption with LUKS, I have an unencrypted boot partition (sda1) and a second encrypted partition (sda2) containing everything else, including root. This is on an eeepc 901 (I'm posting here, though, as I understand this as a mounting issue rather than laptop/netbook specific).
    I have just done a full system upgrade, including moving to kernel 2.6.34-ARCH. Now, although I am prompted for the passphrase, which is accepted. I subsequently see the following:
    ::Checking Filesystems [BUSY] fsck.ext2: No such file or directory while trying to open /dev/mapper/root
    /dev/mapper/root:
    The superblock could not be read or does not describe a correct ext2 filesystem.
    If the device is valid and it really does contain an ext2 filesystem (and not swap or
    ufs or something else), then the superblock is corrupt, and you might try running
    e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    Runnig ecfsck -b 8193 /dev/mapper/root simply results in that error message being repeated. Googling and searching the forum only really found this thread to be anything similar. As per the suggestions there, the encrypted partition is last in /etc/fstab and the <options> value is populated:
    /dev/sda1 /boot ext2 defaults 0 1
    /dev/sdb1 /mnt/sdb1 vfat rw #This is an sdhc card permanently inserted
    /dev/mapper/root / ext2 defaults 0 1
    /etc/crypttab is entirely commented out, as it advises the root partition needs to be defined in the initramfs.
    I can decrypt and open the partition using systemrescuecd, and fsck confirms the partition is clean. Equally, I can access the decrypted partition from the maintenance shell I get dumped into.
    I'd be very grateful for any suggestions.
    Last edited by Sagittar (2010-07-17 03:40:49)

    Thanks for responding. I can confirm /dev/sda2 is ext2: after mounting both partitions with the -r flag, df -T reports ext2 file systems. (The theory is that ext2 helps prolong the life of the SSD in the eee pc. Not that that's entirely relevant here.)
    I can't see a way of booting off sysresccd with root=/dev/sda2 without decrypting /dev/sda2 first. I am able to do that from Grub. Is there something I'm missing?
    However, when I pay more attention to what happens on sysresccd when I decrypt the partition, I get the following:
    % cryptsetup luksOpen /dev/sda2 root
    Enter passphrase for /dev/sda2:
    device-mapper: remove ioctl failed: Device or resource busy
    Key slot 0 unlocked.
    So, although I can then mount /dev/sda2 (or, to be precise, /dev/mapper/root) as normal, my guess is that the third line is a big clue as to why my normal boot process fails. I am pursuing that now.

  • Copied my Arch root partition to a new one but I can't boot [SOLVED]

    I booted to my arch live cd and copied my Arch / partition (/dev/sda1) to an empty partition (/dev/sda9) via a cp -a command.  The new partition should now contains an exact copy of my old root partition.  I also modified the /etc/fstab in the new partition to reflect the new block device for the root filesystem.  I also added a line to my menu.lst to boot it.  I didn't do something right because I get a kernel panic when grub boots into the new partition.
    menu.lst entry:
    title Arch Testing
    root (hd0,8)
    kernel /boot/vmlinuz26 root=/dev/sda9 ro quiet vga=773 acpi_enforce_resources=lax vga=773
    initrd /boot/kernel26.img
    Ideas?
    EDIT: Just read this wiki page
    The fix as root:
    mount /dev/sda9 /mnt
    cd /mnt/dev
    rm console ; mknod -m 600 console c 5 1
    rm null ; mknod -m 666 null c 1 3
    rm zero ; mknod -m 666 zero c 1 5
    mount -o bind /dev /mnt/dev
    mount -t proc none /mnt/proc
    mount -o bind /sys /mnt/sys
    cd /
    chroot /mnt /bin/bash
    mkinitcpio -p kernel26
    Last edited by graysky (2009-12-05 15:14:01)

    Since you can't delete Apple IDs and having multiple Apple IDs can cause confusion, what you may want to do is rename your existing Apple ID to the new email (desired Apple ID).  That would in effect do what you want, get rid of the old and give you the new.
    See "Apple ID: Changing your Apple ID"
    ivan

  • Root partition suddenly full while updating packages with Pacman

    Hello
    I'm not sure if this is a problem with Pacman, but my root partition seems to have become completely full while updating my system using pacman -Syu. Before updating anything, there seems to have been an update to a new version of Pacman (3.3.1-1) that needed to be installed before updating packages.
    In the middle of the updates, I got this error:
    error: error writing to file '/var/cache/pacman/pkg/openoffice-base-3.1.1-2-x86_64.pkg.tar.gz': No space left on device
    Also, I don't know if this is related, but I got a lot of 'not found' errors after that.
    The entire output from everything:
    ~ $ sudo pacman -Syu
    Password:
    :: Synchronizing package databases...
    core 34.6K 101.4K/s 00:00:00 [#####################] 100%
    extra 427.5K 394.3K/s 00:00:01 [#####################] 100%
    community 374.7K 362.2K/s 00:00:01 [#####################] 100%
    :: The following packages should be upgraded first :
    pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n] y
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): pacman-3.3.1-1
    Total Download Size: 0.60 MB
    Total Installed Size: 2.10 MB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from core...
    pacman-3.3.1-1-x86_64 618.9K 455.6K/s 00:00:01 [#####################] 100%
    checking package integrity...
    (1/1) checking for file conflicts [#####################] 100%
    (1/1) upgrading pacman [#####################] 100%
    ~ $ sudo pacman -Syu
    :: Synchronizing package databases...
    core is up to date
    extra is up to date
    community is up to date
    :: Starting full system upgrade...
    resolving dependencies...
    looking for inter-conflicts...
    Targets (42): taglib-extras-1.0.1-1 qt-4.5.3-2 liblastfm-0.3.0-4
    loudmouth-1.4.3-1 libmtp-0.3.7-1.1 amarok-2.2.0-1 apr-1.3.9-1
    db-4.8.24-1 apr-util-1.3.9-3 apache-2.2.13-3 bluez-4.54-1
    python-2.6.3-1 dbus-python-0.83.0-2.1 device-mapper-2.02.53-1
    eclipse-3.5.1-1 gpm-1.20.6-3 perl-5.10.1-3 groff-1.20.1-3
    vim-7.2.266-1 gvim-7.2.266-2 heimdal-1.2.1-7 inkscape-0.46-13
    iproute2-2.6.29-2 lib32-db-4.8.24-1 lib32-heimdal-1.2.1-7
    libical-0.44-1 libsasl-2.1.23-2 lm_sensors-3.1.1-2
    lvm2-2.02.53-1 nexuiz-data-2.5.2-1 nexuiz-2.5.2-1
    redland-1.0.9-4 openoffice-base-3.1.1-2 pam-1.0.4-2
    php-5.3.0-5 pstoedit-3.50-1 ruby-1.9.1_p243-2 soprano-2.3.1-1
    texlive-bin-2009.4-1 texlive-core-2009.15574-1 wget-1.12-1
    xchat-2.8.6-5
    Total Download Size: 1354.95 MB
    Total Installed Size: 2035.02 MB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from core...
    db-4.8.24-1-x86_64 4.7M 432.0K/s 00:00:11 [#####################] 100%
    device-mapper-2.02.... 479.0K 287.9K/s 00:00:02 [#####################] 100%
    gpm-1.20.6-3-x86_64 173.2K 243.7K/s 00:00:01 [#####################] 100%
    perl-5.10.1-3-x86_64 13.5M 412.5K/s 00:00:33 [#####################] 100%
    groff-1.20.1-3-x86_64 4.1M 365.7K/s 00:00:12 [#####################] 100%
    heimdal-1.2.1-7-x86_64 2.8M 368.5K/s 00:00:08 [#####################] 100%
    iproute2-2.6.29-2-x... 489.0K 303.8K/s 00:00:02 [#####################] 100%
    libsasl-2.1.23-2-x86_64 118.5K 252.4K/s 00:00:00 [#####################] 100%
    lvm2-2.02.53-1-x86_64 930.3K 327.3K/s 00:00:03 [#####################] 100%
    pam-1.0.4-2-x86_64 537.8K 289.5K/s 00:00:02 [#####################] 100%
    wget-1.12-1-x86_64 672.4K 308.0K/s 00:00:02 [#####################] 100%
    :: Retrieving packages from extra...
    qt-4.5.3-2-x86_64 26.9M 418.8K/s 00:01:06 [#####################] 100%
    liblastfm-0.3.0-4-x... 223.4K 252.0K/s 00:00:01 [#####################] 100%
    loudmouth-1.4.3-1-x... 80.8K 183.8K/s 00:00:00 [#####################] 100%
    libmtp-0.3.7-1.1-x86_64 439.4K 309.5K/s 00:00:01 [#####################] 100%
    amarok-2.2.0-1-x86_64 10.9M 486.0K/s 00:00:23 [#####################] 100%
    apr-1.3.9-1-x86_64 328.5K 332.4K/s 00:00:01 [#####################] 100%
    apr-util-1.3.9-3-x86_64 237.6K 322.3K/s 00:00:01 [#####################] 100%
    error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from archlinux.unixheads.org : Connection timed out
    error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    bluez-4.54-1-x86_64 671.6K 361.7K/s 00:00:02 [#####################] 100%
    python-2.6.3-1-x86_64 15.2M 442.0K/s 00:00:35 [#####################] 100%
    dbus-python-0.83.0-... 177.4K 225.6K/s 00:00:01 [#####################] 100%
    eclipse-3.5.1-1-x86_64 162.0M 457.1K/s 00:06:03 [#####################] 100%
    vim-7.2.266-1-x86_64 8.6M 437.9K/s 00:00:20 [#####################] 100%
    gvim-7.2.266-2-x86_64 1115.4K 216.9K/s 00:00:05 [#####################] 100%
    inkscape-0.46-13-x86_64 18.4M 464.6K/s 00:00:41 [#####################] 100%
    libical-0.44-1-x86_64 281.3K 283.7K/s 00:00:01 [#####################] 100%
    lm_sensors-3.1.1-2-... 133.2K 228.9K/s 00:00:01 [#####################] 100%
    redland-1.0.9-4-x86_64 307.4K 275.7K/s 00:00:01 [#####################] 100%
    error: error writing to file '/var/cache/pacman/pkg/openoffice-base-3.1.1-2-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'openoffice-base-3.1.1-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'openoffice-base-3.1.1-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/php-5.3.0-5-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'php-5.3.0-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'php-5.3.0-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/pstoedit-3.50-1-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'pstoedit-3.50-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'pstoedit-3.50-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/ruby-1.9.1_p243-2-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'ruby-1.9.1_p243-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'ruby-1.9.1_p243-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/soprano-2.3.1-1-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'soprano-2.3.1-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'soprano-2.3.1-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/texlive-bin-2009.4-1-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'texlive-bin-2009.4-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'texlive-bin-2009.4-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/texlive-core-2009.15574-1-any.pkg.tar.gz': No space left on device
    error: failed retrieving file 'texlive-core-2009.15574-1-any.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'texlive-core-2009.15574-1-any.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    error: error writing to file '/var/cache/pacman/pkg/xchat-2.8.6-5-x86_64.pkg.tar.gz': No space left on device
    error: failed retrieving file 'xchat-2.8.6-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
    error: failed retrieving file 'xchat-2.8.6-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
    warning: failed to retrieve some files from extra
    error: failed to commit transaction (File unavailable (e.g., file not found, no access))
    Errors occurred, no packages were upgraded.
    ~ $
    Also, I haven't restarted my system yet. Should I try and see what happens?
    Thanks!

    This happened to me recently. I could not restart my laptop properly due to lack of space on my root partition.
    The error during boot was along the lines of:-
    Starting D-BUS system messagebus   - Failed
    Failed to start message bus: Failed to close "var/run/dbus.pid": No space left on drive
    Hardware Abstraction Layer - Failed
    everything else during the boot was as normal till I started to type in my username - but couldn't because the keyboard was inactive.
    I used a Wolvix live CD to investigate and found a QT4 file in the packman cache which was 6.9GB in size (compared to the normal 27mb size). Once that was deleted and the drive/partition error checked everything was back to normal. So before you reboot I would definitely recommend clearing any oversize file out of your packman cache, or just clearing the whole cache.
    Last edited by Nixie (2009-10-05 17:16:13)

  • Can't get lvm/luks to boot - cannot find root partition

    Hi,
    I'm trying to get a dm-crypt on top of lvm to boot but without success so far. I followed http://wiki.archlinux.org/index.php/Sys … r_dm-crypt and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM, everything works fine (I can mount the partition) but when I try to boot from it, it cannot find the crypted partition and fails.
    USELVM="yes"
    HOOKS="base udev usb usbinput lvm2 encrypt filesystems"
    root=/dev/mapper/sda2 cryptdevice=/dev/sda2:root2-lvol0 ro
    jan@jan ~/src/xf86-video-ati $ ll /dev/mapper/
    insgesamt 0
    crw-rw---- 1 root root 10, 62 21. Feb 2008 control
    brw------- 1 root disk 254, 0 21. Feb 2008 root
    brw------- 1 root disk 254, 1 21. Feb 2008 root2-lvol0
    brw------- 1 root disk 254, 2 21. Feb 2008 sda2
    /dev/mapper/root is my current encrypted / without lvm
    The boot process successfully identifies the lvm /dev/mapper/root2-lvol0 and continues with hook 'encrypt' but doesn't ask me for a passphrase but goes on to hook 'filesystems' and fails then because it can't mount the correct root-partition obviously.
    There's only /dev/mapper/root2-lvol0 and /dev/mapper/control when I'm in the rescue sh from initrd.
    Anyone got that combination to work?
    - Jan

    Reboot, at the sound of the chime (not before) depress the option key, when the startup manager appears choose OSX.

  • Cannot resize root partition

    i used gparted live in order to maximize the size of root partition but i can't
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 718847 358400 7 HPFS/NTFS/exFAT
    /dev/sda2 * 718848 586656347 292968750 7 HPFS/NTFS/exFAT
    /dev/sda3 612048894 976771071 182361089 5 Extended
    /dev/sda4 586657792 612046847 12694528 83 Linux
    /dev/sda5 967215104 976771071 4777984 82 Linux swap / Solaris
    /dev/sda6 612048896 967213055 177582080 83 Linux
    Number Start End Size Type File system Flags
    1 1049kB 368MB 367MB primary ntfs
    2 368MB 300GB 300GB primary ntfs boot
    4 300GB 313GB 13.0GB primary ext4
    3 313GB 500GB 187GB extended
    6 313GB 495GB 182GB logical ext4
    5 495GB 500GB 4893MB logical linux-swap(v1)
    i minimize the size of sda6(home folder) in order to give more space to my root partition sda4 but i can't .gparted don't give the option to add the unallocated space to sda4.when i tried to adjust the partitions the swap partition was off
    Last edited by kosgeter (2014-04-30 21:52:13)

    That's a no-no, you can't do that
    To increase the size of sda4, there must be continuous free space after it.
    In your case it's like
    sda4
    sda5
    sda6
    You first reduce sda6 and you get free space after it, you need to move sda6(not just resize it). Also you will need to delete sda5(which is your swap) and remake it.
    Example:
    sda4 - 10GB
    sda5 - 4GB
    sda6 - 100GB
    delete sda5 and resize sda6:
    sda4 - 10GB
    4GB free space
    sda6 - 50GB
    50GB free space
    move sda6:
    sda4 - 10GB
    50GB free space
    sda6 - 50 GB
    4GB free space
    resize sda4 and create swap(sda7):
    sda4 - 60GB
    sda6 - 50 GB
    sda7 - 4GB
    Might I suggest that you use console tools instead of gparted(imho gparted is buggy). The tools in the arch install iso should do fine. Also you can't resize mounted partitions,  so you shouldn't try to touch your arch root partition while using it
    Last edited by rand_x0r (2014-05-01 16:06:31)

  • [PPC] new install fails to boot: root partition not found

    Hi,
    new ArchPPC installation on a iMac G3. It does not boot further than initramfs because root partition is not found. I get something like:
    Root device /dev/sda4 doesn't exist
    Attempting to created it
    ERROR: unable to determine major/minor number of root device /dev/sda4
    then I get a dropbox recovery console but keyboard doesn't work.
    I chroot in the installed system to change mkinicpio pata hook to ide, regenerated initramfs but that didn't help.
    Any guidance to diagnose and solve this issue would be greatly appreciated.

    Hi, sorry I just realized you replied to my thread.
    I don't have my mac at the moment, but I must have done something like :
    - boot the live CD
    - get the output of lsmod
    - copy this output to mkinitcpio.conf (the one that's on your HD), remove the autodetect hook
    - chroot into your HD setup
    - regenerate initramfs
    - update yaboot (is this really mandatory?)
    - exit chroot and reboot.

  • Resized root partition didn't really resize

    I had two partitions, 250 + 50 gigs. Then I decided to remove the second one and grow the root partition over the whole disk.
    So I started using install DVD -> disk utility -> removed the second and grew the first. Everything went OK.
    Then I rebooted and it there was no more empty space on the drive. So I strted disk utility (live system) and the numbers were funny, I'm talking about partition (not drive!):
    used space: 200gigs, free space: 50 gigs, total capacity: 300 gigs.
    So the partition got resized but the volume actually didn't?
    Then I ran (live) verify disk and it found "minor error in volume header" (no **** sherlock, you're missing 50 gigs) but couldn't fix it. I restarted from DVD, ran disk utility there and there were no errors found!
    So, how can I grow the root filesystem? How come can "real" system find errors and live doesn't?

    I fixed it!
    I did what the graphical interface should call in the background, but it seems it just didn't.
    Ran the system from DVD, opened terminal and wrote
    diskutil resizeVolume /dev/disk0s2 SIZE
    it's now ok.
    The funny part is that SIZE parameter was exactly the same as
    diskutil resizeVolume /dev/disk0s2 limits
    returned under "Current size".
    It seems there's a bug in diskutil.

  • How to create a third partition without messing up Boot Camp partition?

    I have been running a dual-partition Boot Camp setup (with Mac OS 10.5 and Vista) on my Macbook Pro with no hitches for the past year or so. Recently, I have decided that I want to create a third partition to boot into Windows XP. Of course, Boot Camp doesn't let me do this, so I am trying to do it manually by resizing my Mac OS partition and devoting the remaining space to a new partition. However, when I try to resize my Mac OS partition in Disk Utility, it warns me that "Changing the partition map may make this disk unbootable using Windows."
    So I am wondering: is there any way for me to create a new Windows partition without messing up my preexisting Boot Camp setup?

    I found this blog post shortly after the first BootCamp beta was out. I successfully split mine into three partitions per the instructions. However, since Leopard now lets you live partition your disk, you can probably do the partitioning via Disk Utility instead of using diskutil in Terminal.
    <http://twoyearstwodays.blogspot.com/2006/05/bootcamp-sharing-data-between-osx-a nd.html>

  • Replica info - filtered vs. read/write of the root partition

    Hello all,
    According to Craig's setup guide, the BM server should be in the its own partition of which it is the master replica and it should contain a read/write replica of the root partition.
    We currently have this setup but the one issue we are having is that our content filter is using LDAP to monitor eDir authentication and it seems to be grabbing some workstation authentications as opposed to the user authentications.
    One suggestion to resolve this issue is to use a filtered replica which only sees users and user groups. Is this an option with our BM servers or should I be looking at using a different server for LDAP authentication and put a filtered replica on that one.
    Any thoughts are greatly appreciated.
    Steve D.

    BorderManager needs to read license objects when it launches, filtering
    objects from NDS, access rules from NDS and its own configuration from
    NDS. It also needs to read NMAS-related information from NDS.
    I have found that the most efficient way to a) get BMgr to read its
    information and b) fix filtering issues is to have the BMgr server in
    its own OU. In the past, there was also a Site-Site VPN dependency on
    reading a root replica, but that was fixed sometime ago. (VPN may
    launch faster if the BM server has a root replica, but it doesn't have
    to have it).
    BM wants to read licenses initially from the root of the replica ring,
    so it helps if the BM server is the master of the replica ring holding
    the licenses. This is not a requirement, but it makes BM launch faster
    usually, and it especially important in branch offices with a site-site
    VPN. BM read filters from the NBMRuleContainer, which is almost always
    in the same ou as the server. It is easier to fix filtering issues if
    you can simply delete them all and remigrate them into NDS without
    having to worry about filters from some other BM server being in the
    same container. These are the main reasons I like to have BM in its
    own partition and the master of that replica ring.
    It may help to have a replica of the security container on the server
    as well, for nmas-related VPN logins, but I'm not sure on that. If you
    are running NMAS RADIUS on the same server, you need to have replicas
    of the user partitions also on the server. And with NMAS-related
    logins for VPN, you really want all the clients and all the servers
    with user replicas up to the latest version of NMAS.
    Access rules are normally applied to the server object, but if they are
    applied to ou's above BM, it may help to have replicas holding those
    OU's on the server, but it's not required. (BM will have to read the
    OU's from some other server if it can't get them from itself though).
    Offhand, those are the NDS-related requirements I can think of for BM.
    I would be putting my efforts into fixing the LDAP calls that the
    application is using so that it doesn't look at workstation objects
    rather than try to filter those objects out. However, perhaps you
    could alter your NDS design and put all the workstation objects into
    one or more OU's that the LDAP app doesn't look at?
    Craig Johnson
    Novell Support Connection SysOp
    *** For a current patch list, tips, handy files and books on
    BorderManager, go to http://www.craigjconsulting.com ***

  • Adding unallocated space to root partition

    Root partition is too small, so I wanted to add more space from unallocated space.
    Problem is, that I can't expand root partition and add unallocated space to it. How can I fix it?
    P.S. I used Live CD for that, but this screen is from current system (on Live CD, partitions was not locked). That's so, because it was too hard to make screenshot from Live CD.
    Last edited by daGrevis (2012-07-04 14:32:22)

    bohoomil wrote:As your sda4 seems mostly free, you can a) backup its content, b) delete it entirely, c) expand sda3, d) re-create sda4. You can as well play with moving / resizing partitions, but the previous option seems better to me. Of course, create backups and use a Live CD so that all the partitions are modified when unmounted. The only thing you should remember to do afterwards is correct your fstab with valid UUIDs.
    I'd second this. You could also (after you delete sda4 and increase the size of sda3) make an extended partition out of all the remaining space and then create a logical partition for (what is now) sda4 (it will get a different number when you do this).
    Right now your unallocated space could only be used to add to sda4, because you have used up all your primary partitions. If you make a new extended partition and then put sda4 in it as a logical partition, you will be able to make more logical partitions out of the unallocated space.
    If this is too confusing just go with bohoomil's original suggestion
    Last edited by 2ManyDogs (2012-07-04 15:50:14)

  • [CLOSED + MOVED]Activate lvm2 on ext3 root partition

    Hello guys,
    I want to move to lvm2 on my arch installation, I haven't used any lvm before. So here's what I did so far:
    1. shrink root partition using gparted to 7 gigabytes
    2. created an lvm partition with size 8 gigabytes
    3. migrated all files from the root partition to the lvm partition (in single user mode: # rsync -axSX / /newpartition)
    4. added lvm2 hook before the filesystems hook in /etc/mkinitcpio.conf according to http://wiki.archlinux.org/index.php/Con … #Using_lvm
    5. regenerated the initramfs image using # sudo mkinitcpio -g /boot/kernel26.img
    5a. added a grub entry with root=/dev/vg/root (I have no idea what the difference is between that and /dev/mapper/vg-root)
    5b. edited /etc/fstab to use /dev/vg/root (again, no idea if /dev/mapper/vg-root would have been more appropriate) as root mountpoint "/"
    6. Rebooted
    7. Unfortunately, I cannot copy-paste the output, but upon reboot, the initramfs loads fine, it seems to recognize to lvm2 volume, but then says "trying to open console - not found" or something like that and then kernel panics on me.
    Any ideas?
    thanks!
    CLOSED+MOVED:Moving this question elsewhere, as this topic seems too advanced for this subgroup.
    Last edited by awayand (2010-01-13 12:44:11)

    I used reiserfs for many years, many partitions, many distros and had no problems. Every now and then I'd use ext3 but there were a few issues. I got a new laptop in January and decided to take the plunge: shrunk vista, small ext2 /boot and the rest set up as an encrypted partition with LVM2, all logical volumes set up as ext4 (except swap!). I've been very impressed with ext4 stability.
    Oh, and step (5) edit fstab to reflect the new file systems, make sure /etc/mtab doesn't exist.

  • Can't add a new partition without erasing it all.

    Hi! I have a problem in Disk Utility in which I cannot add a partition because the plus button is greyed out. I can select to make two partition in the drop down but that would probably erase everything.  All I want to do is add one partition to the existing partition without erasing anything so I can dual boot Windows 8.  I can't use boot camp because I can only install Windows 7 since my computer is from 2010.  Thanks in advance!

    ^^^ with pic =).
    And then just link your object/text with the standard hyperlink menu!

Maybe you are looking for