Redhat devamlı kilitleniyor. Detayı için hangi log dosyasına bakmalıyım...

who -b  den sistemin açılışını görebilirsin  uptime da yapar aynısını

last -x  sistemin kapanışını yeniden başlatılmasını bu bilgileri verir.

/ var / log / messages dende sistem mesajlarını bulabilirsin

ben de şimdi /var/log/messages'i inceliyordum. Ama kilitlenmeyle ilgili birşey bulamadım. bir hata veya birbaşka birşey. Şimdi sizin dediğiniz diğer komutlara bakayım. Çok teşekkür ederim.

who -b    ve  last -x  komutları son sisteme girişleri son sistem bootları görüyorum. Ancak sistemin kilitlenmeden önce son verdiği mesajı göremiyorum. Yani windows olay günlüğü gibi birşey görebilirmiyim. yada sistemin neden kilitlendiğiyle ilgili nasıl bir araştırma yapabilirim. izleyeceğim yolun başlangıcı nedir acaba 🙁

log dosyalarını hepsi açık olmaya bilir.

 / etc / syslog.conf dosyanı editörle açıp içeriğine bak." # " olanlarla ilgili sistem kayıt tutmuyodur öncelikli bunları açabilirsin.

Selamlar,

#dmesg

komutunun çıktısınada bir gözatmakta fayda olabilir.

Selam Mücahid Kardeş, komutu yazdım, çıkanlardan anladığım disk hatalı.

en altta 2 satır şöyle;

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

oysa diski yeni değiştirmiştim. 🙁 Ben aşağıda çıkanlara bakıp kilitlenmenin nedeni olabilecek sadece disk hatasını gördüm. Sizin yorumunuz ne oluır acaba.

.... register #01: 00178020
.......     : max redirection entries: 0017
.......     : PRQ implemented: 1
.......     : IO APIC version: 0020
.... register #02: 02000000
.......     : arbitration: 02
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 00F 0F  1    1    0   1   0    1    1    B9
 01 000 00  1    0    0   0   0    0    0    00
 02 000 00  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 000 00  1    0    0   0   0    0    0    00
 05 000 00  1    0    0   0   0    0    0    00
 06 000 00  1    0    0   0   0    0    0    00
 07 000 00  1    0    0   0   0    0    0    00
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
 10 000 00  1    0    0   0   0    0    0    00
 11 000 00  1    0    0   0   0    0    0    00
 12 000 00  1    0    0   0   0    0    0    00
 13 000 00  1    0    0   0   0    0    0    00
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ19 -> 0:19
IRQ22 -> 0:22
IRQ23 -> 0:23
IRQ24 -> 1:0
IRQ48 -> 2:0
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2657.1465 MHz.
..... host bus clock speed is 132.1732 MHz.
cpu: 0, clocks: 259528, slice: 51905
CPU0<T0:259520,T1:207600,D:15,S:51905,C:259528>
cpu: 1, clocks: 259528, slice: 51905
cpu: 3, clocks: 259528, slice: 51905
cpu: 2, clocks: 259528, slice: 51905
CPU1<T0:259520,T1:155696,D:14,S:51905,C:259528>
CPU2<T0:259520,T1:103776,D:29,S:51905,C:259528>
CPU3<T0:259520,T1:51888,D:12,S:51905,C:259528>
checking TSC synchronization across CPUs: passed.
migration_task 0 on cpu=0
migration_task 1 on cpu=1
migration_task 2 on cpu=2
migration_task 3 on cpu=3
PCI: PCI BIOS revision 2.10 entry at 0xfaf80, last bus=5
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/24c0] at 00:1f.0
PCI->APIC IRQ transform: (B0,I29,P0) -> 16
PCI->APIC IRQ transform: (B0,I29,P1) -> 19
PCI->APIC IRQ transform: (B0,I29,P3) -> 23
PCI->APIC IRQ transform: (B0,I31,P0) -> 16
PCI->APIC IRQ transform: (B0,I31,P1) -> 17
PCI->APIC IRQ transform: (B0,I31,P1) -> 17
PCI->APIC IRQ transform: (B3,I1,P0) -> 48
PCI->APIC IRQ transform: (B4,I1,P0) -> 24
PCI->APIC IRQ transform: (B5,I1,P0) -> 22
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
speakup:  initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd
allocated 64 pages and 64 bhs reserved for the highmem bounces
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SER                                                                                        IAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
oprofile: can't get RTC I/O Ports
block: 1024 slots per queue, batch=256
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev f9
PIIX4: chipset revision 2
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD2502ABYS-50B7A1, ATA DISK drive
hdb: SAMSUNG CD-ROM SC-148C, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
blk: queue c0438b04, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c0438b04, I/O limit 4095Mb (mask 0xffffffff)
hda: 488397168 sectors (250059 MB) w/16384KiB Cache, CHS=30401/255/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
pci_hotplug: PCI Hot Plug PCI Core version: 0.4
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 214k freed
VFS: Mounted root (ext2 filesystem).
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Warning: Adapter 0 Firmware Compatible Version is KW710, but should be SA510
Warning: Adapter 0 BIOS Compatible Version is KW710, but should be SA510
Warning ! ! ! ServeRAID Version Mismatch
scsi0 : IBM PCI ServeRAID 5.10.21
  Vendor: IBM       Model: SERVERAID         Rev: 1.00
  Type:   Processor                          ANSI SCSI revision: 02
  Vendor: IBM       Model: 02R0980a S320  1  Rev: 1
  Type:   Processor                          ANSI SCSI revision: 02
