Filesystem corrupted [SOLVED]

Hi friends, I can`t boot, I see this
/dev/sda1 contains a file system with error,check forced.
Directory inode 822530, block 0, offset 0: directory corrupted.
I can get to the filesystem. I don`t know which directory is inode 822530 to delete it.
What should I do.
filip
Last edited by mezcal (2007-05-29 20:19:41)

enter maintenance mode and run 'fsck /dev/sda1'
Last edited by tardo (2007-05-29 06:42:46)

Similar Messages

Frequent 'Filesystem Corrupt', Invalid File count

I have been getting this message every a couple of days in my MBP or iMac running 10.6.2. It happens/visible only when I runs Disk Utility and Verify Disk. Of course, this brings unsettling point to me when it comes now and then. Not to mention I have to boot from DVD to run disk utility to fix this
Error Message: Invalid file count (It should be xxxxx instead of xxx+1) AND
Error Message: Invalid volume directory count (It should be xxxxx instead of xxxx-1)
Any idea what causes this and what's the impact i.e. do I lose any files?
Thanks!!

Leonard Ong wrote:
Hi Tim,
By default, it is HFS+ Journaled (non-case sensitive). So I have also the same understanding that journalled filesystem should be robust as you wrote it. But the fact that this comes now and then, It created some doubts.
Is this a harmless error message or should I be worried about it. That basically my questions. I do repair when I see this.
It can't be because of disk is failing for a number of reason:
1) I have the same behavior both in my iMac and MBP
2) Both HDD has been replaced with new one recently
3) Both HDD has passed through surface scan from TechTool Deluxe 5.0.6, so no bad blocks
Still a puzzle...
Are you sure that the errors are showing up on both computers when performing either a "Verify Disk" or "Repair Disk" and NOT just a "Verify Disk Permissions" or "Repair Disk Permissions"? Permissions errors are mostly harmless. Filesystem errors (the sort you see when you ask for "Verify Disk" or "Repair Disk" in Disk Utility are not harmless and you should be worried about those.
If so, then either both drives are failing or your drives are being exposed to a strong enough magnetic field to damage their data (and that would have be pretty strong -- a common refrigerator magnet wouldn't do the trick.) In all of my years of working with journaled filesystems (or operating systems with "filesystem logging" which is the same thing) I have NEVER seen a journaled volume have filesystem errors unless it was physically failing.
Journaling will prevent filesystem errors if it's enabled for pretty much every cause except for a physically defective or damaged disk. Here's the short version of how journaling works...
Journaling (aka "filesystem logging") is intended to prevent filesystem corruption... and it's pretty rock-solid.
1) A "journal" (or "log") area is added.
2) A hard rule is established that, under no circumstances may the OS be performing writes to both the journal and the regular filesystem at the same time. One must be flushed before it can work on the other and vice versa.
3) When a write operation is about to happen, the OS writes information to the journal indicating which blocks on the filesystem are about to be changed and what it's about to change. This information is flushed to disk.
4) The OS can then perform the write on the actual filesystem areas it intended to change. These must then be flushed to disk.
5) The journal can now be cleared.
That's pretty much it (simplified). But think about what this does. Normally if something interrupts a write operation (something crashes, a kernel panic, a power loss, etc.) there is something that will still have integrity because the OS will not write to both the journal and the regular filesystem at the same time.
If a failure occurs while writing to the filesystem it's no big deal. When the system boots back up, it notices the journal wasn't cleared so it "replays" the journal. This re-writes any blocks that might only have been partially written thus clearing any chance of corruption on the volume.
If a failure occurs while writing to the journal it's still no big deal. When the system boots back up it notices a corrupt journal, but that means the regular filesystem itself wasn't being touched so the filesystem is guaranteed to not have errors on it (although it does mean the last file you were about to save probably didn't get saved -- and that file wouldn't have written successfully even if journaling were off. At least this way there is no filesystem corruption.)
While it sounds pretty solid (and it is) there's still a potential for corruption, but it's rare. If a drive swings the access arms to a specific track and starts writing data, the assumption is that the write head is above the correct track. If the head is "sloppy" due to wear, then the head may be slightly mis-aligned and bleeding writes into the adjacent track. This will cause filesystem corruption even with journaling enabled.
If these drives came with the computers then the only warranty would be via Apple. If you purchased these drives on your own then they probably came with a pretty good manufacturer warranty -- most drives I've purchased in recent years had at least a 3 year warranty.

Filesystem corruption --- how to prevent?

