What's in your /var/log/dmesg? (search for sdc and the nearby lines) On Thu, Jul 14, 2016 at 2:34 AM, Hersh <parikhh1 at gmail.com> wrote: > I tried to run fsck on /dev/sdc drive and here what I got. > > [root at 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 at 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? > > > On 13 July 2016 at 19:22, Hersh <parikhh1 at gmail.com> wrote: > > > 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. > > > > On 12 July 2016 at 23:03, Gordon Messmer <gordon.messmer at gmail.com> > wrote: > > > >> On 07/12/2016 09:52 AM, Hersh wrote: > >> > >>> 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". > >>> > >> > >> > >> > >> 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? > >> > >> > >> _______________________________________________ > >> CentOS mailing list > >> CentOS at centos.org > >> https://lists.centos.org/mailman/listinfo/centos > >> > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > > -- Marcelo "¿No será acaso que esta vida moderna está teniendo más de moderna que de vida?" (Mafalda)