10-13-2011
As long as the drive is equal in size or larger, you can.
After you restore your partition table, linux won't know about the new partition layout yet. It needs to be told to reread it. fdisk can do that -- just fdisk /dev/sda and immediately write back the same partition layout.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
SuSE 8
Both LILO and GRUB are complaining about not being able to write to the boot sector. Is this definitely a problem with the drive or is there another possible problem? I've checked the BIOS and I don't think the problem is there....it's probably the drive.
Just another Linux user (1 Reply)
Discussion started by: HumanBeanDip
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
Pls can someone assist me with the command to be use to recover from bad sector in Openserver 5.0.4. This is because during level 0 backup the backup will hang when it gets to the bad sector.
Pls contact me
::email removed::
Thanks
Kayode (1 Reply)
Discussion started by: kayode
1 Replies
3. Solaris
I had Solaris 8 installed on a Ultra 10 machine but during a shutdown the root partition got corrupted. I have 3 other partitions on the drive (var, swap, home). Is there a way to reinstall the root partition without effecting the other partitions?
Also, when I run format from single user mode I... (4 Replies)
Discussion started by: jbestor
4 Replies
4. Solaris
I'm mirroring up a T2000. Able to metainit and metattach all partitions with the exception of root. Getting the following error:
metattach: <hostname>; c1t1d0s0; is mounted on /
I'm stumped. By the way, target 1 is the boot disk. (7 Replies)
Discussion started by: Probos
7 Replies
5. Solaris
Dear all,
I have a root partition which is 20 G in size. I have var and /tmp as seperate file systems. But this 20 G of root is not sufficeint.
I want to increase the size of the / partition.
Is there any way to increase with out down time.
my df -k output is
Filesystem ... (4 Replies)
Discussion started by: jegaraman
4 Replies
6. Solaris
I have a T1000 Sparc server that has a relatively small root partition which is 24Gb and a larger partition dedicated to /export/home that is approximately 100 Gb. We have a lot of data going to /var/audit and to /var/core/corefiles. Is there any non-destructive way to redirect files from... (4 Replies)
Discussion started by: goose25
4 Replies
7. Solaris
Hi everyone,
I got error which is "!bad user (root)" in crontab...
I tried changing password,
I checked etc/cron/cron.allow and cron.deny,
And also I checked the permissions of my files,
its(my crontab script) still not working....
Please help... (12 Replies)
Discussion started by: ijustneeda
12 Replies
8. Solaris
Hello guys,
I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Discussion started by: bhargav90
2 Replies
9. SCO
I have SCO Openserver 5.0.5
Root partition is 96% full and I would like to make it bigger. How can this be done?
1) Can I use 'dd' to backup 'root' and then backup '/u' to a third hard disk, then divvy the primary hard disk to have a larger 'root' filesystem (i.e. previous root + u)
2) ... (5 Replies)
Discussion started by: grips03
5 Replies
10. Ubuntu
Dear Concern,
I am new in ubuntu. Is root user disable in ubuntu? Also, is os partition default in ubuntu? I don't find any feature to create customize mount point to install OS.
Below is my current OS partition.
amirislam@blnidapp03:~$ df -h
Filesystem Size Used... (1 Reply)
Discussion started by: makauser
1 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)