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.
----------------------------
[root@localhost ~]# fdisk -l
Disk /dev/sda: 1932.7 GB, 1932735283200 bytes, 3774873600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0004118b
Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 3774873599 1886923776 8e Linux LVM
Disk /dev/sdb: 1664.6 GB, 1664568262656 bytes, 3251109888 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00000081
Device Boot Start End Blocks Id System /dev/sdb1 * 63 3251106179 1625553058+ 83 Linux fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]# [root@localhost ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 50G 4.8G 46G 10% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 300K 63G 1% /dev/shm tmpfs 63G 18M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/mapper/MD3200-results 19T 9.0T 9.3T 50% /data/results /dev/sdb1 1.5T 234M 1.5T 1% /share /dev/mapper/centos-home 1.8T 5.5G 1.7T 1% /home /dev/sda1 497M 158M 340M 32% /boot tmpfs 13G 32K 13G 1% /run/user/1000 tmpfs 13G 36K 13G 1% /run/user/0 /dev/sde 917G 625G 247G 72% /media/usb [root@localhost ~]# fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]#
------------------------------
Regards Hersh
On 07/12/2016 11:52 AM, Hersh wrote:
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.
[root@localhost ~]# fdisk -l
Disk /dev/sda: 1932.7 GB, 1932735283200 bytes, 3774873600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0004118b
Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 3774873599 1886923776 8e Linux LVM
Disk /dev/sdb: 1664.6 GB, 1664568262656 bytes, 3251109888 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00000081
Device Boot Start End Blocks Id System /dev/sdb1 * 63 3251106179 1625553058+ 83 Linux fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]# [root@localhost ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 50G 4.8G 46G 10% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 300K 63G 1% /dev/shm tmpfs 63G 18M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/mapper/MD3200-results 19T 9.0T 9.3T 50% /data/results /dev/sdb1 1.5T 234M 1.5T 1% /share /dev/mapper/centos-home 1.8T 5.5G 1.7T 1% /home /dev/sda1 497M 158M 340M 32% /boot tmpfs 13G 32K 13G 1% /run/user/1000 tmpfs 13G 36K 13G 1% /run/user/0 /dev/sde 917G 625G 247G 72% /media/usb [root@localhost ~]# fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]#
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.
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?
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@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@centos.org https://lists.centos.org/mailman/listinfo/centos
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?
On 13 July 2016 at 19:22, Hersh parikhh1@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@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@centos.org https://lists.centos.org/mailman/listinfo/centos
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@gmail.com wrote:
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?
On 13 July 2016 at 19:22, Hersh parikhh1@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@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@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 2016-07-14 07:34, Hersh wrote:
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?
On 13 July 2016 at 19:22, Hersh parikhh1@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@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@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hi,
what does lsblk say?
//Zdenek
-
Gordon Messmer -
Hersh -
Johnny Hughes -
Marcelo Roccasalva -
Zdenek Sedlak