journal has aborted error on FC 2

vinodkn · #1 10th May 2005, 08:36 AM

6:28 PM 5 May 2005

Fedora Core release 2 (Tettnang)
Kernel 2.6.10-1.771_FC2smp on an x86_64
login: bepuser
Password:
[bepuser@bep bepuser]$ su -
Password:
[root@bep root]# top
-bash: /usr/bin/top: Input/output error
[root@bep root]# dmesg
ice sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
scsi4 (0:0): rejecting I/O to offline device
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
scsi4 (0:0): rejecting I/O to offline device
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
EXT3-fs error (device sda6) in start_transaction: Journal has aborted
[root@bep root]#

This is the error getting after this error we have to reboot AMD FC2 server forcibily.

We have already changed the one Hard disk still problem persists.

Help required.

AndyGreen · #2 10th May 2005, 08:40 AM

What is sda? What is the interface (scsi?)
What's the cabling situation?

Is there any crisis further up maybe in /var/log/messages which can explain why sda is an "offline device" now?

vinodkn · #3 10th May 2005, 08:45 AM

sda is scsi 36 GB hdd. there r two HDDs one 36 GB first and 140 GB second one, connected with scsi cable on board Tyan M/B

AndyGreen · #4 10th May 2005, 08:46 AM

Heat? Is the failing HDD mounted above the other one?

vinodkn · #5 10th May 2005, 08:49 AM

yes one above one but we have kept cooling fan near to hdds.

AndyGreen · #6 10th May 2005, 08:52 AM

Is it the failing HDD that is on top? Just wondering how hot it gets.

Was there anything further up /var/log/messages about the point that it went offline?

vinodkn · #7 10th May 2005, 08:56 AM

but if it is because of hdd getting heated then after just a forced restart system should not come up?

after restart server works ok for some days or may be week also. our server room temp is 15 degree celsius

AndyGreen · #8 10th May 2005, 08:59 AM

Fair enough on the heat.

So what about the logs?

vinodkn · #9 10th May 2005, 09:34 AM

the log is given above after that we had to reboot the server forcibily.

one more log

5 May 2005

[bepuser@bep bepuser]$ su -
Password:
[root@bep root]# ntsysv
-bash: /usr/sbin/ntsysv: Input/output error
[root@bep root]# dmesg
-bash: /bin/dmesg: Input/output error
[root@bep root]#

AndyGreen · #10 10th May 2005, 09:37 AM

Right but in /var/log/messages, I would expect some persistant notification at the time that the drive was taken offline, from the previous boot? There is nothing?

vinodkn · #11 10th May 2005, 12:17 PM

at 6:05 PM 5 May 2005

