Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory How do I check 4 physical damaged on Linux hard disks? Post 302380966 by frank_rizzo on Wednesday 16th of December 2009 06:43:24 PM
Old 12-16-2009
it might take a while depending on the size of the disk. you have more options if you can write to the disk. also check out badblocks(8)
Code:
# changing blocksize may speed up things.
# make sure there are no I/O read errors
dd if=/dev/sdb of=/dev/null bs=1024k

Also keep an eye on /var/log/messages while this is running.

Last edited by Yogesh Sawant; 01-14-2011 at 01:49 PM.. Reason: added code tags
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

how to assign same mount point for file systems mounted on physical disks

We have 6 hard disks attached to the hardware. Of this 2 hard disks are of 9 GB each. Now I want combine both the same in such a way that i see a combined entry in the output of df -k . The steps I follow are 1. Create partition on hard disks (Using format partition) 2. Run newfs -v for... (6 Replies)
Discussion started by: Hitesh Shah
6 Replies

2. UNIX for Dummies Questions & Answers

monitoring the state of physical disks

Hello, I would like to know if there are commands that can be used to monitor the state of physical disks (including RAID) under AIX and SUN unix platforms? Thank you in advance. (4 Replies)
Discussion started by: VeroL
4 Replies

3. UNIX for Dummies Questions & Answers

Vertias (physical disks monitoring)

Can anyone tell me what Vertias is? Is it free? What is it used for exactly? Thank you in advance. (1 Reply)
Discussion started by: VeroL
1 Replies

4. HP-UX

determine the physical size of the hard disk

Hi is there a cmd in hpux 11 to determine the physical size of the hard disk. not bdf command. i have searched the other threads here but cant find an answer. thank you guys (4 Replies)
Discussion started by: hoffies
4 Replies

5. Solaris

6120 Array. Additional physical Disks and ZFS

Hi; I have 4 new disks in a 6120 Array attached to a SUN server running zfs. There are already two virtual disks on the array comprising of 3 disk raid 5 for each Vdisk. I need to add two more disks to each vdisk making each a 5 disk raid 5 Vdisk. If ZFS already has the original... (3 Replies)
Discussion started by: myjess
3 Replies

6. Linux

Linux Library symbolic link damaged

Hi, firstly I am not so familiar with linux and i think i have done some damage to the red hat server. It seems that now in command line I am unable to use any basic command whatsoever (ls, move, cp, bash, etc). I was trying to deploy an application and have changed the symbolic link (soft... (1 Reply)
Discussion started by: zaxx
1 Replies

7. AIX

How to determine the physical volume fo the disks

This is the report I got running the comand rptconf, but I would like to know what is the capacity of the disks installed into our server power 6 with AIX System Model: IBM,7778-23X Machine Serial Number: 1066D5A Processor Type: PowerPC_POWER6 Processor Implementation Mode: POWER 6... (6 Replies)
Discussion started by: cucosss
6 Replies

8. Red Hat

Create volume using LVM over 2 physical disks

I wanted to know how we can combine volumes over 2 physical drives. # fdisk -l Disk /dev/sda: 42.9 GB, 42949672960 bytes 255 heads, 63 sectors/track, 5221 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 ... (16 Replies)
Discussion started by: ikn3
16 Replies

9. UNIX for Dummies Questions & Answers

Problem with damaged hard drive during bootup

Hello, I have a problem with the hard drive connected to my setup. When I connect the HDD which is damaged, and try to bring up my system, I get some error messages continuously on my console saying ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 frozen ata2.01: failed command:... (4 Replies)
Discussion started by: sai2krishna
4 Replies
FSCK.MINIX(8)                                                  System Administration                                                 FSCK.MINIX(8)

NAME
fsck.minix - check consistency of Minix filesystem SYNOPSIS
fsck.minix [options] device DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem. The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ- ing to it. Remember that the kernel can write to device when it searches for files. The device name will usually have the following form: /dev/hda[1-63] IDE disk 1 /dev/hdb[1-63] IDE disk 2 /dev/sda[1-15] SCSI disk 1 /dev/sdb[1-15] SCSI disk 2 If the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before exiting. There is no need to reboot after check. WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for deletion. OPTIONS
-l, --list List all filenames. -r, --repair Perform interactive repairs. -a, --auto Perform automatic repairs. This option implies --repair and serves to answer all of the questions asked with the default. Note that this can be extremely dangerous in the case of extensive filesystem damage. -v, --verbose Be verbose. -s, --super Output super-block information. -m, --uncleared Activate MINIX-like "mode not cleared" warnings. -f, --force Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted. -V, --version Display version information and exit. -h, --help Display help text and exit. DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage. If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem, fsck.minix will print "bad magic number in super-block". EXIT CODES
The exit code returned by fsck.minix is the sum of the following: 0 No errors 3 Filesystem errors corrected, system should be rebooted if filesystem was mounted 4 Filesystem errors left uncorrected 7 Combination of exit codes 3 and 4 8 Operational error 16 Usage or syntax error AUTHORS
Linus Torvalds <torvalds@cs.helsinki.fi> Error code values by Rik Faith <faith@cs.unc.edu> Added support for filesystem valid flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>. Check to prevent fsck of mounted filesystem added by Daniel Quinlan <quinlan@yggdrasil.com>. Minix v2 fs support by Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai Langfeldt <janl@math.uio.no>. Portability patch by Russell King <rmk@ecs.soton.ac.uk>. SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8) AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux June 2015 FSCK.MINIX(8)
All times are GMT -4. The time now is 12:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy