>I've been having major stability issues over the last week with my 
>alix box and 0.6 build.  I have tracked it down to disk corruption 
>taking place on the CF card in the asturw partition. Things seem to 
>be exasperated by constant updates to the flash card from CDR and 
>syslogs, etc that we've been discussing in another thread.  Here is 
>an example of today's heartache...
>
>On booting...
>
>Configuring for unionfs...
>Checking asturw filesystem
>ext2fs_check_if_mount: No such file or directory while determining 
>whether /dev/
>hda2 is mounted.
>
>
>ASTURW: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>         (i.e., without -a or -p options)
>Fsck detected errors on /dev/hda2 (4)
>/bin/sh: can't access tty; job control turned off
>#
>
>Then on removing the CF card and attaching to my CentOS box to diagnose...
>
>[r...@localhost ~]# fsck /dev/sdb2
>fsck 1.39 (29-May-2006)
>e2fsck 1.39 (29-May-2006)
>ASTURW contains a file system with errors, check forced.
>Pass 1: Checking inodes, blocks, and sizes
>Extended attribute block 131557 has reference count 35, should be 
>33.  Fix<y>? yes
>
>Pass 2: Checking directory structure
>Entry 'sysinfo_output71.html' in 
>/stat/var/lib/asterisk/static-http/config (61833) has deleted/unused 
>inode 61838.  Clear<y>? yes
>
>Pass 3: Checking directory connectivity
>Pass 4: Checking reference counts
>Pass 5: Checking group summary information
>Block bitmap differences:  -149504
>Fix<y>? yes
>
>Free blocks count wrong for group #4 (32269, counted=32270).
>Fix<y>? yes
>
>Free blocks count wrong (211504, counted=211505).
>Fix<y>? yes
>
>Inode bitmap differences:  -61838
>Fix<y>? yes
>
>Free inodes count wrong for group #4 (15442, counted=15443).
>Fix<y>? yes
>
>Free inodes count wrong (107849, counted=107850).
>Fix<y>? yes
>
>
>ASTURW: ***** FILE SYSTEM WAS MODIFIED *****
>ASTURW: 342/108192 files (0.6% non-contiguous), 4711/216216 blocks
>[r...@localhost ~]#
>
>After running fsck and placing the CF card back into the alix box, I 
>boot again OK and everything seems fine. But as the system has 
>locked up on me (no calls, no internet access, cannot ssh in) a few 
>times recently I'm getting worried.
>
>All I can think of is that my CF card is going bad. It's a cheap 
>Adata 1GB and I have two of them both of which are exhibiting the 
>problem. What would be a more robust card?
>
>Thanks
>David

Hi David,

I only use SanDisk "Ultra II" and "Extreme III" 1 GB or bigger CF 
cards in several systems (mostly Soekris and i386) and never had any 
problem.

BTW: If you don't use "PERSISTLOG=yes" the syslog (and "/var") should 
go to tmpfs (run "mount" to check).

Michael

--
Email: mailto:mkeu...@web.de

------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to