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.

Similar Messages

Smallest possible root partition?

I'm trying to remotely (SSH) convert a machine from Ubuntu Server to Arch Linux.
The owner of the machine does not have any external storage available (e.g., flash drives) - he switched over to using Apple products almost exclusively and has been using cloud services and such to store everything.
The machine's partition table currently looks like:
# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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: 0x000af6e3
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 625141759 312320001 5 Extended
/dev/sda3 625141760 625142447 344 83 Linux
/dev/sda5 501760 625141759 312320000 8e Linux LVM
Disk /dev/mapper/Pauls--Ubuntu--Server-root: 317.8 GB, 317785636864 bytes
255 heads, 63 sectors/track, 38635 cylinders, total 620675072 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/mapper/Pauls--Ubuntu--Server-root doesn't contain a valid partition table
Disk /dev/mapper/Pauls--Ubuntu--Server-swap_1: 2009 MB, 2009071616 bytes
255 heads, 63 sectors/track, 244 cylinders, total 3923968 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/mapper/Pauls--Ubuntu--Server-swap_1 doesn't contain a valid partition table
# parted /dev/sda print
sda sda1 sda2 sda3 sda5
james@Pauls-Ubuntu-Server:~$ sudo parted /dev/sda print
Model: ATA WDC WD3200AAJS-0 (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 256MB 255MB primary ext2 boot
2 257MB 320GB 320GB extended
5 257MB 320GB 320GB logical lvm
3 320GB 320GB 352kB primary ext4
Would it be possible, via a creative combination of fstab and symlinks, to have a root partition of ~200 MB? What issues might arise?

Depends on what you have on it. If /var, /home, /usr, /boot, /etc, and /opt are on on their own partitions, you could probably get away with a root that was just a few MB. Each of those that is on the root partition will add to the requirements, generally /etc doesn't take too much, /boot can, depending on how many kernels you have, and /opt depends completely on whether you use any programs that get installed there; I have none. /srv is something else to consider if you run apache or something.
Of course, putting /usr and /var on their own partitions creates some other challenges, and those will be two of your larger dirs.
Last edited by Scimmia (2013-12-05 18:27:51)

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.

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.

Fresh btrfs root partition cannot boot/unknown filesystem [solved]

Just reformatted my SSD with 3 partitions.
1) EFI
2) /boot (ext4)
3) / (btrfs)
I copied over my systefrom tars, adjusted the new fstab to use btrfs, I rebuilt my kernel images, and rebuilt grub.cfg in the chroot. When I reboot, I get:
Welcome to grub!
error: unknown filesystem
Entering rescue mode...
grub rescue>
Per the wiki, there should be no special setup steps to boot to a btrfs root with grub. When did I f-up?
/etc/fstab
LABEL=arch64 / btrfs defaults,discard,noatime,ssd,compress=lzo 0 0
LABEL=boot /boot ext4 defaults,discard,noatime 0 2
Excuse the short post, typing in a phone.
Last edited by graysky (2013-07-29 01:24:47)

Yes, it is dropped to a GRUB rescue shell. I can boot if I manually type the following but WTF?! Why isn't grub doing this by itself?
grub rescue> set prefix=(hd0,2)/grub
grub rescue> insmod (hd0,2)/grub/x86_64-efi/linux.mod
grub rescue> set root=(hd0,2)
grub rescue> linux /vmlinuz-linux-ck root=/dev/sda3
grub rescue> initrd /initramfs-linux-ck.img
grub rescue> boot
Link to my autogenerated /boot/grub/grub.cfg
Last edited by graysky (2013-07-29 00:28:58)

Extending root partition

Hi
We have installed an Oracle VM server. We have 3 VM 's in it. In one of the machine we have installed two database.
The root partition is 5gb. which is now 99% full.
My question is, how can I extend the root partition.
this is result of df-h command:
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 3.0G 2.9G 1.3M 100% /
/dev/xvda1 92M 37M 50M 43% /boot
tmpfs 5.4G 7.7M 5.4G 1% /dev/shm
/dev/xvdb1 237G 201G 24G 90% /u01
/dev/xvdd 296G 229G 53G 82% /u03
Appreciate your help
Thanks
Edited by: dba88 on 5 Jun, 2013 6:50 PM