Fedora Core release 2 (Tettnang)
Kernel 2.6.10-1.771_FC2smp on an x86_64
login: bepuser
Password:
[bepuser@bep bepuser]$ ps
PID TTY TIME CMD
3648 pts/4 00:00:00 bash
3678 pts/4 00:00:00 ps
[bepuser@bep bepuser]$ ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 3548 476 ? S 17:38 0:00 init [5]
root 2 0.0 0.0 0 0 ? SW 17:38 0:00 [migration/0]
root 3 0.0 0.0 0 0 ? SWN 17:38 0:00 [ksoftirqd/0]
root 4 0.0 0.0 0 0 ? SW 17:38 0:00 [migration/1]
root 5 0.0 0.0 0 0 ? SWN 17:38 0:00 [ksoftirqd/1]
root 6 0.0 0.0 0 0 ? SW< 17:38 0:00 [events/0]
root 7 0.0 0.0 0 0 ? SW< 17:38 0:00 [events/1]
root 8 0.0 0.0 0 0 ? SW< 17:38 0:00 [khelper]
root 24 0.0 0.0 0 0 ? SW< 17:38 0:00 [kacpid]
root 103 0.0 0.0 0 0 ? SW< 17:38 0:00 [kblockd/0]
root 104 0.0 0.0 0 0 ? SW< 17:38 0:00 [kblockd/1]
root 112 0.0 0.0 0 0 ? SW 17:38 0:00 [khubd]
root 172 0.0 0.0 0 0 ? SW 17:38 0:00 [pdflush]
root 173 0.0 0.0 0 0 ? SW 17:38 0:00 [pdflush]
root 176 0.0 0.0 0 0 ? SW< 17:38 0:00 [aio/0]
root 174 0.0 0.0 0 0 ? SW 17:38 0:00 [kswapd1]
root 175 0.0 0.0 0 0 ? SW 17:38 0:00 [kswapd0]
root 177 0.0 0.0 0 0 ? SW< 17:38 0:00 [aio/1]
root 259 0.0 0.0 0 0 ? SW 17:38 0:00 [kseriod]
root 453 0.0 0.0 0 0 ? SW< 17:38 0:00 [ata/0]
root 454 0.0 0.0 0 0 ? SW< 17:38 0:00 [ata/1]
root 459 0.0 0.0 0 0 ? SW 17:38 0:00 [scsi_eh_0]
root 460 0.0 0.0 0 0 ? SW 17:38 0:00 [scsi_eh_1]
root 461 0.0 0.0 0 0 ? SW 17:38 0:00 [scsi_eh_2]
root 462 0.0 0.0 0 0 ? SW 17:38 0:00 [scsi_eh_3]
root 471 0.0 0.0 0 0 ? SW 17:38 0:00 [scsi_eh_4]
root 472 0.0 0.0 0 0 ? SW 17:38 0:00 [ahd_dv_0]
root 488 0.0 0.0 0 0 ? SW 17:39 0:00 [scsi_eh_5]
root 489 0.0 0.0 0 0 ? SW 17:39 0:00 [ahd_dv_1]
root 497 0.0 0.0 0 0 ? SW 17:39 0:00 [kjournald]
root 1699 0.0 0.0 0 0 ? SW 17:39 0:00 [kjournald]
root 1700 0.0 0.0 0 0 ? SW 17:39 0:00 [kjournald]
root 1701 0.0 0.0 0 0 ? SW 17:39 0:00 [kjournald]
root 1702 0.0 0.0 0 0 ? SW 17:39 0:00 [kjournald]
root 2407 0.0 0.0 3476 656 ? S 17:39 0:00 syslogd -m 0
root 2411 0.0 0.0 2436 476 ? S 17:39 0:00 klogd -x
root 2422 0.0 0.0 2432 496 ? S 17:39 0:00 irqbalance
rpc 2433 0.0 0.0 4516 620 ? S 17:39 0:00 portmap
rpcuser 2453 0.0 0.0 4516 756 ? S 17:39 0:00 rpc.statd
root 2533 0.0 0.0 61400 2412 ? S 17:39 0:00 cupsd
root 2661 0.0 0.0 18164 1560 ? S 17:39 0:00 /usr/sbin/sshd
root 2676 0.0 0.0 7952 956 ? S 17:39 0:00 xinetd -stayalive
root 2686 0.0 0.0 3548 464 ? S 17:39 0:00 gpm -m /dev/input
root 2697 0.0 0.0 4572 700 ? S 17:39 0:00 crond
xfs 2719 0.0 0.0 11084 3268 ? S 17:39 0:00 xfs -droppriv -da
root 2729 0.0 0.0 69192 3208 ? S 17:39 0:00 smbd -D
root 2733 0.0 0.0 62996 2424 ? S 17:39 0:00 nmbd -D
root 2750 0.0 0.0 2432 560 ? SN 17:39 0:00 anacron -s
daemon 2759 0.0 0.0 4564 652 ? S 17:39 0:00 /usr/sbin/atd
root 2792 0.0 0.0 2424 356 tty1 S 17:39 0:00 /sbin/mingetty tt
root 2798 0.0 0.0 2424 356 tty2 S 17:39 0:00 /sbin/mingetty tt
root 2799 0.0 0.0 2424 356 tty3 S 17:39 0:00 /sbin/mingetty tt
root 2801 0.0 0.0 2424 356 tty4 S 17:39 0:00 /sbin/mingetty tt
root 2818 0.0 0.0 2424 356 tty5 S 17:39 0:00 /sbin/mingetty tt
root 2820 0.0 0.0 2424 356 tty6 S 17:39 0:00 /sbin/mingetty tt
root 2821 0.0 0.0 79912 2272 ? S 17:39 0:00 /usr/bin/gdm-bina
root 3011 0.0 0.0 92828 3100 ? S 17:39 0:00 /usr/bin/gdm-bina
root 3016 15.5 0.4 29596 17660 ? S 17:39 4:00 /usr/X11R6/bin/X
bepuser 3052 0.0 0.2 124268 10796 ? S 17:40 0:00 /usr/bin/gnome-se
bepuser 3099 0.0 0.0 14760 752 ? S 17:40 0:00 /usr/bin/ssh-agen
bepuser 3103 0.0 0.2 62584 8884 ? S 17:40 0:01 /usr/libexec/gcon
bepuser 3106 0.0 0.0 5092 884 ? S 17:40 0:00 /usr/bin/gnome-ke
bepuser 3108 0.0 0.0 60892 3124 ? S 17:40 0:00 /usr/libexec/bono
bepuser 3110 0.0 0.2 137604 9320 ? S 17:40 0:00 /usr/libexec/gnom
bepuser 3115 0.0 0.0 8244 1876 ? S 17:40 0:00 fam
bepuser 3194 0.0 0.0 29060 2232 ? S 17:40 0:00 xscreensaver -nos
bepuser 3218 0.0 0.1 93468 7668 ? S 17:40 0:00 /usr/bin/metacity
bepuser 3222 0.0 0.3 132636 12732 ? S 17:40 0:00 gnome-panel --sm-
bepuser 3224 0.0 0.4 163884 18592 ? S 17:40 0:01 nautilus --no-def
bepuser 3226 0.0 0.1 116444 6288 ? S 17:40 0:00 magicdev --sm-cli
bepuser 3228 0.0 0.1 124448 7500 ? S 17:40 0:00 eggcups --sm-clie
bepuser 3230 0.0 0.1 88740 4444 ? S 17:40 0:00 pam-panel-icon --
bepuser 3232 0.0 0.6 195132 24372 ? SN 17:40 0:00 /usr/bin/python /
root 3233 0.0 0.0 3448 516 ? S 17:40 0:00 /sbin/pam_timesta
bepuser 3236 0.0 0.0 47816 3480 ? S 17:40 0:00 /usr/libexec/gnom
bepuser 3267 0.0 0.0 5004 696 ? S 17:40 0:00 /usr/libexec/mapp
bepuser 3269 0.0 0.2 120484 8408 ? S 17:40 0:00 /usr/libexec/cloc
bepuser 3271 0.0 0.1 121228 7328 ? S 17:40 0:00 /usr/libexec/noti
bepuser 3273 0.0 0.2 130960 9300 ? S 17:40 0:00 /usr/libexec/mixe
bepuser 3298 0.0 0.2 125460 8928 ? S 17:40 0:00 /usr/libexec/wnck
bepuser 3328 0.1 0.2 18968 12052 ? S 17:40 0:01 Xvnc :1 -desktop
bepuser 3333 0.0 0.0 20932 1736 ? S 17:40 0:00 vncconfig -iconic
bepuser 3335 0.0 0.0 44796 1024 ? S 17:40 0:00 /bin/sh /usr/bin/
bepuser 3408 0.0 0.2 60404 9220 ? S 17:40 0:00 kdeinit: Running.
bepuser 3411 0.0 0.2 100304 9072 ? S 17:40 0:00 kdeinit: dcopserv
bepuser 3413 0.0 0.2 103324 10456 ? S 17:40 0:00 kdeinit: klaunche
bepuser 3416 0.0 0.3 120668 14496 ? S 17:40 0:00 kdeinit: kded
bepuser 3425 0.0 0.4 133252 18468 ? S 17:40 0:00 kdeinit: knotify
bepuser 3426 0.0 0.0 2416 248 ? S 17:40 0:00 kwrapper ksmserve
bepuser 3428 0.0 0.3 109008 12956 ? S 17:40 0:00 kdeinit: ksmserve
bepuser 3429 0.0 0.3 113272 15184 ? S 17:40 0:00 kdeinit: kwin
bepuser 3431 0.0 0.3 110328 13956 ? S 17:40 0:00 kdeinit: kwrited
bepuser 3433 0.0 0.3 113576 16000 ? S 17:40 0:00 kdeinit: kdesktop
bepuser 3436 0.0 0.4 125240 18496 ? S 17:40 0:00 kdeinit: kicker
bepuser 3437 0.0 0.2 63892 9708 ? S 17:40 0:00 kdeinit: kio_file
bepuser 3438 0.0 0.0 45740 852 ? S 17:40 0:00 /usr/bin/autorun
bepuser 3445 0.0 0.1 88740 4428 ? S 17:40 0:00 pam-panel-icon
bepuser 3446 0.0 0.5 193552 23236 ? SN 17:40 0:00 /usr/bin/python /
bepuser 3447 0.0 0.3 110416 13424 ? S 17:40 0:00 kdeinit: khotkeys
root 3448 0.0 0.0 3448 516 ? S 17:40 0:00 /sbin/pam_timesta
bepuser 3449 0.0 0.1 124448 7440 ? S 17:40 0:00 eggcups
bepuser 3454 0.0 0.4 117164 16912 ? S 17:45 0:00 kdeinit: konsole
bepuser 3455 0.0 0.0 45964 1476 pts/1 S 17:45 0:00 /bin/bash
root 3480 0.0 0.0 60800 1136 pts/2 S 17:48 0:00 su
root 3484 0.0 0.0 45704 1484 pts/2 S 17:48 0:00 bash
root 3510 1.3 2.7 2393840 110888 pts/2 S 17:48 0:13 /data/java/jdk1.5
root 3522 0.0 0.0 44920 516 pts/2 S 17:48 0:00 tail -f catalina.
bepuser 3619 0.0 0.3 106732 13012 ? S 17:54 0:00 /usr/bin/kdesktop
bepuser 3620 1.5 0.4 113952 20244 ? SN 17:54 0:10 /usr/bin/kslidesh
root 3622 0.0 0.1 70904 4160 ? S 17:55 0:00 smbd -D
root 3646 0.0 0.0 6632 764 ? S 18:04 0:00 in.telnetd: itdes
root 3647 0.0 0.0 26192 1408 ? S 18:04 0:00 login -- bepuser
bepuser 3648 0.0 0.0 45828 1440 pts/4 S 18:04 0:00 -bash
bepuser 3679 0.0 0.0 5300 780 pts/4 R 18:05 0:00 ps aux
[bepuser@bep bepuser]$