Sometimes one has to do a hard reset.
When reading about btrfs, its 'copy-on-write'-feature got my attention. 1. Does btrfs completely prevent filesystem corruption on a hard reset?
I'm asking because recently my / (ext4) filesystem on my laptop got corrupted after a hard reset. I blame powertop's suggestion of setting /proc/sys/vm/dirty_writeback_centisecs to 1500, which I'll never do again, I guess. Lost no data, so it's not important. But I have to setup this laptop again --- ext4 or btrfs or something other? (in any case backups will be made --- so btrfs's experimental status doesn't bother me).
2. Are there any filesystem-agnostic system settings which prevent filesystem corruption on a hard reset? If so --- do they have performance penalities or other drawbacks?
Also: 3. What about the 'sync' mount option?
Also: 4. What about other layers like lvm, dm-crypt, dm-raid etc?
Last edited by g3n3r1c (2013-07-28 16:51:23)

cfr wrote:Were you using non-default options with ext4? (Not journalling or changes to the use of barriers etc.)
I was using (wrote it all down ):
Creation:
mke2fs -vt ext4 -E lazy_itable_init=1 -O dir_index,uninit_bg /dev/disk/by-uuid/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
(for every volume)
/etc/fstab
tmpfs /tmp tmpfs auto,async,noatime,nodev,nodiratime,noexec,nosuid,nouser,rw 0 0
UUID=037c4679-a4ef-42a1-bc9e-17a4c41b6283 swap swap pri=1 0 0
UUID=fd8bf3d6-9693-41c2-95ea-c39b3b0d9443 / ext4 auto,async,dev,exec,nouser,noatime,nodiratime,suid,rw 0 1
UUID=4a8985e4-be31-4757-88cd-5f958e4ba6b9 /boot ext4 auto,async,noatime,nodev,nodiratime,noexec,nosuid,nouser,rw 0 1
UUID=b5826354-772c-462f-86f5-c55b625b11cc /var ext4 auto,async,noatime,nodev,nodiratime,noexec,nosuid,nouser,rw 0 1
UUID=6f47fe27-3cbe-4f72-bd3b-d0d10fc4fff3 /home ext4 noauto,async,noatime,nodev,nodiratime,nouser,rw,acl,x-systemd.automount 0 2
I think this does nothing to journaling.
The system was using a cryptdevice directly on disk without partitions with lvm on top and ext4 on top of the lvms, boot was a partition on an usb key.
When / got corrupted i was still able to access /var and /home with a live medium.
Last edited by g3n3r1c (2013-07-28 22:07:30)

Filesystem Corruption?

Hi, Folks,
While this is indeed conjecture, it appears that the 2.0 series of firmware has a filesystem corruption problem as the amount of content on the device increases - in particular, once many applications have been installed. The behavior that I've witnessed in this circumstance is somewhat progressive. Initially, application install or updates begin to slow down dramatically. User behavior starts to contribute to the problem: when an update might takes more than five minute, folks may try aborting the update or sync, which often leads to a corrupted filesystem. This is easy to identify; powering down then back up again will lead to an "Apple logo" hang. Only a DFU restore will recover from this failure.
Much more significant is that even in the absence of inappropriate user behavior, the filesystem issue continues to worsen over time. For techies, the symptoms appear quite similar to serious fragmentation (or analogously for in-memory issues, garbage collection). I'm beginning to think that the core Flash filesystem code has a bug which starts to yield incorrect FS handling once many files are present. A key symptom is that attempts to restore from a backup will often report that the backup file is corrupted. My best guess is that the backup itself was probably performed properly, but the reported corruption actually may have been caused by the iPhone's filesystem itself becoming corrupted prior to the backup.
After having run into this issue often enough that I've needed to perform ~10 DFU restores on three iPhones (one original 8GB, and two 3G 16GB devices), this indeed appears to be a serious problem. Though my guess is that the iPhone's filesystem code is the root cause, I'm interested in hearing feedback from other folks who may have encountered this issue. Are the problems which you've seen consistent with this hypothesis?
Cheers!
Mark

Hello!
I'll add one more interesting data point. I've since found that I have had two different backup files that take well over an hour to restore onto a newly DFU-restored phone. On both of these files, the backup would proceed fairly quickly to a specific point (~50% on one file, and about 75% on the other file), and then would stop (the progress bar kept spinning, but with no forward progress) for about 1 hour, and then would continue and ultimately succeed. It's intriguing that repeating this process with each of these files yielded exactly the same "pause point".
While the thought of a timeout occurring is still quite appropriate, this further suggests that if the core filesystem code is at fault, the error might be induced by a NAND/iNAND error condition (NAND Flash always has errors, by design; Flash filesystems are supposed to handle those errors gracefully). This deterministic very-long-delay condition suggests that (normal) Flash errors just might be confusing the filesystem driver.
FYI!
Mark

