[SOLVED] ReiserFS on /var partition

Currently I have 4 partitions installed on my arch system
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 14.3G 0 part /
├─sda2 8:2 0 9.6G 0 part /var
├─sda3 8:3 0 972.7M 0 part [SWAP]
└─sda4 8:4 0 208.1G 0 part /home
My root (/), /var, and /home partitions have an ext4 filesystem.
I was wondering how I would format my /var partition and install the reiserFS
Last edited by diligentchaos (2012-12-10 08:03:02)

I had to do this in the past because I didn't want reiserfs anymore.  So I can confirm that anonymous_user's suggestion works just fine.  In fact, with Linux, since everything is a file, you can actually create an entire working copy of your system by simply copying the contents to another storage medium.  Just make sure you use something that can correctly preserve the permissions and such.

Similar Messages

  • [SOLVED] Converting the var partition filesystem from ReiserFS to ext4

    Hi,
    I have a system that still uses ReiserFS for its /var partition. It gives me some performence problems which make me want to convert it to the newer ext4. Can it be done without reinstalling the entire system? and if so, how?
    Last edited by Greenstuff (2013-10-05 14:01:41)

    Boot to a live environment.
    Mount the var partition and copy somewhere or tar it up.
    Umount the var partition.
    Format the old var partition to ext4.
    Mount the newly formatted var partition.
    Copy back or untar the archive.
    Reboot.
    EDIT: Make sure you adjust the fstab in the root partition before you reboot!
    Last edited by graysky (2013-10-05 15:14:31)

  • [Solved]Replaced my /var partition (with dd) and am having boot issues

    I recently got a new hard drive and have split /var and root across the two drives. However now I am having issues booting the computer. Each boot it mounts the /var and /home partition (both of which are on the new drive) and hangs for a large period of time before booting. (it does eventually boot fine)
    The reliant section of journalctl is:
    an 05 04:54:33 ArchPC systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Jan 05 04:54:34 ArchPC systemd[1]: Started Load Random Seed.
    Jan 05 04:54:34 ArchPC systemd[1]: Started Recreate Volatile Files and Directories.
    Jan 05 04:55:58 ArchPC systemd[1]: Job dev-disk-by\x2duuid-e6fa1ae1\x2d5579\x2d439d\x2d94cc\x2d11b2c0e67070.device/start timed out.
    Jan 05 04:55:58 ArchPC systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-e6fa1ae1\x2d5579\x2d439d\x2d94cc\x2d11b2c0e67070.device.
    Jan 05 04:55:58 ArchPC systemd[1]: Dependency failed for /dev/disk/by-uuid/e6fa1ae1-5579-439d-94cc-11b2c0e67070.
    Jan 05 04:55:58 ArchPC systemd[1]: Job dev-disk-by\x2duuid-e6fa1ae1\x2d5579\x2d439d\x2d94cc\x2d11b2c0e67070.swap/start failed with result 'dependency'.
    Jan 05 04:55:58 ArchPC systemd[1]: Job dev-disk-by\x2duuid-e6fa1ae1\x2d5579\x2d439d\x2d94cc\x2d11b2c0e67070.device/start failed with result 'timeout'.
    Jan 05 04:55:58 ArchPC systemd[1]: Starting Swap.
    Jan 05 04:55:58 ArchPC systemd[1]: Reached target Swap.
    However I am not sure where this could be, unless it is attempting to mount my windows partition?
    As a side note, during this I also moved my windows install to the same drive as my root and it will no longer boot from ether its new or original drive.
    Thanks.
    Last edited by jarrah-95 (2013-01-04 09:24:59)

    Jarrah-95,
    Thanks for your 'solution' post.  I had a problem on boot with the boot process 'stalling' with a "recreate volatile files and directory" message that would after about a 30 second delay eventually finish the boot process.  Based on your post I ran 'blkid' and discovered my 'swap' partition in my /etc/fstab file had the wrong UUID for the 'swap' entry.
    After entering the 'correct' 'swap 'UUID',  the boot cycle is restored and fast as ever.  Back to the basics wins again.
    Next task is to find out how I created the mistake.
    best regards,
    marvinudy

  • [solved] cannot update because of full /var partition

    hello,
    i have problems updating my packages, because my /var partition is full.
    Total Download Size: 253.57 MiB
    Total Installed Size: 1009.80 MiB
    Net Upgrade Size: -1949.50 MiB
    :: Proceed with installation? [Y/n] y
    error: Partition /var too full: 70069 blocks needed, 52290 blocks free
    error: failed to commit transaction (not enough free disk space)
    Errors occurred, no packages were upgraded.
    to solve this i tried to delete some *.tar.xz files in /var/cache/pacman/pkg, thinking they wouldnt be needed anymore as they are installed already. i could update then, but after a reboot, i had to fix it with
    pacman-db-upgrade
    . should i try to resize my partitions, or is there any easy solution?
    thanks lizzy
    Last edited by caravanlizzy (2015-01-07 00:08:24)

    What the heck were you doing in that pacman transation?  1 GB was added, and nearly 2 GB removed?
    I can't help but suspect that was part of it.  But in either case, you should check what is filling up /var/ as the package cache should not be a major issue.  Are logs filling up?  In other words, are you ignoring your computer screaming at you about some other problem?

  • Errors.log took over /var partition estate

    I have 2GB /var partition with reiserfs filesystem, but it get full after 24 hours and the culprit is errors.log
    errors.log
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    May 25 08:32:39 Kandalf-ArchLinux NOHZ: local_softirq_pending 08
    so on and on... I had to dump this log every now and then to be able to boot into desktop enviroment.
    and another issues i have, my processor is running at wrong cpu freq.
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 15
    model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
    stepping : 6
    cpu MHz : 900.000
    cache size : 4096 KB
    physical id : 0
    siblings : 2
    core id : 0
    cpu cores : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 10
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
    bogomips : 4900.57
    clflush size : 64
    processor : 1
    vendor_id : GenuineIntel
    cpu family : 6
    model : 15
    model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
    stepping : 6
    cpu MHz : 900.000
    cache size : 4096 KB
    physical id : 0
    siblings : 2
    core id : 1
    cpu cores : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 10
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
    bogomips : 4897.20
    clflush size : 64
    How do i set it at max 2.4Ghz?
    Last edited by firestrife (2007-05-25 16:06:06)

    I had the same thing going on (full /var after a day).
    Google told me to append nohz=off to my kernel line in /boot/grub/menu.lst
    Since then there are no more errors in the log-files. Could be a bug in the kernel and/or ndiswrapper (or somehow related)
    Last edited by n8schicht (2007-06-07 10:26:22)

  • /var partition seems to be corrupted

    hi everyone,
    not wanting to necrobump an ancient thread on this i thought i'd create a new post.
    when i booted up today, i was greeted with quite a few failed entries in my bootsplash. gdm wouldn't run, but a login on tty2 worked. seems that my /var partition (seperate partition on sdb, / is on sda) is throwing i/o errors and is mounted read-only.
    is there a way i can move all the files from sdb to sda (or another partition - hdd space shouldn't be a problem, i have plenty), and then change my fstab to reflect the new mountpoint? do i even need to copy the contents of /var or can i somehow just recreate the directory structure and point fstab to a different location?
    in case its relevant, i also use deja dup to backup /var/pacman/cache to a seperate location (sdd i think). i may be able to recreate pacman's cache once i manage to mount /var somewhere that works.
    im on a different system now and i have to go to work in a bit, so i can only post further details later today or tomorrow, but i'd be grateful for any tips or hints as to how to proceed here.
    thanks a bunch!
    regards,
    M.

    so... turns out i wasn't smart, fast or lucky enough. im able to boot and everything seems to work somewhat, but being that pacman's pretty useless without /var it seems i have to reinstall.
    i only kept regular backups of /var/cache/pacman/ and the partition (i was trying out bcache with it, worked pretty well too) i saved it to seems to be acting up also.
    is there anything particular i should be aware of when reinstalling? i'll make sure to back up / first, but i'm guessing i wont be needing it as i assume i'll be reinstalling everything from scratch.
    does anyone else have experience reinstalling arch?
    regards,
    M.
    Last edited by miles969 (2014-07-29 18:08:42)

  • How to create a separate /var partition on solaris non-global zone

    Hi
    I found no simple way to create a separate /var partition in solaris non-global zone.
    I am using solaris 10 u9 and my root pool is zfs. My zone's zonepath is also separate zfs fs.
    But, I do not know how to make the /var as a mountpoint of another zfs dataset since /var is not empty.
    I also do not know if there is a way to install a zone with /var as a separate (outside '/') partition.
    That will be really useful.
    Any suggestion?
    Thanks
    Edited by: vadud3 on Sep 20, 2010 12:16 PM

    I meant a separate zfs fs with mountpoint '/var' in a non-global zone.
    I am insisting, because I do not want /var to fill up the '/' on non-global zone.
    With default non-global zone installation, you cannot avoid that.
    My zonepath itself is a zfs fs. I also have a zfs dataset provisioned to the non-global zone.
    I cannot create a zfs fs out of that dataset and mount it as '/var' becasue by then non-global zone
    already installed content on '/var'
    I want the '/var' as a separate dir or mountpoint, the same reason global zone gives you that option during install.
    Thanks

  • Var partition showing incorrect size

    So I installed a new system on a new rig last night. Today, I noticed that the /var partition is showing a much smaller size, than what it actually is.
    "df -h /var" shows:
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda3 3,0G 266M 2,6G 10% /var
    But "fdisk -l /dev/sda3" as root gives me:
    Disk /dev/sda3: 21.5 GB, 21474836480 bytes
    255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    The 21 gb shown by fdisk is the correct size of the partition, so why on earth will arch only see 3 of those when mounting it as /var?
    The relevant fstab entry looks proper to me:
    UUID=2a2bb9dd-054c-4a04-810b-9bae86c8ca8f /var ext4 defaults 0 1
    And to double check that uuid is correct and pointing to /dev/sda3, I run "ls -l /dev/disk/by-uuid" and get:
    lrwxrwxrwx 1 root root 10 May 1 11:41 2a2bb9dd-054c-4a04-810b-9bae86c8ca8f -> ../../sda3
    Any clue to what is happening here? Help would be much appreciated.

    Maybe the files system was not created properly. Try backup your files and reformat or resize with resize2fs.

  • /var partition moving

    I have a working dual-boot dual HD Arch/Win PC with a separate /var partition.
    Due to disk failure (the one hosting /var among others) I've installed a new HD, created new partitions, and used a live CD (Knopix) to run (as root) "rsync -av 'old var' 'new var'.
    rsync reported several failures (although the majority of files have been transferred.
    Can I expect a safe Linux boot with the new /var mounted?
    If not, whar are my options?
    P.S. my / and /home partitions remained safe on the other, non failing HD.
    Thanks

    mibadt wrote:Can I expect a safe Linux boot with the new /var mounted?
    Try it and see.
    Not an Installation issue, moving to NC...

  • [SOLVED] Cloning boot and var partitions to a new drive for booting

    Ok first of all here's my setup:
    fakeraid (dmraid) / and home on an OCZ Revodrive
    boot with GRUB on a flash drive (since fakeraid doesn't support grub)
    var and downloads/media folder on a 500GB WD Caviar drive
    When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting.  Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
    #dd if=/dev/sde of=~/MBR.img bs=512 count=1
    #dd if=/dev/sde1 of=~/boot.img
    #dd if=/dev/sdc1 of=~/var.img
    I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
    #dd if=~/MBR.img of=/dev/sdc bs=512 count=1
    #dd of=~/boot.img of=/dev/sdc1
    #dd of=~/var.img of=/dev/sdc2
    I also created labels for the filesystems and put those in fstab.
    I'm able to mount both partitions, however I can't boot from the drive.  I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS. 
    I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully.  It is also able to mount the var and boot partitions in fstab. 
    Basically the only problem is that the MBR is somehow wrong.  I then tried booting back into an Arch live USB and installing GRUB from the prompt:
    grub
    grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
    So essentially what I'm asking is how GRUB handles the MBR.  Is it specific to the partition table of the drive in which it resides when it's originally installed?  For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
    I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start. 
    Thanks in advance.
    Last edited by DarksideEE7 (2011-02-13 23:25:31)

    Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB.  It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong.  GRUB is able to find the stage files using:
    #grub
    grub>find /grub/stage1
    grub> find /grub/stage1
    (hd0,0)
    (hd5,0)
    grub>
    (hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
    Here is the output of fdisk -l:
    WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
    256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sde1 1 3907029167 1953514583+ ee GPT
    Disk /dev/sdb: 60.0 GB, 60022480896 bytes
    255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xedb72db9
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
    /dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
    Disk /dev/sdd: 40.0 GB, 40018599936 bytes
    255 heads, 63 sectors/track, 4865 cylinders, total 78161328 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdd doesn't contain a valid partition table
    Disk /dev/sdc: 40.0 GB, 40018599936 bytes
    32 heads, 32 sectors/track, 76329 cylinders, total 78161328 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/sdc1 32 21484543 10742256 83 Linux
    /dev/sdc2 21484544 156317695 67416576 83 Linux
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 83 Linux
    /dev/sda2 206848 42149887 20971520 83 Linux
    /dev/sda3 42149888 976773167 467311640 83 Linux
    Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
    32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/dm-0p1 32 21484543 10742256 83 Linux
    Partition 1 does not start on physical sector boundary.
    /dev/dm-0p2 21484544 156317695 67416576 83 Linux
    Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
    255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Alignment offset: 49152 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-1 doesn't contain a valid partition table
    Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
    255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-2 doesn't contain a valid partition table
    Disk /dev/sdf: 8086 MB, 8086618112 bytes
    249 heads, 62 sectors/track, 1023 cylinders, total 15794176 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sdf1 * 62 200693 100316 83 Linux
    /dev/sdf2 200694 15794175 7796741 83 Linux
    I'm using dmraid, so just to be clear I've configured the raid using:
    #modprobe dm_mod
    #dmraid -ay
    Then I saw the array stored in /dev/mapper/silXXXXX.  I then created partitions for /boot, /, and home.  At that time I was hoping to get GRUB working with the AUR package grub2-dmraid.  I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
    Here is the output of df -h:
    Filesystem Size Used Avail Use% Mounted on
    udev 10M 268K 9.8M 3% /dev
    /dev/mapper/sil_bgbgdjaddicbp1
    11G 5.3G 4.3G 56% /
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/mapper/sil_bgbgdjaddicbp2
    64G 38G 23G 63% /home
    /dev/sda1 95M 16M 75M 18% /boot
    /dev/sda2 19G 142M 19G 1% /var
    /dev/sda3 439G 148G 269G 36% /home/l33/Torrents
    none 1000M 132K 1000M 1% /tmp
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
    and cat /etc/mtab
    proc /proc proc rw,nosuid,nodev,noexec,relatime
    sys /sys sysfs rw,nosuid,nodev,noexec,relatime
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
    /dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
    devpts /dev/pts devpts rw 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev 0 0
    /dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
    /dev/sda1 /boot ext2 rw 0 0
    /dev/sda2 /var reiserfs rw,noatime 0 0
    /dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
    none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
    rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
    nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
    /dev/sde1 /mnt/Green ext4 rw 0 0
    Also I don't have a /proc/mdstat.  That's only for mdadm RAID setups, right?  It's been quite some time since I've used mdadm so I can't remember.
    EDIT:
    So I booted into a live Arch USB and entered the grub shell.  I ran:
    #grub
    grub> root (hd3,0)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd3)
    Checking if "/boot/grub/stage1" exists.....no
    Checking if "/grub/stage1 exists.......yes
    Checking if "/grub/stage2 exists.......yes
    Checking if "/grub/e2fs_stage1_5 exists....yes
    Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
    succeeded
    Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
    Done.
    Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved.  More to come.
    Last edited by DarksideEE7 (2011-02-13 23:18:44)

  • [SOLVED] Moving boot, home and var partition post-install

    I've installed my whole Arch on a single 10GB partition because of low disk space. But now that I've gained a lot of disk space, I want to move /boot, /home and /var to separate partitions.
    I'm going to use live CD, so everything will be unmounted.
    home and var:
      I assume it's just a matter of moving files and changing fstab.
    boot:
      I assume, I'll have to move all files to new partition and re-install grub/burg.
    Is there anything more to it?
    Last edited by Camus (2011-12-01 11:37:32)

    You need to edit your fstab file, copy files to the new partitions (check for permissions!), and restore grub(2), see wiki.
    If you do not have custimized Arch, you could do a reinstall, but I'm not responsible for that tip. So be sure to have a backup or something like that.

  • [SOLVED] error pacman: /var/cache/pacman/pkg exists in filesystem

    Hi guys, yesterday night I tried to update my system and I got the following error which seems weird:
    resolving dependencies...
    looking for conflicting packages...
    Package (1) Old Version New Version Net Change
    core/pacman 4.2.0-5 4.2.0-6 0.00 MiB
    Total Installed Size: 4.22 MiB
    Net Upgrade Size: 0.00 MiB
    :: Proceed with installation? [Y/n] y
    (1/1) checking keys in keyring [##########################################################] 100%
    (1/1) checking package integrity [##########################################################] 100%
    (1/1) loading package files [##########################################################] 100%
    (1/1) checking for file conflicts [##########################################################] 100%
    error: failed to commit transaction (conflicting files)
    pacman: /var/cache/pacman/pkg exists in filesystem
    Errors occurred, no packages were upgraded.
    It seems weird to me because it conflicts to the whole folder and not to any specific package. Any clue, what is going on and how to solve it?
    Last edited by theodore (2015-01-26 19:51:37)

    clfarron4 wrote:
    theodore wrote:
    Allan wrote:Is your /var/cache/pacman/pkg a directory or a symlink?
    yes I have it in a different partition and then I have symilinked it
    I'd have thought it would have been better to set a different directory for the pacman cache, mounting the partition to that through /etc/fstab and using the CacheDir variable in /etc/pacman.conf, but I'll leave that to your judgement.
    If you don't want to do that, then I'll leave someone else to put up a solution (my brain's screaming bind mounts for some unknown reason).
    So, you are saying that I should enable the CacheDir in /etc/pacman.conf and point it to the partition where I have now the pacman cache.

  • [solved] automatically mount crypted partitions

    Hey!
    I have an encrypted partition on my extern esata drive. I'd like it is automatically mount it on plugging in the drive.
    For that I have found an tutorial (unfortunately in German) about how to do it with udev:
    http://michael.stapelberg.de/Artikel/au … setup_udev
    But I'm using systemd, so this do not work this way.
    Can anybody explain me, how it will be done with systemd? I have to write a systemd unit file, haven't I?
    Thank you very much for some advices?
    Last edited by smohr (2012-07-27 12:44:23)

    I have solved it. Thank you Mr.Elendig!
    For running more than one command in your udev rules, it is necessary to execute them in a bash script and connect them with &&.

  • [SOLVED] Mounting a logical partition

    Scenario:
    /dev/sda1 primary NTFS windows boot
    /dev/sda2 primary NTFS windows home
    /dev/sda3 primary ext4 arch /boot
    /dev/sda5 primary ext4 arch /
    /dev/sda6 logical ext4 arch /home
    /dev/sda7 arch swap
    Do I perform mount /dev/sda6 /mnt/home as if it were a "normal" partition?
    EDIT: I would mount each logical partition as normal.
    Last edited by tancrackers (2012-08-29 03:34:46)

    shortcut144 wrote:
    perbh wrote:
    Assume your fat-partition is /dev/sda5 (just as an example)
    sudo mount -t vfat /dev/sda5 /some/mount/point
    Otherwise - as 's3kt0r' says - you can easily mount a ntfs-partition for read/write as well (using ntfs-3g)
    Awesome, thank you.  Marked as solved.
    Should I put this command in my fstab, or just make a startup command for this?
    You could do either ....
    If it will _always_ be there and you always want it mounted - put it in /etc/fstab, -or- you could put it in /etc/rc.local (without using 'sudo' of course).
    I'm a great believer in using rc.local because you _know_ that everything which might be needed (modules eg.) will be available by then.
    If you use /etc/fstab, your entry would be:
    /dev/sda5 /mount/point vfat defaults 0 0

  • Systemd error when using separate /var partition

    I recently moved /var to a new partition and have noticed this error in journalctl log
    Dec 05 07:48:00 archlinux systemd[1]: Started Console System Shutdown Logging.
    Dec 05 07:48:00 archlinux systemd[1]: var.mount mount process exited, code=exited status=32
    Dec 05 07:48:00 archlinux systemd[1]: Failed unmounting /var.
    I added an entry in fstab for /var
    /dev/sda4 /var ext4 defaults,noatime,discard 0 1
    Drive is ssd and I simply added the options I have for / is this correct?

    HungGarTiger wrote:The error message is actually showing a successful unmount by journald not being able to write to the log file....
    What? I don't understand.
    The log says "umounting /var" then "Failed to umount /var"
    What I think falconindy is saying is that, yes systemd will still try and fail to umount /var. However, if you add "shutdown" to the end of your HOOKS="" array in /etc/minitcpio.conf and rebuild the initramfs. That shutdown hook will umount /var after all the systemd and journald stuff is no longer running.
    Personaly, I'm just going have journald write the journal to /run/log/journal. I run AIDE before and after every upgrade, so I will know if anything funky happens to my system. A log would be usefull, but as long as I know what files have been changed I can recover them from my backups.
    Last edited by hunterthomson (2012-12-11 06:22:36)

Maybe you are looking for