This is log at 6.05 PM .

Previus log was taken at 6.28 P.M

vinodkn · #12 13th May 2005, 07:26 AM

any update drivers for adaptec AIC7902W Dual channel U320 SCSI on Fedura Core 2.

Please help very critical.

AndyGreen · #13 13th May 2005, 07:32 AM

The drivers will be part of the kernel.

AFAIK you can happily install the latest FC3 kernel package on FC2 without explosions, at least, if there are explosions you can reboot back into your old kernel via grub. Apparently one should try to use the same gcc version for kernel and usermode but I don't think this can be a realistic issue: that's what the kernel APIs are for. Grab the kernel package from here and install with rpm -i

http://mirror.hiwaay.net/redhat/fedo...pdates/3/i386/

If that doesn't have what you want consider getting a development kernel, but your risk of explosions notches up a bit....

http://mirror.hiwaay.net/redhat/fedo...6/Fedora/RPMS/

If that doesn't have what you want, then you need to build a stock kernel.org kernel, verify the problem exists in that: if it does, bug bugme.osdl.org, if it doesn't bug bugzilla.redhat.com.

vinodkn · #14 13th May 2005, 07:38 AM

i need any update drivers for adaptec AIC7902W Dual channel U320 SCSI running Fedora Core 2. Kernel version is 2.6.10-1.771_FC2smp on an x86_64.

AndyGreen · #15 13th May 2005, 07:41 AM

Neither Redhat nor anybody else right now are making updated kernel packages for FC2. If your SCSI card has separate drivers (I do not know but assume not) then you need to go to the maintainer of your drivers. If it is part of the kernel, you need to take the advice above (although changing the repo path to x86_64 instead of i386), or roll your own stock kernel.