Sponsored Content
Full Discussion: Bad PBR on Intel Machine
Top Forums UNIX for Dummies Questions & Answers Bad PBR on Intel Machine Post 13573 by mogfog on Friday 18th of January 2002 10:35:36 PM
Old 01-18-2002
Bad PBR on Intel Machine

Thanks LivinFree
That information in that website is really great.
I'll try some of those troubleshooting techniques.

Mogfog
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bad PBR Sig Operating System Not Found...why ?

Well i install successfully Solaris on my Second Hard disk, although i had to make it primary Master and my orignal hard disk as pirmary slave, because solaris will not let Windows on primary master. Anyway after installation when i try to boot from hard disk , it shows message bad PBR Sig ... (3 Replies)
Discussion started by: abidmalik
3 Replies

2. UNIX for Dummies Questions & Answers

Bad PBR sig

ok, i recently posted asking for a distro of unix, and someone said to try solaris, so i booted up the dvd iso installer. And after making some kind of mistake in the preperation, I couldnt retry the installer, it repeated the Warning: Bad Geometry. thing, and when i tried to just boot up into... (0 Replies)
Discussion started by: FaoX666
0 Replies

3. Solaris

PBR Bad in sun solaris 10 intel version

Hai while booting sun solaris 10 in a intel machine,its showing PBR bad and its showing disk boot failure.but the is detecting.please guide me (1 Reply)
Discussion started by: subbiahvin
1 Replies

4. Solaris

bad pbr sig

After installing Solaris 10 x86 (solaris 5 2009 update 7 ) i've been granted a “Bad PBR sig” error message on boot, making my system unbootable. any one has any solution for this problem (1 Reply)
Discussion started by: maxim42
1 Replies

5. Solaris

By loading I have received the following issue: BAD PBR SIGN.

Hi folks. By disk cloning on Solaris x86, I used a command dd. I pulled out the source and inserted the new disk. By loading I have received the following issue: BAD PBR SIGN. :( (5 Replies)
Discussion started by: wolfgang
5 Replies

6. Solaris

Solaris x86: Bad PBR sig

Hello everyone, I have a Sun x4600 (Solaris 10 x86) server.During boot up "Bad PBR sig" error comes soon after post (before GRUB). Unless the return key is pressed the server never boots up. Once the return key is pressed the boot process continues without any problem. Can you please help me... (1 Reply)
Discussion started by: pingmeback
1 Replies

7. Solaris

where can i download solaris 10 64bit for my intel machine?

where can i download solaris 10 64bit for my intel machine? i am able to find only 32bit solaris for intel machine. Please help me.. (2 Replies)
Discussion started by: chidori
2 Replies

8. Solaris

Veritas volume manager installation problem in Intel machine

i have downloaded veritas storage foundation 5.1 sp1 from veritas website. when i tried to install veritas through the installation script.. installation proceeds fine and then when it reaches Installing VRTSsfmh package - it doesnt proceed further it is stuck with this package. when i checked... (2 Replies)
Discussion started by: chidori
2 Replies

9. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
DOSFSCK(8)						       MAINTENANCE COMMANDS							DOSFSCK(8)

NAME
dosfsck - check and repair MS-DOS file systems SYNOPSIS
dosfsck|fsck.msdos|fsck.vfat [-aAflnrtvVwy] [-d path -d ...] [-u path -u ...] device DESCRIPTION
dosfsck verifies the consistency of MS-DOS file systems and optionally tries to repair them. The following file system problems can be cor- rected (in this order): - FAT contains invalid cluster numbers. Cluster is changed to EOF. - File's cluster chain contains a loop. The loop is broken. - Bad clusters (read errors). The clusters are marked bad and they are removed from files owning them. This check is optional. - Directories with a large number of bad entries (probably corrupt). The directory can be deleted. - Files . and .. are non-directories. They can be deleted or renamed. - Directories . and .. in root directory. They are deleted. - Bad file names. They can be renamed. - Duplicate directory entries. They can be deleted or renamed. - Directories with non-zero size field. Size is set to zero. - Directory . does not point to parent directory. The start pointer is adjusted. - Directory .. does not point to parent of parent directory. The start pointer is adjusted. - Start cluster number of a file is invalid. The file is truncated. - File contains bad or free clusters. The file is truncated. - File's cluster chain is longer than indicated by the size fields. The file is truncated. - Two or more files share the same cluster(s). All but one of the files are truncated. If the file being truncated is a directory file that has already been read, the file system check is restarted after truncation. - File's cluster chain is shorter than indicated by the size fields. The file is truncated. - Clusters are marked as used but are not owned by a file. They are marked as free. Additionally, the following problems are detected, but not repaired: - Invalid parameters in boot sector. - Absence of . and .. entries in non-root directories When dosfsck checks a file system, it accumulates all changes in memory and performs them only after all checks are complete. This can be disabled with the -w option. OPTIONS
-a Automatically repair the file system. No user intervention is necessary. Whenever there is more than one method to solve a problem, the least destructive approach is used. -A Use Atari variation of the MS-DOS filesystem. This is default if dosfsck is run on an Atari, then this option turns off Atari for- mat. There are some minor differences in Atari format: Some boot sector fields are interpreted slightly different, and the special FAT entries for end-of-file and bad cluster can be different. Under MS-DOS 0xfff8 is used for EOF and Atari employs 0xffff by default, but both systems recognize all values from 0xfff8...0xffff as end-of-file. MS-DOS uses only 0xfff7 for bad clusters, where on Atari values 0xfff0...0xfff7 are for this purpose (but the standard value is still 0xfff7). -d Delete the specified file. If more that one file with that name exists, the first one is deleted. -f Salvage unused cluster chains to files. By default, unused clusters are added to the free disk space except in auto mode (-a). -l List path names of files being processed. -n No-operation mode: non-interactively check for errors, but don't write anything to the filesystem. -r Interactively repair the file system. The user is asked for advice whenever there is more than one approach to fix an inconsistency. -t Mark unreadable clusters as bad. -u Try to undelete the specified file. dosfsck tries to allocate a chain of contiguous unallocated clusters beginning with the start cluster of the undeleted file. -v Verbose mode. Generates slightly more output. -V Perform a verification pass. The file system check is repeated after the first run. The second pass should never report any fixable errors. It may take considerably longer than the first pass, because the first pass may have generated long list of modifications that have to be scanned for each disk read. -w Write changes to disk immediately. -y Same as -a (automatically repair filesystem) for compatibility with other fsck tools. If -a and -r are absent, the file system is only checked, but not repaired. EXIT STATUS
0 No recoverable errors have been detected. 1 Recoverable errors have been detected or dosfsck has discovered an internal inconsistency. 2 Usage error. dosfsck did not access the file system. FILES
fsck0000.rec, fsck0001.rec, ... When recovering from a corrupted file system, dosfsck dumps recovered data into files named 'fsckNNNN.rec' in the top level direc- tory of the file system. BUGS
Does not create . and .. files where necessary. Does not remove entirely empty directories. Should give more diagnostic messages. Undelet- ing files should use a more sophisticated algorithm. AUTHORS
Werner Almesberger <werner.almesberger@lrc.di.epfl.ch> Extensions (FAT32, VFAT) by and current maintainer: Roman Hodek <roman@hodek.net> Linux December 31 1997 DOSFSCK(8)
All times are GMT -4. The time now is 06:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy