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
Forums
Discussions
Discussions
Discussions
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
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
10-31-2001 08:09 AM
10-31-2001 08:09 AM
/dpss/hp$fsck /dev/vg01/lvol21
** /dev/vg01/lvol21
** Last Mounted on /dpss
** Phase 1 - Check Blocks and Sizes
CANNOT READ: BLK 670272
CONTINUE? y
CANNOT READ: BLK 670272
CONTINUE? y
CANNOT READ: BLK 670272
CONTINUE? y
FAILED READ OF BLOCK #670272, RETRIED 2 TIMES
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION (INODE FREE) BAD
BAD CYLINDER GROUPS
FIX? y
** Phase 6 - Salvage Cylinder Groups
90 files, 0 icont, 1135636 used, 2255489 free (121 frags, 281921 blocks)
DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.
***** FILE SYSTEM IS NOT CLEAN -- DISK MEDIA PROBLEMS ENCOUNTERED *****
***** FILE SYSTEM WAS MODIFIED *****
/home/root$dd if=/dev/vg01/lvol21 of=/dev/null bs=1024k
dd read error: I/O error
654+1 records in
654+1 records out
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2001 08:18 AM
10-31-2001 08:18 AM
Re: Bad Disk
do an lvdisplay -v /dev/vg01/lvol21 |more
and look for stale extents.
The disk corresponding to
the stale extent should be
the faulty one.
Once you identify it, do
a pvdisplay on it to make
sure it is indeed not accessible. Also check it
doing an ioscan -fnCdisk
and see whether it shows
a NO_HW corresponding to it's
path
-raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2001 08:21 AM
10-31-2001 08:21 AM
Re: Bad Disk
Have you tried "lvdisplay -v "
hope this helps.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2001 08:21 AM
10-31-2001 08:21 AM
Re: Bad Disk
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2001 08:22 AM
10-31-2001 08:22 AM
Re: Bad Disk
Two way you can check about the bad disk.
do a ioscan on the disks
ioscan -fnC disk
and run a lvdisply -v /dev/vgnn/lvolnn and look for any stale
GoodLuck,
-USA..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2001 12:37 PM
10-31-2001 12:37 PM
Re: Bad Disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2001 04:49 AM
11-01-2001 04:49 AM
SolutionThen, for each device file, do a dd(1) read test:
dd if=/dev/rdsk/... of=/dev/null bs=64k
(note rdsk, not dsk)
Probably one of these will give an I/O error. Then do a "lssf /dev/rdsk/..." to determine the hardware path, do an "ioscan -f -H ...", etc..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2001 05:46 AM
11-01-2001 05:46 AM
Re: Bad Disk
The dd using rdsk did the trick. I now have the hardware path needed. Thx.