Frequent Filesystem Corruption

*+Hello Interwebs!+*
OK, I'll just jump right into the heart of the matter. I'm a tech for my local school district and we are having some problems with our iMac Multimedia Lab. Over the past nine months, 5 of the 22 iMacs have suffered from filesystem corruption. The only recourse for these machines has been to completely wipe out the OS X partition and start fresh (with appropriate restore from Time Machine.)
*_Here's the list for why I know it's file system corruption:_*
The iMac will not boot OS X. I have seen it stop at the "throbber", the progress bar, or just the Apple logo.
Mounting the iMac disk via Target Disk Mode (love that feature) succeeds, but only for the Bootcamp partition. The OS X partition fails to mount.
A verify of the disk reveals the OS X partition needs to be repaired (I've seen invalid sibling entries, orphaned children etc.). Attempting to repair the disk fails. This latest attempt (just yesterday) said that the catalog B trees could not be rebuilt. I should have made more complete notes on what was said each time, but each time until this last one I assumed it was an odd one-in-a-million kind of event. A fluke
 Attempting to repair or rebuild the drives with Drive Genius 3 also fails
So far 98% of the user's files have been recoverable via Data Rescue 3
The physical hard drive does not appear to be failing (retrieving files from the drive does not hang or "beachball", the drive does not appear and disappear in Disk Utility, Finder remains responsive, etc.)
 Normally I'd chalk it up to a series of bad drives. Just happened to be the unlucky guy who purchased a bad run of iMacs, right? Here's where things start to get interesting. I submit to you, the list of oddities:
 The drives verify as good via SMART
 The RAM checks out
 After deleting and re-creating the partition (and re-installing OS X) all problems disappear.
 The corruption has not happened to the same Mac twice
 Bootcamp is installed on the same drive and functions before, after, and during the corruption on the Mac side.
 The Bootcamp partition has not had this issue on ANY of the iMacs
*_Also, to rule out the obvious:_*
 There have been no brownouts or surges
 We seriously doubt a virus, as the malfunctions appear anywhere from simultaneously (two machines went down at the same time about a month ago) to months apart. Plus, the user's documents are restored after reformat, so one would surmise that if it were a malicious program the Mac would keep failing again and again.
 The machines have been in a climate-controlled area
 It has not been the same user affected
 Sometimes the problem occurs after an unavoidable hard shutdown (which occurs only infrequently. These machines are not being excessively powered down improperly. Only what you would expect with a Mac Lab running multimedia five days a week), other times it is completely out-of-the-blue
*_And last but not least, the specs:_*
 iMac 10,1 (21.5 inch)
 Stock drives
 OS X Snow Leopard (latest updates)
 Stock memory
 Joined to our Active Directory infrastructure
 HFS+ file system (not case sensitive, the default for OS X Snow Leopard)
 No out-of-the-ordinary drive maint. programs. Drive Genius was loaded yesterday afternoon (AFTER recovering from the latest failure) to run a verification on all iMacs, but was not installed prior. All Macs, both those that have failed in the past and those that have never failed, passed with flying colors.
*_Frequently used software includes:_*
 iPhoto
 iDVD
 iMovie
 Safari
The machines are also loaded with Parallels 5, which loads the Bootcamp partition into a VM. Parallels was setup via the standard wizard, no oddball configuration or hacks.
TL;DR:
*The OS X partition has become corrupted on five different iMacs, but the physical drives are fine. WHY!?*

I have TechTool Pro: what tests do you run with that?
I'm inclined to believe that you may have a failing drive that's just not being recognised by the tools you have to hand. I'd encourage you to make a couple of secure backups as soon as possible, and consider changing the drive forthwith.
Maybe someone else can offer less scare-mongery advice…

Filesystem corruption in Mac OS X

I have just run a md5sum check on a 300GB partition which I used as a "Reference" partition which is mounted read-only 99% of the time. I keep such things as software, music, e-books and all other reference documents which will not change on it. Most files have an md5sum checksum attached to them which is kept in a separate file.
I run a md5sum check every once in a blue moon. I guess I ran the last one some time in the past 5 years. I ran one today, and discovered with great alarm that 5 files none of which I have touched for years and years have failed the md5sum check.
Of the files I was able to recover from another source, I have found that the failure in every case involved a difference of an entire 4kB sector. The error in each case involved incorrectly read data with no warning of a bad sector or a bad read, or any indication that the data may be corrupt. Is this more likely to be a hardware-related failure or a kernel software filesystem-related failure? Has anybody ever conducted a systematic study of data integrity guarantees in Mac OS X filesystems? What is the hardware error rate of a typical disk? How reliable is the filesystem, and in what circumstances can corruption occur? Is this well understood?

Dr. T wrote:
I would dispute this. It is not well known, I believe, although I would hope it is at least moderately well known, that when you read a data-grade CD-ROM or DVD-ROM on Mac OS X, you will with a reasonable frequency (more than 1 sector/6GB read in my experience) occasionally get a silent incorrectly read sector. Yet this is factual.
Those are optical media consisting of some clear plastic and optical film. Plus, they don't even use HFS+ so it is a bit of a moot point.
I am interested in a rate in the form of number of sector silently returned differently read to the data originally written, per amount of data written. Thanks.
In other words, what percentage of written data will be read differently? That depends on a number of factors such as age of drive, hours of use, usage conditions, environmental conditions, etc. File system used on the disk is irrelevant. All disks die eventually - some after 6 months, some after 5 years.
I run the md5sum checksum check only occasionally. The data is occasionally copied from one disk to another, but whenever I do this, I do not only check md5sum checksums, I make precautions to ensure that all data caches are flushed before running a full compare between the original and the copy. The current disk is less 2 years old, and the partition is the sole partition on that drive. The disk is a standard Western Digital server-grade drive. You may prefer buying Best Buy disks yourself, I will leave this to you.
I actually buy my disks from Other World Computing, but they are the same drives that Best Buy sells. I've never run checksums on all my data and, frankly, I'm not going to. It isn't worth my time. If your data is critical and it is worth your time, you need to use professional quality hardware. A single WD drive does not qualify. You need to look at a RAID, at a minimum. Tape would be good too. The professional storage systems are designed to be big, fast, and automatically recover from failures like what you have experienced. They don't come cheap and WD doesn't sell them. Look at Sun, IBM, HP, EMC, those kind of people.
I thought he meant the sort of professional-grade filesystem used in the Unix world, such as perhaps ZFS or ReiserFS, but I may be mistaken.
You can never be too sure. Ask a specific question and you'll get a specific answer.
It is a stretch to call ZFS "professional-grade". It is brand new. There is experimental support for it in 10.5 but it will be a while before it is ready for the general public. In any event, ZFS on a single drive won't be that much better than HFS+ on a single drive. It is only as good as the media. If the media has no redundancy, neither does the file system.
ReiserFS is a Linux file system, not Unix. There is a difference. It has its own set of problems. Agsin, it would be a stretch to claim ReiserFS is sigificantly different or better than any other modern file system.

New message on stopping filesystem [BUG solved]

Well, today there is an update for filesystem package, and I have installed it by Pacman -Syu, but now when I am stopping PC, and it's going to stop filesystem daemon, appears this message:
umount: /dev device is busy
Before upgrading, it don't appear.
It's normal? Is there anyone who has the same problem?
Greetings
Last edited by Davigetto (2007-05-13 12:45:53)

I have catch some part of the message while rebooting:
Saving Random Seed [DONE]
Saving System Clock [DONE]
Unmounting Filesystems [BUSY]
-> umount: /dev: device is busy
REBOOTING...
That message has appeared to me without any apparent reason... What must I do to solve it? It would be very painfully for me reinstall all again... -.-'
Greetings

Root filesystem corrupted, only var left

Hi fellow Arch users!
I was wondering if anybody would have an idea if it would be possible to restore packages and rebuild the system having only var partition.
In short - I have had an encrypted system with var and home stored on separate hard drives. Unfortunately hard drive that was storing root of the system got broken and I lost everything apart var and home.
I would be grateful for your thoughts,
Greg
Last edited by Gregosky (2014-10-14 19:18:14)

I came back from holiday and started working on restoring my Arch from var. Here is what I have done: I have formatted my new SSD hard drive, mounted it as /mnt, created /mnt/var and /mnt/boot, then I have mounted my var and boot partitions. Once mounted I have executed following:
pacman -r /mnt -Syu
. All packages were rebuilt and filesystem structure was restored however at the moment I'm unable to chroot to /mnt.

Checking package integrity... corrupted [ SOLVED ]

I got this error,
checking package integrity...
error: archive flac-1.1.4-1.pkg.tar.gz is corrupted
archive flac-1.1.4-1.pkg.tar.gz is corrupted
prompt#
What can I do ?
I got this while running pacman -Syu Can I do pacman -Syu "minus flac" ?
Last edited by go4it (2007-03-28 20:09:00)

lucke wrote:rm /var/cache/pacman/pkg/flac-1.1.4-1.pkg.tar.gz and run pacman again.
Good to remember should I have this problem again
Many thanks !

Unknown filesystem error [solved]

I just updated arch and now when I try to mount my usb harddrive I get this error:
# mount /mnt/usbdrive
mount: unknown filesystem type 'vfat'
Anyone know whats up?

I met the same problem.
the key is that the kernel is updated ( e.g. from 2.23 -> 2.24 ).
the vfat kernel module reside in difference directory (/lib/modules/XXXx-2.24/)after update.
but the kernel version in /proc is the old one , until you reboot.
if you don't reboot, when load the vfat module, the insmod will search the /lib/modules/`uname -r` , which can found nothing to load. well, what you get is nothing but some string like
# modprobe vfat
FATAL: Could not load /lib/modules/2.6.23-ARCH/modules.dep: No such file or directory.
so, you can understand why you are happy now.

Error: archive mozilla-firefox.pkg.tar.gz is corrupted.solve

I wanted to see which of Opera and FireFox was bigger but started the download. Instinctly I do ^C-c just to soon notice the above (subject name) error when trying to install firefox. I've tried to force it without success. I can't find the package neither when searching with "find". Help appreciated.

Stinky wrote:
You'll find the package in
/var/cache/pacman/pkg/
..and delete it then try again.

NX 6800 Ultra Freezes and screen corruption (Solved by PSU)

I bought this card a few months ago and have had problems consistently with it. Sometimes when I boot up my screen goes orange and is comepletly scrambled.
More importantly when ever I play World of Warcraft 8 times out of 10 the game will freeze on load. Other times it will freeze during game play. Other times I will get the orange scrambled screen again.
I have the latest drivers and a 500w power supply. As a test I out my old Geforce back in (a 4600). All the problems disappeared. So I am confident the card is the root of my problems. Someone suggested I upgrade the firmware of the card. No idea how to do that and I cant see a link on the download/driver page.
Any ideas?
Thanks

Quote from: solomani on 17-May-05, 20:59:11
I have the latest drivers and a 500w power supply. As a test I out my old Geforce back in (a 4600). All the problems disappeared. So I am confident the card is the root of my problems.
Just because you have a 500w power supply doesn't mean it is powerful enough. Some 350w PSU's are more powerful than a 500w PSU. Unfortunately the power of the power supply is backed by the amps on the individual rails (3.3, 5, 12) instead of volts. If you could post the amps on those it would help us eliminate that as a problem. You can find them on a sticker on the side of the PSU.
That is what seems like the issue to me. The reason why things worked fine with the old card is it is not nearly as power hungry as your current card.
Also if you could post more hardware specs of your system it would help. Follow my signature for the info you should include.
Good Luck
Jeremy

[SOLVED - Filesystem issue]Pacman corrupt - urgent help needed

Erm, little problem here.
Updated last night as normal and powered down my rig.
This evening I got home, powered up and typed in
sudo pacman -Syu
and was greeted with the following:
[llawwehttam@Steelhorn ~]$ sudo pacman -Syu
Password:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
error: could not open file /var/lib/pacman/sync/core/file-5.04-3/desc: Input/output error
error: could not open file /var/lib/pacman/sync/core/file-5.04-3/desc: Input/output error
error: could not open file /var/lib/pacman/sync/core/file-5.04-3/desc: Input/output error
error: could not open file /var/lib/pacman/sync/core/file-5.04-3/desc: Input/output error
error: could not open file /var/lib/pacman/sync/core/file-5.04-3/desc: Input/output error
error: could not open file /var/lib/pacman/sync/extra/rtmpdump-2.3-3/desc: Input/output error
*snip - lots of copies*
resolving dependencies...
looking for inter-conflicts...
Targets (2): findutils-4.4.2-3 lib32-gtk2-2.22.1-2
Total Download Size: 2.09 MB
Total Installed Size: 7.90 MB
Proceed with installation? [Y/n]
After some googling I came to the conclusion that pacman was corrupt.
I have NO idea how this happened.
Is there a way to fix this without a re-install?
Help is very much appreciated.
EDIT:
I have read the thread here: https://bbs.archlinux.org/viewtopic.php?id=95007 but I'm not sure if that would apply in this situation.
EDIT2:
Tried this:
$ $ sudo pacman -Syy
:: Synchronizing package databases...
core 35.9K 287.2K/s 00:00:00 [################################] 100%
error: could not remove database core
error: failed to update core (could not remove database entry)
extra 449.2K 446.1K/s 00:00:01 [################################] 100%
error: could not remove database extra
error: failed to update extra (could not remove database entry)
community 405.7K 366.7K/s 00:00:01 [################################] 100%
error: could not remove database community
error: failed to update community (could not remove database entry)
multilib 21.8K 251.3K/s 00:00:00 [################################] 100%
archlinuxfr 23.0K 237.6K/s 00:00:00 [################################] 100%
doesn't look normal.
Any ideas much appreciated.
EDIT3: More info:
$ cd /var/lib/pacman/sync/core/file-5.04-3/
[llawwehttam@Steelhorn file-5.04-3]$ ls
ls: cannot access desc: Input/output error
ls: cannot access depends: Input/output error
depends desc
$ ls -l /var/lib/pacman/sync{,/*}
/var/lib/pacman/sync:
total 248
drwxr-xr-x 116 root root 4096 Nov 24 19:57 archlinuxfr
drwxr-xr-x 4 root root 94208 Nov 24 19:15 community
drwxr-xr-x 7 root root 12288 Nov 24 19:15 core
drwxr-xr-x 3 root root 131072 Nov 24 19:15 extra
drwxr-xr-x 125 root root 4096 Nov 24 19:57 multilib
/var/lib/pacman/sync/archlinuxfr:
total 456
drwxr-xr-x 2 root root 4096 Nov 24 19:57 afur-aur-1.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 afur-makepkg-0.3-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 arora-git-20101002-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 asd-tower-defense-v2.0_beta4-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 aurvote-0.4-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 awesome-3.4.8-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 azenis-icon-theme-0.1.1-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 b43-firmware-4.178.10.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 balz-1.15-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 batterysystemtray-git-20101122-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 bepo-keymaps-1.0rc2-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 bin32-flashplayer-standalone-10.1.85.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 bin32-skype-staticqt-2.1.0.81-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 cairo-dock-2.1.3-9
drwxr-xr-x 2 root root 4096 Nov 24 19:57 cairo-dock-themes-1.6.3.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 cairo-xcb-1.10.0-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ccsm-0.9.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 celt-0.7-0.7.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 celt-0.8.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 cgit-0.8.3.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 clipgrab-3.0.7.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 codecs-20100303-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 compiz-core-0.9.2-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 compiz-plugins-extra-0.9.2-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 compiz-plugins-main-0.9.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 compiz-plugins-unsupported-0.9.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 compizconfig-python-0.9.2-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 customizepkg-0.2.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 emerald-git-20101118-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 fbpanel-6.1.491svn-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 fbpanel-fr-6.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 flashplugin-prerelease-10.2.161.23-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 fluxbox-git-20100912-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 foremost-1.5.7-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-gcj-4.5.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-gcj-ecj-4.5-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc43-4.3.4-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gerix-wifi-cracker-ng-r20-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 go-openoffice-fr-3.2.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gsimplecal-0.6-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gtk-theme-overglossed-hybrid-0.1-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 jaolt-0.5.3_627-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 jumanji-git-20101001-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kernel-sources-2009.06.13-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kernel26-i915-2.6.35-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kernel26-xen-2.6.35.8-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kernel26-xen-headers-2.6.35.8-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kernel26rt-2.6.33.7_rt29-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 kirikoo-upload-0.4.6-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-jack-0.118.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libv4l-0.6.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libafterimage-1.18-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libcompizconfig-0.9.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libfm-0.1.14-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libiptcdata-1.0.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libjpeg7-7-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libpng12-1.2.43-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lsb-release-1.4-10
drwxr-xr-x 2 root root 4096 Nov 24 19:57 man-pages-fr-3.03.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 mechtower-1.0.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 mkgmap-r1728-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 mumble-1.2.2-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 nautilus-elementary-162-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 nautilus-gkim-0.6.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 obapps-0.1.7-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 obkey-git-20101028-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-ar-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-base-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-de-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-es-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-fi-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-fr-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-it-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-nb-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-nl-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-pt-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-sl-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-uk-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-zh-CN-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 ooo4kids-zh-TW-1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 openbox-menu-0.3.5-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 package-query-0.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pacman-color-3.4.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pari-2.3.5-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pastebin-0.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pcmanfm-0.9.8-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pdftk-1.41-6
drwxr-xr-x 2 root root 4096 Nov 24 19:57 playonlinux-3.8.6-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 pure-ftpd-1.0.29-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 python-networkx-1.3-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 qrun-0.50-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 quad-1.12-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 rar-3.9.3-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 rar-beta-4.0.b1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 rawtherapee-3.0a1-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 redshift-1.6-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 repacman-0.98-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 rxvt-unicode-afterimage-9.06-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 sdesktop-0.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 stapler-2b-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 tint2-svn-523-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 toilet-0.2-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 trayfreq-fr-0.2.x.dev2-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 tuxbox-3.1.4-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 tuxracer-0.61-8
drwxr-xr-x 2 root root 4096 Nov 24 19:57 usmb-20100212-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 volumeicon-0.2.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 wto-1.0.3-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 xcas-0.9.0-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 xcfa-3.7.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 xcompmgr-dana-20091025-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 xfce4-gkim-0.6.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 yaourt-0.9.5.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 yget-2.2.1-1
/var/lib/pacman/sync/community:
total 0
d????????? ? ? ? ? ? python-openbabel-2.3.0-2
d????????? ? ? ? ? ? python2-openbabel-2.3.0-2
/var/lib/pacman/sync/core:
total 4
drwxr-xr-x 2 root root 4096 Nov 21 09:54 file-5.04-3
d????????? ? ? ? ? ? gzip-1.4-2
d????????? ? ? ? ? ? less-436-2
d????????? ? ? ? ? ? patch-2.6.1-2
d????????? ? ? ? ? ? sed-4.2.1-3
/var/lib/pacman/sync/extra:
total 4
drwxr-xr-x 2 root root 4096 Nov 24 19:15 rtmpdump-2.3-3
/var/lib/pacman/sync/multilib:
total 492
drwxr-xr-x 2 root root 4096 Nov 24 19:57 binutils-multilib-2.20.1-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 chuck-1.2.1.3-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 dwarffortress-0.31.18-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 flashplugin-10.1.102.64-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-ada-multilib-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-fortran-multilib-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-libs-multilib-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-multilib-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 gcc-objc-multilib-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-alsa-lib-1.0.23-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-alsa-oss-1.0.17-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-alsa-plugins-1.0.23-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-ati-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-atk-1.32.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-attr-2.4.44-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-audiofile-0.2.7-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-cairo-1.10.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-curl-7.21.2-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-db-4.8.26-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-dbus-core-1.4.0-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-e2fsprogs-1.41.12-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-expat-2.0.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-flac-1.2.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-fontconfig-2.8.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-freetype2-2.4.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-gcc-libs-4.5.1-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-gdk-pixbuf2-2.22.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-giflib-4.1.6-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-glib-1.2.10-11
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-glib2-2.26.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-glibc-2.12.1-9
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-gnutls-2.8.6-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-gtk-1.2.10-11
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-gtk2-2.22.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-heimdal-1.3.3-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-intel-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-jack-0.118.0-6
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-lcms-1.19-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libasyncns-0.8-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libcanberra-0.25-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libcap-2.19-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libcups-1.4.5-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libdrm-2.4.21-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libflashsupport-9.0.21.78-10
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libgcrypt-1.4.6-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libgl-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libgpg-error-1.9-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libice-1.0.7-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libjpeg-8.0.2-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libldap-2.4.22-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libmng-1.0.10-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libogg-1.2.0-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libpng-1.4.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libsamplerate-0.1.7-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libsm-1.2.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libsndfile-1.0.21-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libstdc++5-3.3.6-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libtiff-3.9.4-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libtool-2.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libvorbis-1.3.1-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libx11-1.3.5-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxau-1.0.6-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxcb-1.7-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxcomposite-0.4.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxcursor-1.1.11-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxdamage-1.1.3-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxdmcp-1.0.3-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxext-1.2.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxfixes-4.0.5-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxft-2.2.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxi-1.3.2-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxinerama-1.1.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxml2-2.7.7-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxmu-1.0.5-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxpm-3.5.8-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxrandr-1.3.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxrender-0.9.6-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxslt-1.1.26-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxss-1.2.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxt-1.0.9-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxtst-1.1.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxv-1.0.5-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxvmc-1.0.6-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxxf86dga-1.1.1-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-libxxf86vm-1.1.0-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-mach64-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-mesa-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-mga-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-mpg123-1.12.3-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-ncurses-5.7-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-nouveau-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-nspr-4.8.6-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-nss-3.12.7-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-nvidia-utils-260.19.21-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-openal-1.12.854-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-openssl-1.0.0.a-6
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-pango-1.28.3-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-pcre-8.10-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-pixman-0.20.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-pulseaudio-0.9.21-14
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-qt-4.7.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-r128-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-readline-6.1.002-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-savage-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-sdl-1.2.14-7
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-sdl_image-1.2.10-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-sdl_ttf-2.0.10-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-sis-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-speex-1.2rc1-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-sqlite3-3.7.1-2
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-tdb-1.2.1-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-tdfx-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-unichrome-dri-7.8.2-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-util-linux-ng-2.18-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-v4l-utils-0.8.1-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-xcb-util-0.3.6-3
drwxr-xr-x 2 root root 4096 Nov 24 19:57 lib32-zlib-1.2.5-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 libtool-multilib-2.4-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 nspluginwrapper-1.3.0-4
drwxr-xr-x 2 root root 4096 Nov 24 19:57 skype-2.1.0.81-5
drwxr-xr-x 2 root root 4096 Nov 24 19:57 wine-1.3.7-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 wine_gecko-1.1.0-1
drwxr-xr-x 2 root root 4096 Nov 24 19:57 zsnes-1.51-7
Last edited by llawwehttam (2010-11-24 20:29:43)

loafer wrote:It's the sync DB which has the problem. Rename the dirs to core-old etc. and then "pacman -Syy" to force a download. If that fixes it you can just delete the old ones.
Thanks,
Ill try that in a minute.
I guessed that Input/output error meant filesystem corruption so I rebooted using :
sudo shutdown -rF now
and the resulting fsck on bootup had a few errors.
Manually fixed them and now waiting for fsck to finish.
Could take a while.
I'll update when it boots.
update:
Booted,
sudo pacman -Syy
*no errors*
sudo pacman -Syu
*no errors*
Guess its fixed then.
I see how your fix would work, but I'm not sure I would have been able to rename the folders if they contain corrupted files.
Thanks anyway,
Matt
Last edited by llawwehttam (2010-11-24 20:27:35)

[solved] Hibernate corrupting NTFS-Filesystem

Hey Guys.
I'm running an Dualboot of Arch (x64) and Win7 (32bit) for a long time now, perfectly. sda1 is my ntfs formatted windows partion, sda2 and following arch. I have a little Script that hibernates arch and set grub to boot windows, it looks like this:
#!/bin/bash
echo "Press ENTER to boot Windows"
read -s -n 1
grub-set-default 2
suspend2disk
And it worked perfectly till today. The mistake was to make a new install of windows (the old one was messed up due some software testing), and i decided to use the x64 win7. I don't know if its cause of this. But now the hole hibernating thing is crashing my ntfs filesystem.
Steps to reproduce: umount and format sda1, suspend. Install windows, booted from an arch-cd and setting up my grub again. resumed arch, mount sda1 and copied some install sources to the windows desktop (i have the folder as bookmark in thunar), running the hibernate script and booted windows. I installed a hole bunch of things on windows, and deleted the install sources from desktop. After finishing this (no arch boot meanwhile), i rebooted and bring up my arch again. I opened Thunar and accessed the windows desktop. And surprise, there are the install sources on desktop. It shows the folder like before the hibernate. confused about this, i remounted the partition, but no change. Booting windows again results in an nice filesystem corruption error and a system rescue. So, the question is: Why?
I should say, that today i updated gamin (0.1.10-4 -> 0.1.10-5). Could this be the culprit? maybe just an accident that the reinstall of windows and the update happens the same day.
I will test to umount the ntfs before suspending, maybe it will help. Or maybe just remounting read-only will do the job.
So far, Corubba
Last edited by Corubba (2011-08-24 22:24:37)

After resuming from hibernation, the system is supposed to be in the same state as before the hibernation. You cannot modify a hibernated mounted file system without corrupting it. A mounted filesystem can never be modified by a tool when it is mounted and this is exactly what you do. In principle remounting it read only is not sufficient either.
The hibernation cannot unmount all filesystems before hibernating because that would just mean rebooting the normal way, not hibernating (but it could make sense to unmount the specific filesystem you want to access, for example the Windows one).
In your situation, you have to fully unmount the windows ntfs partition before hibernating your computer and be sure you do not access the linux partition from windows in any way.

[SOLVED] Filesystem check failed

Hi all,
i've just upgraded the system, but when rebooting it gives me that error on sda5 (the linux partition) and suggests me to repair manually and reboot! what should i repair? can you please give me any suggestion?
Thanks in advance
Last edited by virusso80 (2010-01-15 15:48:04)

guisacouto wrote:
it seems like today is broken filesystem day.. LOL
I had this problem too in my laptop and that fsck solved it very well!
unfortunatly I cannot say the same thing about the external hard drive that is connected to the desktop which has a fat32 filesystem corrupted.. I'm trying to find some courage to format it, because testdisk can only recover the files with some default name.. thats not good enough because 320GB of music, movies and documents isnt very usefull without the real names.. x| I guess this is just not my day
regards!
There's a /sbin/fsck.vfat as well.

Filesystem corrupted [SOLVED]

Similar Messages

Maybe you are looking for