Hi,
I have a littel experience with XEN, but when i think like a Linux administrator it is not possible to extend the disk xvda directly because the full size of disk xvda is used and you are not using the LVM concept.
i advice you to create a new partion in the disk xvdb (xvdb2) and move your home directory to this partition (you can add the mount in the fstab file).
I hope this can help you
Best Regards

Attempting to resize my root partition on LVM

My root partition is currently full, so I want to resize it. I'm using LVM and the filesystem is ext4, so I assumed it should be easy enough. My plan was to reduce my /home to make space. However, when following the instructions in the wiki get the following error:
# resize2fs /dev/vg/syshome 450G
resize2fs 1.42.4 (12-June-2012)
Filesystem at /dev/vg/syshome is mounted on /home; on-line resizing required
resize2fs: On-line shrinking not supported
According to https://ext4.wiki.kernel.org/index.php/ … esystem.3F however, online resizing should be possible.
What am I missing?
Last edited by phunni (2012-08-03 20:37:26)

First, install and use ncdu to check what's eating up all the space.
$ ncdu / --exclude /home --exclude /media
Maybe it's easily fixed, like a log file or something. Speaking of which, learn2logrotate. Here's my /etc/logrotate.conf.
Then if you still want to grow the root partition, try this: https://wiki.archlinux.org/index.php/LV … cal_volume
Next time please specify in the title that it's about LVM.

LVM + LUKS + TRIM @ root partition

