December 8, 200718 yr Hi all, I've been trying to add a new hard drive into the mix and I keep getting this error that comes up on the console screen. It happens after the clearing has started. This is very similar to other errors that I have encountered every now and then. After the error comes up, it's impossible to restart the server using commands that I am familiar with (reboot, halt, etc.) Issuing the reboot command causes a broadcast message about how the server is going down... but nothing ever happens after that. Anyway... attached is the snip of the syslog (if I can get the attachements working). Nope attachements still don't work... so here it is... Dec 8 18:03:22 Tower emhttp[1073]: clearing disk7 ... Dec 8 18:03:23 Tower kernel: [ 102.566538] md7: new disk Dec 8 18:03:26 Tower kernel: [ 105.458971] md7: new disk Dec 8 18:04:02 Tower emhttp[1073]: ... clearing 1% complete Dec 8 18:04:43 Tower emhttp[1073]: ... clearing 2% complete Dec 8 18:05:24 Tower emhttp[1073]: ... clearing 3% complete Dec 8 18:06:07 Tower emhttp[1073]: ... clearing 4% complete Dec 8 18:06:52 Tower emhttp[1073]: ... clearing 5% complete Dec 8 18:07:33 Tower emhttp[1073]: ... clearing 6% complete Dec 8 18:08:02 Tower kernel: [ 380.765203] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 Dec 8 18:08:02 Tower kernel: [ 380.765346] printing eip: Dec 8 18:08:02 Tower kernel: [ 380.765413] c0160240 Dec 8 18:08:02 Tower kernel: [ 380.765415] *pde = 00000000 Dec 8 18:08:02 Tower kernel: [ 380.765483] Oops: 0000 [#1] Dec 8 18:08:02 Tower kernel: [ 380.765549] Modules linked in: md_mod fuse ata_piix sata_promise tg3 libata piix ide_core Dec 8 18:08:02 Tower kernel: [ 380.766111] CPU: 0 Dec 8 18:08:02 Tower kernel: [ 380.766112] EIP: 0060:[<c0160240>] Not tainted VLI Dec 8 18:08:02 Tower kernel: [ 380.766113] EFLAGS: 00210283 (2.6.22.5 #9) Dec 8 18:08:02 Tower kernel: [ 380.766349] EIP is at __block_write_full_page+0xc1/0x2bc Dec 8 18:08:02 Tower kernel: [ 380.766419] eax: 00000000 ebx: 00000000 ecx: 00000003 edx: 00000000 Dec 8 18:08:02 Tower kernel: [ 380.766492] esi: 027c9978 edi: 00000000 ebp: c1236f00 esp: df8ddb54 Dec 8 18:08:02 Tower kernel: [ 380.766564] ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068 Dec 8 18:08:02 Tower kernel: [ 380.766636] Process emhttp (pid: 1148, ti=df8dc000 task=de355ab0 task.ti=df8dc000) Dec 8 18:08:02 Tower kernel: [ 380.766709] Stack: df8ddbfc e01d91f0 00000000 004f9329 00000000 00000200 c0ff4390 2542ea70 Dec 8 18:08:02 Tower kernel: [ 380.767078] 00000000 00000000 c0163065 df9e10a8 0000004a c1236f00 00000005 df9e10a8 Dec 8 18:08:02 Tower kernel: [ 380.767446] c01618dd df8ddd24 00000000 df8ddbf0 df8ddd24 c0163065 df9e1140 0000000e Dec 8 18:08:02 Tower kernel: [ 380.767814] Call Trace: Dec 8 18:08:02 Tower kernel: [ 380.767943] [<c0163065>] blkdev_get_block+0x0/0x45 Dec 8 18:08:02 Tower kernel: [ 380.768045] [<c01618dd>] block_write_full_page+0xc8/0xd0 Dec 8 18:08:02 Tower kernel: [ 380.768146] [<c0163065>] blkdev_get_block+0x0/0x45 Dec 8 18:08:02 Tower kernel: [ 380.768246] [<c0134019>] __writepage+0x8/0x1f Dec 8 18:08:02 Tower kernel: [ 380.768345] [<c0133efb>] write_cache_pages+0x16e/0x284 Dec 8 18:08:02 Tower kernel: [ 380.768445] [<c0134011>] __writepage+0x0/0x1f Dec 8 18:08:02 Tower kernel: [ 380.768544] [<c0134030>] generic_writepages+0x0/0x24 Dec 8 18:08:02 Tower kernel: [ 380.768644] [<c013404d>] generic_writepages+0x1d/0x24 Dec 8 18:08:02 Tower kernel: [ 380.768743] [<c0134074>] do_writepages+0x20/0x30 Dec 8 18:08:02 Tower kernel: [ 380.768842] [<c015c5c1>] __sync_single_inode+0x51/0x196 Dec 8 18:08:02 Tower kernel: [ 380.768943] [<c015c83d>] __writeback_single_inode+0x137/0x13f Dec 8 18:08:02 Tower kernel: [ 380.769045] [<c01449a2>] cache_alloc_refill+0xc6/0x175 Dec 8 18:08:02 Tower kernel: [ 380.769147] [<c0161e10>] alloc_buffer_head+0x27/0x2b Dec 8 18:08:02 Tower kernel: [ 380.769247] [<c015c9ad>] sync_sb_inodes+0x168/0x1fd Dec 8 18:08:02 Tower kernel: [ 380.769347] [<c015ca85>] writeback_inodes+0x43/0x64 Dec 8 18:08:02 Tower kernel: [ 380.769448] [<c01339bf>] balance_dirty_pages+0x8e/0x132 Dec 8 18:08:02 Tower kernel: [ 380.769550] [<c0131041>] generic_file_buffered_write+0x4a7/0x57b Dec 8 18:08:02 Tower kernel: [ 380.769654] [<c01561c6>] file_update_time+0x26/0x8b Dec 8 18:08:02 Tower kernel: [ 380.769755] [<c013155f>] __generic_file_aio_write_nolock+0x44a/0x474 Dec 8 18:08:02 Tower kernel: [ 380.769860] [<c023b8b4>] sd_rw_intr+0x1fb/0x203 Dec 8 18:08:02 Tower kernel: [ 380.769961] [<c01315d4>] generic_file_aio_write_nolock+0x4b/0x9e Dec 8 18:08:02 Tower kernel: [ 380.770062] [<f8862a25>] ata_scsi_qc_complete+0x111/0x11d [libata] Dec 8 18:08:02 Tower kernel: [ 380.770179] [<c0146fed>] do_sync_write+0xbe/0xfb Dec 8 18:08:02 Tower kernel: [ 380.770279] [<f881a64f>] pdc_interrupt+0x17d/0x1b1 [sata_promise] Dec 8 18:08:02 Tower kernel: [ 380.770383] [<c02371af>] scsi_softirq_done+0xbc/0xc3 Dec 8 18:08:02 Tower kernel: [ 380.770485] [<c01215b2>] autoremove_wake_function+0x0/0x33 Dec 8 18:08:02 Tower kernel: [ 380.770588] [<c0103c0b>] common_interrupt+0x23/0x28 Dec 8 18:08:02 Tower kernel: [ 380.770689] [<c01470b5>] vfs_write+0x8b/0x106 Dec 8 18:08:02 Tower kernel: [ 380.770788] [<c01471d8>] sys_write+0x41/0x67 Dec 8 18:08:02 Tower kernel: [ 380.770886] [<c0103a62>] syscall_call+0x7/0xb Dec 8 18:08:02 Tower kernel: [ 380.770986] ======================= Dec 8 18:08:02 Tower kernel: [ 380.771053] Code: 0f 45 f2 f6 c4 08 75 04 0f 0b eb fe 8b 5d 0c 89 5c 24 18 3b 7c 24 20 72 12 77 06 3b 74 24 1c 76 0a 0f ba 33 01 0f ba 2b 00 eb 79 <8b> 03 a8 20 75 73 8b 03 a8 02 74 6d 8b 44 24 14 39 43 14 74 29 Dec 8 18:08:02 Tower kernel: [ 380.773090] EIP: [<c0160240>] __block_write_full_page+0xc1/0x2bc SS:ESP 0068:df8ddb54
December 8, 200718 yr Author well.. ok.... it appears that I have some bad ram. I decided to run the memtest and almost immediately the bottom of the screen filled up with a red-background and a bunch of errors. That's bad right Well.. off to the store tomorrow then.
Archived
This topic is now archived and is closed to further replies.