Journalled Block Device driver loaded
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: ide0(3,6): orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 43474
ext3_orphan_cleanup: deleting unreferenced inode 43473
ext3_orphan_cleanup: deleting unreferenced inode 43470
EXT3-fs: ide0(3,6): 3 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 240k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:1d.7 to 64
hcd.c: ehci-hcd @ 00:1d.7, Intel Corp. 82801DB USB EHCI Controller
hcd.c: irq 23, pci mem f887a000
usb.c: new USB bus registered, assigned bus number 1
ehci-hcd.c: restricting 64bit DMA mappings to segment 0 ...
ehci-hcd.c: USB 2.0 support enabled, EHCI rev 1. 0
hub.c: USB hub found
hub.c: 4 ports detected
usb-uhci.c: $Revision: 1.275 $ time 12:50:27 Sep  4 2002
usb-uhci.c: High bandwidth mode enabled
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 16
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 19
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <[email protected]>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,6), internal journal
Adding Swap: 2996112k swap-space (priority -1)
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,7), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,8), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
parport0: PC-style at 0x378 [PCSPP]
ohci1394: pci_module_init failed
ip_tables: (C) 2000-2002 Netfilter core team
tg3.c:v1.0 (Jul 19, 2002)
divert: allocating divert_blk for eth0
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/10                                                                                        0/1000BaseT Ethernet 00:0c:76:7f:ed:cd
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[root@localhost root]#

Selçuk hocam bu cihazı ne için kullanıyorsun ?

Selçuk hocam bu cihazı ne için kullanıyorsun ?

Ertan hocam, bir muhasebe programımız var. Bu programın server olarak kullanıyoruz bunu. IBM DB2 var içinde.

Selamlar,

#dmesg

çıktısından alınan sonuca göre diskteki bazı sektörler arızalı gibi. Aşağıdaki bağlantılardan konuyu detaylı inceleyebilirsiniz.

http://www.linuxquestions.org/questions/linux-hardware-18/hdd-errors-hda-dma_intr-status%3D0x51-%7B-driveready-seekcomplete-error-%7D-480669/

http://www.linuxquestions.org/questions/linux-hardware-18/dma_intr-error%3D0x84-%7B-drive-status-error-badcrc-%7D-488121/

http://unix.derkeiler.com/Newsgroups/comp.unix.admin/2003-04/0470.html

Kolaylıklar

teşekkür ederim mücahid üstad.