Nuts. How about "cat /proc/meminfo"?

Is there anything else i can try to fix this problem?

Here's what I get when I use cat /proc/meminfo:

empeg:/empeg/bin# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 11161600 3391488 7770112 1269760 520192 1552384
Swap: 16412672 0 16412672
MemTotal: 10900 kB
MemFree: 7588 kB
MemShared: 1240 kB
Buffers: 508 kB
Cached: 1516 kB
SwapTotal: 16028 kB
SwapFree: 16028 kB

After running
ls -lF /
swapon /dev/hda6
cat /proc/meminfo

here's what I get:


empeg:/empeg/bin# ls -lF /
total 23
drwxr-xr-x 2 0 0 1024 Apr 1 2003 bin/
drwxr-xr-x 2 0 0 1024 Jul 4 2000 dev/
drwxr-xr-x 5 0 0 1024 Oct 12 07:30 drive0/
drwxr-xr-x 2 0 0 1024 Jun 2 1999 drive1/
drwxr-xr-x 4 0 0 1024 Apr 1 2003 empeg/
drwxr-xr-x 3 0 0 1024 Sep 15 1999 etc/
drwxr-xr-x 2 0 0 1024 Feb 9 2000 lib/
drwx------ 2 0 0 12288 Apr 1 2003 lost+found/
drwxr-xr-x 2 0 0 1024 Jun 2 1999 mnt/
dr-xr-xr-x 21 0 0 0 Oct 23 15:13 proc/
lrwxrwxrwx 1 0 0 3 Apr 1 2003 sbin -> bin/
lrwxrwxrwx 1 0 0 10 Apr 1 2003 swapfile -> ./dev/hda6
drwxr-xr-x 2 0 0 1024 Apr 13 1999 tmp/
drwxr-xr-x 4 0 0 1024 Feb 6 2000 usr/
drwxr-xr-x 3 0 0 1024 Aug 28 1999 var/

empeg:/empeg/bin# swapon /dev/hda6
Adding Swap: 16028k swap-space (priority -2)

empeg:/empeg/bin# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 11169792 9031680 2138112 1265664 3768320 3538944
Swap: 16412672 0 16412672
MemTotal: 10908 kB
MemFree: 2088 kB
MemShared: 1236 kB
Buffers: 3680 kB
Cached: 3456 kB
SwapTotal: 16028 kB
SwapFree: 16028 kB

empeg:/empeg/bin#

Okay, that all looks good.

And the filesystem check still fails if run immediately after the swapon /dev/hda6 command ?

When I run the swapon /dev/hda6 command, i see this:

Adding Swap: 16028k swap-space (priority -1)



Then when I get to fsck -fay /dev/hda4, I see this:

Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
no room for private writable mapping
error: -12
fsck.ext2: Memory allocation failed while retrying to read bitmaps for /dev/hda4

It looks like this has happened a couple of times before, with "large" drives of the time. I bet that there's something more than usually wrong with the hard drive and fsck needs more memory than usual. Let's try adding more swap space and see what happens:

Code:

---

mkswap /dev/hda2
swapon /dev/hda2
fsck -fay /dev/hda4

---

ISTR that you don't have a second drive, but if you do, and those steps didn't work, also try this:

Code:

---

mkswap /dev/hdb6
mkswap /dev/hdb2
swapon /dev/hdb6
swapon /dev/hdb2
fsck -fay /dev/hda4

---

That should add more swap space than I could possibly imagine that you need.

After running these commands, after "Pass 5: Checking group summary information", here's what I see:

Block bitmap differences: -7911454 -7911455 -7911456 -7911457 -7911458 -7925896
-15136748 -15136749 -15136750 -15136751 -15136752
Fix? yes

Free blocks count wrong for group #965 (0, counted=5).
Fix? yes

Free blocks count wrong for group #967 (0, counted=1).
Fix? yes

Free blocks count wrong for group #1847 (0, counted=5).
Fix? yes

Free blocks count wrong (94744107, counted=94744108).
Fix? yes


/dev/hda4: *****FILE SYSTEM WAS MODIFIED*****
/dev/hda4: 13891/915008 files (25.5% non-contiguous), 22369732/117113850 blocks
empeg:/empeg/bin#



I tried a sync after this, and it no longer hangs up at the "Verifying Disk Integrity" step anymore.

Thank you!

Wow, nice work puzzling through that one, Bitt!

I suppose I ought to modify the bigdisk builder to create a larger swap partition than merely 16MB. Maybe have it do 32MB by default instead.

Cheers

Well, the error message was pretty straightforward. I'd just never seen a report of fsck running out of memory with the swap enabled, so I figured the swap had merely not been enabled properly. Apparently it can run out of memory with the swap enabled, though. I don't think losing 16MB is a big deal, but this has apparently only happened three times, including this one. Eh. Do it anyway. 16MB is like four tracks.

Hi there,

last month the harddisk of my beloved MK2 crashed. I had to replace it with a new one. Experienced the same issues as in 2007. Searched Google, as I could not remember the solution. And guess what, I found my own post LOOOOOOL!


BTW: The solution in my case is to load the empeg 2.00 dev. Image. The extra custom RAM of my MK2 causes constant problems. Therefore the v2.00 seems to ignore the additional Memory.
Now with 2.00dev. and resent hijack, it runs stable as it used to for the last years! I love my empeg MK2 and my Panasonic HD1 combo more than my turbo charged subaru legacy.


Cheers

Mmm. sounds like flaky wiring on the extra RAM.
Easy enough to ignore (as you are doing) if you stick to the older releases.

Cheers