Hi.
I'm installing a fresh arch linux PC right now with LVM + LUKS and TRIM because i have one SSD , and UEFI mobo.
SSD has a physical partition for the /boot and the rest one used with LVM where a virtual group created called "lvmRootPool" which contains two logical volumes ("lvmRootPool-root" and "lvmRootPool-swap")
The lvmRootPool-swap was kept for swap and
the lvmRootPool-root for /.
Here comes the question. I want to enable TRIM for that disk (i know the security risk) and following this guide i have to add a specific line with discard keyword in /mnt/etc/crypttab (i'm before chroot). But when i open the /mnt/etc/crypttab it has a note saying
Do not list your root partition here, it must be set up beforehand by the initramfs (/etc/mkinitcpio.conf)
So what i supposed to do ? Should i add that line at crypttab file or not ?
lvmRootPool-root /dev/sda2 none luks,discard
Also , is it possible to use TRIM for swap ? I think that isn't but maybe something have been changed that i don't know.
Thank you.
Last edited by netpumber (2015-05-24 18:06:40)

maybe your missing pieces are: https://wiki.archlinux.org/index.php/So … IM_for_LVM and https://wiki.archlinux.org/index.php/Dm … encryption
In a nutshell:
For encryption you need to change the kernel parameter in your bootloader, add encryption and resume hook to mkinitcpio.conf. If the hooks are at the right spots, it just works for swap as well.
For LVM passthru there is a setting described in the link above
You still need the discard flags in your fstab.

[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.

Resize root partition within a PVM

Hello - I have found any information about this searching the forum, but I am trying to re-size the root partition that comes with one of the PVM templates (some of them are really small). In order to do this, you need to boot into an ISO.
With a PVM, you cannot boot directly to an ISO...you have to network boot from an NFS share using the contents of the ISO. Same way you would deploy a PVM from ISO.
My problem comes in when I need to get into "linux rescue" mode at the grub prompt when you first boot to the ISO normally. This prompt does not seem to come up when network booting to the ISO. Does anyone know the proper steps to do this?

I think I figured this out. I had to...
- Delete the swap partition (because it's the last one by default with the template, xvdb3).
- Delete the root partition (xvdb2).
- Re-create root partition with same starting block and partition number (but reserve space for swap, I left 2gb).
- Re-create swap partition with remaining space, and assign swap type of 82.
- Reboot, and run resize2fs on root partitions (I'm currently at this stage but it looks like this will work fine).
- Shutdown the VM, detaching the disk that was resized, and attached it back to original VM. Then start the VM.
- mkswap /dev/xvda3 (on swap partition)
- swapon /dev/xvda3
- free -m (to view new swap space)
Edited by: ekrengel on Mar 13, 2012 10:39 AM
Update steps...

Corrupted Win7 Partition

Can someone help me recover my corrupted Win7 partition please?
Last login: Mon Jan 12 18:37:17 on console
diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            502.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         497.3 GB   disk0s4
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 GB     disk1
   1:                 DOS_FAT_32 UNTITLED                2.0 GB     disk1s1
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            GSP1RMCPRXFRER_EN_DVD *3.3 GB     disk2
diskutil cs list
No CoreStorage logical volume groups found
gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 1953525167
       start        size index contents
           0           1         MBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640   980461752      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
   980871392     1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
   982140928   971382784      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1953523712        1423
1953525135          32         Sec GPT table
1953525167           1         Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0    geometry: 121601/255/63 [1953525168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 980461752] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 980871392 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 982140928 - 971382784] HPFS/QNX/AUX

Ok after an entire day it finally finished scanning:
No disk found.
TestDisk will try to restart itself using the sudo command to get
root (superuser) privileges.
sudo may ask your user password, it doesn't ask for the root password.
Usually there is no echo or '*' displayed when you type your password.
Password:
TestDisk 7.0-WIP, Data Recovery Utility, December 2014
Christophe GRENIER <[email protected]>
http://www.cgsecurity.or
TestDisk 7.0-WIP, Data Recovery Utility, December 2014
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
Disk /dev/rdisk0 - 1000 GB / 931 GiB - 1953525168 sectors (RO)
The harddisk (1000 GB / 931 GiB) seems too small! (< 8244231 TB / 7498084 TiB)
Check the harddisk size: HD jumpers settings, BIOS detection...
The following partitions can't be recovered:
     Partition               Start        End    Size in sectors
> MS Data                589197655 2408374607 1819176953
   MS Data                608449240 2427626192 1819176953
   Mac HFS                980871388 1961333139 980461752
   MS Data               1026846776 2846023728 1819176953
   Mac HFS               1278484238 1994314511 715830274
   Mac HFS               1364515067 4661906751 3297391685
   Mac HFS               1364900009 4762958318 3398058310
   Mac HFS               1365656154 2733684382 1368028229
   MS Data               1533864209 16102014586812747 16102013052948538 [tem: %s
   Mac HFS               1653462088 2056279113 402817026
[ Continue ]
NTFS, blocksize=4096, 931 GB / 867 GiB
What is the next step now Loner T?

Copying root partition, what about dev

When I get a stable system I copy my good root partition to another disk, of course editing /boot/grub/menu.lst and /etc/fstab to use that partition so that I can boot into either my "stable" Arch or my "work in progress" Arch. I copy the root partition using rsync like this. Everything always works fine and I don't have any problem, but I do have a question: is it still necessary to
# Include
+ /dev/console
+ /dev/initctl
+ /dev/null
+ /dev/zero
AFAIK even these devices are now created dynamically by udev. Are they? Is it possible now to boot a system with an empty /dev directory?

falconindy wrote:Unnecessary. devtmpfs is mounted very early on top of /dev and managed by the kernel. "Back in the day" these nodes were needed for proper operation in early userspace before /dev was mounted.
I could see on my running system that the device nodes all have the same creation date and my question really was whether any devices had to exist in the filesystem before the devtmpfs was laid on top. And the guy from New Jersey with the big smile face says "unnecessary." Thanks.

[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.

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)

Corrupted root partition - a possible rescue?

Similar Messages

Maybe you are looking for