Find the answer to your Linux question:
Results 1 to 5 of 5
my hp proliant DL185 server doesn't boot up as expected . i've managed to capture the msgs & traces dumped to console. See below end_request: I/O error, dev cciss/c0d2, sector ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2008
    Posts
    60

    Question kernel hangs


    my hp proliant DL185 server doesn't boot up as expected .

    i've managed to capture the msgs & traces dumped to console. See below

    end_request: I/O error, dev cciss/c0d2, sector 0
    end_request: I/O error, dev cciss/c0d2, sector 0
    end_request: I/O error, dev cciss/c0d2, sector 1
    ciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
    end_request: I/O error, dev cciss/c0d3, sector 0
    cciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
    end_request: I/O error, dev cciss/c0d3, sector 0
    backtrace from SysRq -w

    SysRq : Show Blocked State
    f7ad1e40 00203082 f7853b90 e54af7f0 e54af948 cba30e00 00000001 00000020
    e5ad2250 00000000 000000ff e5ad2250 00000000 00000000 00000000 7fffffff
    e55afe00 e55afd44 e55afe04 c05ab1c5 256e2000 00000000 e56e2000 00000000
    Call Trace:
    [<c05ab1c5>] schedule_timeout+0x13/0x86
    [<c05ab095>] wait_for_common+0xb9/0x103
    [<c021a4b6>] default_wake_function+0x0/0x8
    [<c0409473>] cciss_ioctl+0x6fb/0xd1e
    [<c0207852>] read_tsc+0x6/0x22
    [<c02335a6>] getnstimeofday+0x4a/0xca
    [<c023618a>] tick_dev_program_event+0x1e/0x8c
    [<c026c316>] dput+0x31/0xf7
    [<c026570c>] __link_path_walk+0x9fd/0xb2b
    [<c038442f>] blkdev_driver_ioctl+0x4b/0x5b
    [<c054420b>] igmp_rcv+0x38f/0x496
    [<c0384ad6>] blkdev_ioctl+0x697/0x6e5
    [<c054420b>] igmp_rcv+0x38f/0x496
    [<c054420b>] igmp_rcv+0x38f/0x496
    [<c027e02d>] do_open+0x1d9/0x258
    [<c027e21a>] blkdev_open+0x0/0x4d
    [<c027e23f>] blkdev_open+0x25/0x4d
    [<c025c3a5>] __dentry_open+0x13b/0x212
    [<c025c498>] nameidata_to_filp+0x1c/0x2c
    [<c02667c3>] do_filp_open+0x350/0x64d
    [<c023786c>] do_futex+0x8a/0x6ee
    [<c024feaa>] handle_mm_fault+0x4e0/0x4ea
    [<c054420b>] igmp_rcv+0x38f/0x496
    [<c027d871>] block_ioctl+0x13/0x16
    [<c027d85e>] block_ioctl+0x0/0x16
    [<c026744c>] vfs_ioctl+0x1c/0x5d
    [<c02676c6>] do_vfs_ioctl+0x239/0x247
    [<c025c203>] do_sys_open+0xae/0xb6
    [<c0267715>] sys_ioctl+0x41/0x58
    [<c0203759>] sysenter_do_call+0x12/0x25
    [<c054420b>] igmp_rcv+0x38f/0x496
    Any thoughts on what could be wrong here???

    Thanks in advance,
    David

  2. #2
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    Something is wrong with Hard disk. Check your Hard disk using tools provided by Hard disk Manufacturer.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  3. #3
    Just Joined!
    Join Date
    Jun 2008
    Posts
    60
    thanks for the reply. I suspected the hard disk because of - cciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4

    however i am out of my depth to interpret those backtraces. Is there anything in the backtrace that points out that the hard drive is the culprit indeed?

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,392
    These messages:
    end_request: I/O error, dev cciss/c0d2, sector 0
    end_request: I/O error, dev cciss/c0d2, sector 0
    end_request: I/O error, dev cciss/c0d2, sector 1
    Are a strong indication that the problem is with the disc or array. It is unable to read the beginning of the device, which is the MBR (Master Boot Record) and partition table. There is nothing in the backtrace that helps. As DC said, get and run the diagnostics from the manufacturer (HP in this case).
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  5. #5
    Just Joined!
    Join Date
    Jun 2008
    Posts
    60
    thank you.

    so,heres the scene...I am booting from a usb stick. And the raid set( 12 disks on raid 6 config) is mounted separate.

    the stick has code doing some checks before it mounts the raid set.

    Now, i deleted and recreated RAID, it boots OK at the moment, but i'm wary it may fall over again if its a hard drive issue( when it attempts to read from a bad block for example)

    How can i reproduce the earlier scenario?
    - dd if=/dev/random of=dev/cciss/c0d2
    from what you mentioned "It is unable to read the beginning of the device", the above command should fail at sector 0, is it?

    As DC said, get and run the diagnostics from the manufacturer (HP in this case).
    gavent had much success with this, tried mhdd & seatools with no luck

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •