- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Determine bad disk from syslog error message.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 04:37 AM
тАО07-18-2007 04:37 AM
I/O error: dev 08:10, sector 0
various sectors.
I need to determine exactly which disk is having problems.
/dev/cciss/c0d0p3 1008M 139M 818M 15% /
/dev/cciss/c0d0p1 463M 20M 420M 5% /boot
/dev/cciss/c0d0p5 5.9G 2.0G 3.6G 35% /home
/dev/cciss/c0d0p7 3.9G 689M 3.0G 18% /opt
none 1005M 0 1005M 0% /dev/shm
/dev/cciss/c0d0p10 2.0G 33M 1.8G 2% /tmp
/dev/cciss/c0d0p8 3.9G 1.5G 2.3G 39% /usr
/dev/cciss/c0d0p6 3.9G 87M 3.6G 3% /var
/dev/cciss/c0d0p9 2.0G 34M 1.8G 2% /var/dtv
/dev/sda5 9.8G 160M 9.1G 2% /oraback/DB2
/dev/sda3 20G 12G 7.4G 61% /oradata/DB1
HP/Compaq Proliant servers.
lspci and dmesg have not been very helpful.
fdisk -l
Disk /dev/sda: 255 heads, 63 sectors, 8855 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 3 24066 83 Linux
/dev/sda2 4 6 24097+ 83 Linux
/dev/sda3 7 2617 20972857+ 83 Linux
/dev/sda4 2618 8855 50106735 5 Extended
/dev/sda5 2618 3923 10490413+ 83 Linux
/dev/sda6 3924 4054 1052226 83 Linux
Unable to read /dev/sdb
Our standard setup involves doing hardware raid with a smart card. Seems we have a dead disk. I need to know which filesystem to run fsck on.
TIA, as always generous points for good answers.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 05:16 AM
тАО07-18-2007 05:16 AM
Re: Determine bad disk from syslog error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 08:21 AM
тАО07-18-2007 08:21 AM
Re: Determine bad disk from syslog error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 08:25 AM
тАО07-18-2007 08:25 AM
Re: Determine bad disk from syslog error message.
Seems the system is overwhelmed with I/O at the moment can't figure out why it can't read /dev/sdb when its not configured.
Other ideas welcome.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 08:25 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 09:37 AM
тАО07-18-2007 09:37 AM
Re: Determine bad disk from syslog error message.
Well, try using fdisk again, but changing the 'units' to sectors instead:
fdisk -lu /dev/sda
There is an 'sdb' in the system? Is it showing up in '/proc/scsi/scsi'?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 12:43 PM
тАО07-18-2007 12:43 PM
Re: Determine bad disk from syslog error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 12:58 PM
тАО07-18-2007 12:58 PM
Re: Determine bad disk from syslog error message.
# cat /proc/partitions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:15 PM
тАО07-18-2007 07:15 PM
Re: Determine bad disk from syslog error message.
[root@golan1 ~]# ll -u /dev/sdb*
0 brw-rw---- 1 root disk 8, 16 Jul 19 10:15 /dev/sdb
0 brw-rw---- 1 root disk 8, 17 Jul 18 16:32 /dev/sdb1
0 brw-rw---- 1 root disk 8, 21 Jul 18 16:32 /dev/sdb5
0 brw-rw---- 1 root disk 8, 22 Jul 18 16:32 /dev/sdb6
Clearly shows the major and minor number of the problem.
Shared storage is having read errors. If its bad disk on storage, we face downtime. If its just the fiber card or other local system issue, we'll fail over to the working node and correct the hardware problem.
Thannks.
I'll probably close this and hand out points very soon.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:22 PM
тАО07-18-2007 07:22 PM
Re: Determine bad disk from syslog error message.
I really like /proc/partitions
My output was not from the effected system, it was merely an example to document the case.
Thanks. I should have known that.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com