Broken Output For Fdisk -l

Home » CentOS » Broken Output For Fdisk -l
CentOS 7 Comments

Hi,

There was some problem with our system so I re-installed the server with CentOS 7. Now, when I am trying to run ‘fdisk -l’ command, it is returning a broken output.

It throws this error- “fdisk: cannot open /dev/sdc: Input/output error”.

There are valid /dev/sdd and /dev/sde devices which are mounted and they are accessible but, somehow /dev/sdc is having a problem and ‘fdisk -l’ is not returning the full output.

Below is an output of fdisk -l for reference. Any suggestion on how to fix this would be very helpful.

————————–

7 thoughts on - Broken Output For Fdisk -l

  • –rSB1WmiiKf3jmLDn3qqmgh6xV4v8IrmDf Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    Sounds like a bad drive. I would start by looking for errors in
    /var/log/messages and dmesg.

    You could check the connection cable if anyone has had the machine open.

    –rSB1WmiiKf3jmLDn3qqmgh6xV4v8IrmDf

  • So, your server had an undiagnosed problem, and now it reports read errors on /dev/sdc? Do you think those two things might be related?

  • There were no live connections.

    The problem what we had was more related to OS requirement for some software. This drive was not in a bad shape.

  • I tried to run fsck on /dev/sdc drive and here what I got.

    [root@localhost ~]# fsck /dev/sdc fsck from util-linux 2.23.2
    e2fsck 1.42.9 (28-Dec-2013)
    fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc Could this be a zero-length partition?
    [root@localhost ~]# fsck /dev/sdc1
    fsck from util-linux 2.23.2
    e2fsck 1.42.9 (28-Dec-2013)
    fsck.ext2: No such file or directory while trying to open /dev/sdc1
    Possibly non-existent device?

  • What’s in your /var/log/dmesg? (search for sdc and the nearby lines)


    Marcelo

    “¿No será acaso que esta vida moderna está teniendo más de moderna que de vida?” (Mafalda)

  • –Ddv88x3pPFU0n5WdajbpQrbcOla581QbF
    Content-Type: multipart/mixed;
    boundary=”————656A9487A336E45660969D3B”

    This is a multi-part message in MIME format.
    ————–656A9487A336E45660969D3B
    Content-Type: multipart/alternative;
    boundary=”————17F1EF41D81048DDE1196227″

    ————–17F1EF41D81048DDE1196227
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    Hi,

    what does lsblk say?

    //Zdenek

    ————–17F1EF41D81048DDE1196227

  • If your hard drive has failed physically, maybe this little guide can help you or at least give you some hope. So roll up your sleeves and get to work. Diagnosing and fixing a broken hard drive is serious business. Do take it seriously, but also try to exclude some of the more simple to fix culprits before you fork out hundreds of dollars to a so-called specialist. The more informed you are, the better. How far you go to diagnose and fix your hard drive will depend on how important the data is for you.

LEAVE A COMMENT