aMule Forum
English => aMule Help => Topic started by: minage on February 10, 2008, 01:41:52 AM
-
Hi,
I'm having new problems with these lastest svn...
More or less, versions after crypto++ was introduced as necessary.
Everytime i start amule it hash a part file. (i think randomly, but i'll check next times).
And since i got my pc freezed some days ago, amule seems to re-mount my external hd (where there is the incoming dir) as read only. :\
I didn't modify anything... so, today i updated the svn to (08 - 02 - 2008) and compiled right.
I mounted the hd, i tested it copying files and deleting them and everything was right. (as user of course)
I started amule, connect....everything ok...
I came back after some hours and "Error saving file.....blabla, read only file system".
So i opened a console, tryed to copy a file and i couldn't because the filesystem is read-only...
why?
thanks
edit:
this is my syslog of today (but it's very similar to the day when my pc freezed)
Feb 9 13:00:23 zurigo kernel: CPU: Intel Pentium III (Coppermine) stepping 03
Feb 9 13:00:23 zurigo kernel: ACPI: setting ELCR to 0e00 (from 0c00)
Feb 9 13:00:23 zurigo kernel: Setting up standard PCI resources
Feb 9 13:00:23 zurigo kernel: PCI: Probing PCI hardware
Feb 9 13:00:23 zurigo kernel: PCI: Firmware left 0000:00:0a.0 e100 interrupts e
nabled, disabling
Feb 9 13:00:23 zurigo kernel: PCI quirk: region f100-f13f claimed by ali7101 AC
PI
Feb 9 13:00:23 zurigo kernel: PCI quirk: region f140-f15f claimed by ali7101 SM
B
Feb 9 13:00:23 zurigo kernel: PCI: Bus 2, cardbus bridge: 0000:00:13.0
Feb 9 13:00:23 zurigo kernel: IO window: 00001400-000014ff
Feb 9 13:00:23 zurigo kernel: IO window: 00001800-000018ff
Feb 9 13:00:23 zurigo kernel: PREFETCH window: 10000000-13ffffff
Feb 9 13:00:23 zurigo kernel: MEM window: 14000000-17ffffff
Feb 9 13:00:23 zurigo kernel: PCI: Bus 6, cardbus bridge: 0000:00:13.1
Feb 9 13:00:23 zurigo kernel: IO window: 00001c00-00001cff
Feb 9 13:00:23 zurigo kernel: IO window: 00002000-000020ff
Feb 9 13:00:23 zurigo kernel: PREFETCH window: 18000000-1bffffff
Feb 9 13:00:23 zurigo kernel: MEM window: 1c000000-1fffffff
Feb 9 13:00:23 zurigo kernel: IP route cache hash table entries: 2048 (order: 1
, 8192 bytes)
Feb 9 13:00:23 zurigo kernel: TCP established hash table entries: 8192 (order:
3, 32768 bytes)
Feb 9 13:00:23 zurigo kernel: TCP bind hash table entries: 4096 (order: 2, 1638
4 bytes)
Feb 9 13:00:23 zurigo kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://
www.scyld.com/network/eepro100.html
Feb 9 13:00:23 zurigo kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified
by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Feb 9 13:00:23 zurigo kernel: hda: IBM-DARA-206000, ATA DISK drive
Feb 9 13:00:23 zurigo kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 9 13:00:23 zurigo kernel: hdd: CRN-8241B, ATAPI CD/DVD-ROM drive
Feb 9 13:00:23 zurigo kernel: ide1 at 0x170-0x177,0x376 on irq 15
Feb 9 13:00:23 zurigo kernel: ide-floppy driver 0.99.newide
Feb 9 13:00:23 zurigo kernel: nf_conntrack version 0.5.0 (1535 buckets, 12280 m
ax)
Feb 9 13:00:23 zurigo kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 9 13:00:23 zurigo kernel: Using IPI Shortcut mode
Feb 9 13:00:23 zurigo kernel: VFS: Mounted root (reiserfs filesystem) readonly.
Feb 9 13:00:23 zurigo kernel: sda: assuming drive cache: write through
Feb 9 13:00:23 zurigo kernel: sda: assuming drive cache: write through
Feb 9 17:01:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:01:51 zurigo kernel: clusters badly computed (616 != 601)
Feb 9 17:01:51 zurigo kernel: File system has been set read-only
Feb 9 17:02:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:02:51 zurigo kernel: clusters badly computed (617 != 602)
Feb 9 17:02:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:02:51 zurigo kernel: clusters badly computed (618 != 603)
Feb 9 17:02:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:02:51 zurigo kernel: clusters badly computed (619 != 604)
Feb 9 17:03:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:03:51 zurigo kernel: clusters badly computed (620 != 605)
Feb 9 17:04:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:04:51 zurigo kernel: clusters badly computed (621 != 606)
Feb 9 17:10:24 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:10:24 zurigo kernel: clusters badly computed (622 != 607)
Feb 9 17:10:24 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:10:24 zurigo kernel: clusters badly computed (623 != 608)
Feb 9 17:10:24 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:10:24 zurigo kernel: clusters badly computed (624 != 609)
Feb 9 17:10:24 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:10:24 zurigo kernel: clusters badly computed (625 != 610)
Feb 9 17:11:06 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:11:06 zurigo kernel: clusters badly computed (626 != 611)
Feb 9 17:11:06 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:11:06 zurigo kernel: clusters badly computed (627 != 612)
Feb 9 17:11:46 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:11:46 zurigo kernel: clusters badly computed (628 != 613)
Feb 9 17:11:46 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:11:46 zurigo kernel: clusters badly computed (629 != 614)
Feb 9 17:12:29 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:12:29 zurigo kernel: clusters badly computed (630 != 615)
Feb 9 17:12:29 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:12:29 zurigo kernel: clusters badly computed (631 != 616)
Feb 9 17:12:29 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:12:29 zurigo kernel: clusters badly computed (632 != 617)
Feb 9 17:13:07 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:13:07 zurigo kernel: clusters badly computed (633 != 618)
Feb 9 17:13:07 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:13:07 zurigo kernel: clusters badly computed (634 != 619)
Feb 9 17:13:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:13:51 zurigo kernel: clusters badly computed (635 != 620)
Feb 9 17:13:51 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:13:51 zurigo kernel: clusters badly computed (636 != 621)
Feb 9 17:14:34 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:14:34 zurigo kernel: clusters badly computed (637 != 622)
Feb 9 17:14:34 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:14:34 zurigo kernel: clusters badly computed (638 != 623)
Feb 9 17:14:34 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:14:34 zurigo kernel: clusters badly computed (639 != 624)
Feb 9 17:15:17 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 9 17:15:17 zurigo kernel: clusters badly computed (640 != 625)
Feb 9 17:15:17 zurigo kernel: FAT: Filesystem panic (dev sda1)
...etc...
lastest messages are:
Feb 10 01:17:30 zurigo kernel: clusters badly computed (10696 != 10692)
Feb 10 01:17:30 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 10 01:17:30 zurigo kernel: clusters badly computed (10697 != 10693)
Feb 10 01:17:30 zurigo kernel: FAT: Filesystem panic (dev sda1)
Feb 10 01:17:30 zurigo kernel: clusters badly computed (10698 != 10694)
But my hd works right on this machine, works right too if i connect it to another pc with windows.
It's have problem only if a start amule...i think.
-
Your fulesystem is corrupted. Scan it.
-
minage,
You have a corrupted file system. Either run scandisc on windows or fsck on linux. And pray. :-\
PS: Try to save any important data before doing so.
-
That's strange because I don't have any error using hd by my-self (copying, deleting, executing files...)
fsck is only for linux filesystems...so I tested the hd with windows scandisk e no problems found, now i doing an accurate test...)
-
No errors found on windows :-\
I made a bash script that write on external hd every 5 seconds and It works for hours with no problem...
I can't use dosfsck because it stop with "malloc: cannot allocate memory"... (and i don't know how to solve it...)
I really don't know what to do...only amule doesn't works...and i tried some cvs versions.
-
http://www.google.com/search?q=%22clusters+badly+computed
It's reading time.
-
No way with this fat fs.
Changed it to ext3, hope it'll work fine :)
Thanks for patience and helping ;)