07-14-2009
If your file system has failed, you are likely going to lose a good deal of data. However, you can bring the array into a degraded state by marking the bad drive(s) as failed and rerunning the fsck.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi ,
I have a filesystem on AIX 4.3.3 which i need to share with other clients who use Windows NT and Redhat linux 7.3.
I use samba to share this with Windows NT Clients.
Now i was to share this with Linux clients.
When i try to nfs mount this on Linux i get
"mount: failed, reason given by... (1 Reply)
Discussion started by: Sushesh
1 Replies
2. UNIX for Dummies Questions & Answers
I have Pentium 4 CPU with 3 GHZ
500MB of RAM w/ 120 GB of HDD space. I am trying to install Sun Solaris 9 (x86).
I saw somewhere to on-line to get Device Configuration Assistant, but I am not sure where or if you guys have any documentations on this issue.
This is the error I am getting:
... (1 Reply)
Discussion started by: vtsao
1 Replies
3. SuSE
I am having some problems with a Reiserfs partitioned drive on my Suse 9.2 server.
I run reiserfsck:-
# reiserfsck --fix-fixable /dev/hdi1
and I get:-
Partition /dev/hdi1 is mounted with write permissions, cannot check it
so I remount as Read-Only using:-
# mount -o remount,ro... (2 Replies)
Discussion started by: Mark Ward
2 Replies
4. Solaris
My Solaris10 cannot boot after I made an error when apending the vfstab to:
dev to mount======/dev/dsk/c0d0p1:1
device to fsck====== <blank>
mount pt=========/Data
FS Type==========pcfs
fsck pass=========-
mount at boot=====yes
mount options===== <blank>
My 'Data' partition is a... (3 Replies)
Discussion started by: maag
3 Replies
5. HP-UX
Hi....
I newbee to this and wanted help on hpux11 system. Disk is being replaced and need to rebuild and what r the commands I need to perform after the disk is swapped :confused:
Thanks! (1 Reply)
Discussion started by: catwomen
1 Replies
6. Red Hat
Hi There,
I have been googling for this error and try solution provided but still not avail to resolve Kickstart Issue.
Any expert have encounter this problem? Thanks.
Regards,
Regmaster (4 Replies)
Discussion started by: regmaster
4 Replies
7. AIX
I have an NFS file system mounted on one of my AIX servers with "mount -v cifs".. The server from which the file system was mounted has crashed and now my "df -g" output is hanging. Is there any was to unmount this NFS file system? I have tried "umount -f". Doesn't work.
Or is there any way in... (6 Replies)
Discussion started by: wibhore
6 Replies
8. UNIX for Dummies Questions & Answers
hi,
system operation: unix sco 3.2.4
Kernel not rebuild, do not remove or update tcp/ip e3H0 driver.
messages:
cat:cannot open../sdevice.d/5
line:5.1 32 -1
fatal error:mdevice:wrong number of fields
idmaster:device do not exist in therefore can not be update
idinstall: cannot... (0 Replies)
Discussion started by: milen
0 Replies
9. Solaris
I recently ran the Solaris 10 upgrade 10 and everything went fine. About 2 months later after rebooting and getting ready to load the latest upgrade that came out, I am getting this error.
ERROR: svc:/system/filesytem/root: default failed to mount /usr (see 'svc -x' for details)
... (6 Replies)
Discussion started by: drew_1980
6 Replies
10. Linux
I have a failed 160 GB Western Digital Netcenter NAS disk and its image after failing in .DSK format.
When I connect the disk to my ubuntu machine and typed:
# losetup -o 512006144 /dev/loop1 /dev/sdc
# mkdir /tmp/sdc
# mount -r -t reiserfs /dev/loop1 /tmp/sdc
I get my folders and... (0 Replies)
Discussion started by: jalil1408
0 Replies
BADSECT(8) System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
/sbin/badsect sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much prefer-
able to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be
copied with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad
blocks in the i-list of file systems or in swap areas.
Adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter, as UNIX does
not supply formatters. Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect
may be used to good effect.
Badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a direc-
tory BAD there and change into it. Run badsect giving as argument all the bad sectors you wish to add. (The sector numbers should be
given as physical disk sectors relative to the beginning of the file system, exactly as the system reports the sector numbers in its con-
sole error messages.) Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors
should show up in two files or in the bad sector files and the free list. Have fsck remove files containing the offending bad sectors, but
do not have it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
Badsect works by giving the specified sector numbers in a mknod(2) system call (after taking into account the filesystem's block size),
creating a regular file whose first block address is the block containing bad sector and whose name is the bad sector number. The file has
0 length, but the check programs will still consider it to contain the block containing the sector. This has the pleasant effect that the
sector is completely inaccessible to the containing file system since it is not available by accessing the file.
SEE ALSO
mknod(2), bad144(8), fsck(8)
BUGS
If both sectors which comprise a (1024 byte) disk block are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover both (bad) disk sectors.
On the PDP-11, only sector number less than 131072 may be specified on 1024-byte block filesystems, 65536 on 512-byte block filesystems.
This is because only a short int is passed to the system from mknod.
3rd Berkeley Distribution BADSECT(8)