[root@W5OMR /etc/asterisk/custom]# /usr/sbin/safe_asterisk: line 125:
7375 Segmentation fault (core dumped) nice -n $PRIORITY
${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed
/usr/sbin/safe_asterisk: line 125: 17574 Segmentation fault (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed
/usr/sbin/safe_asterisk: line 125: 18918 Segmentation fault (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed
[root@W5OMR /etc/asterisk/custom]# dmesg | grep hd
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
hda: LITE-ON CD-ROM LTN-4891S, ATAPI CD/DVD-ROM drive
hdb: WDC WD800JB-00CRA1, ATA DISK drive
hdb: max request size: 128KiB
hdb: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63,
UDMA(100)
hdb: cache flushes not supported
hdb: hdb1 hdb2
hda: ATAPI 48X CD-ROM drive, 96kB Cache, UDMA(33)
EXT3 FS on hdb1, internal journal
Adding 1020116k swap on /dev/hdb2. Priority:-1 extents:1 across:1020116k
[root@W5OMR /etc/asterisk/custom]#
You linux gurus... here's my Achilles heel ... harddrive tuning. Scares
the hell out of me.
I instinctively went to e2fsck /dev/hdb2 and I get
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? uhm ... I guess 'no' ... maybe...
{{{shudder}}} what to do, what to do...
I asked the system for help ...
Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
Hmmm... ok. -n. Go check it, and make no changes, just report back
what's going on. Sounds like the option to try.
[root@W5OMR /sys/power]# e2fsck -n /dev/hdb2
e2fsck 1.39 (29-May-2006)
Warning! /dev/hdb2 is mounted.
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/hdb2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains 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>
... and, it just did it again ...
:/usr/sbin/safe_asterisk: line 125: 21504 Segmentation fault (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed
/usr/sbin/safe_asterisk: line 125: 22464 Segmentation fault (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed
