11-04-2009
What I dont get is what are you trying to copy with dd...
dd in LVM only works if you are copying an entire disk (and so keep the LVM structure integrity...) a dd of a logical volume that boots to a new disk just like that makes no sence...
Where Im puzzled is more how can you boot without lvol1?
were your root disks (in vg00) in mirror?
The (I hope) faulty disk was changed OK, what was done after? ( will greatly help to understand...)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi..
i am using sun solaris...and this is the filesystem information...
you can see th slice(swap) c0t0d0s1 is giving some absord information......and during rebooting it is asking to run fsck mnually..when i run fsck manually it is giving error incorrect starting and end header...smthing like... (1 Reply)
Discussion started by: Prafulla
1 Replies
2. Filesystems, Disks and Memory
Alright.
My neighbor kid brings me his iBook and says nothing works. He decided to move the file system to his likeness and that semed to create the problems. Now he doesn't have access rights to his home.
I have run fsck over and over again and I keep getting ** fs modified **
I have also... (0 Replies)
Discussion started by: maxwell
0 Replies
3. Solaris
Hi,
Can anybody tell me that is it the command "fsck" can be run by the root account only?
Thanks. (2 Replies)
Discussion started by: efang
2 Replies
4. UNIX for Dummies Questions & Answers
Howdie everyone...
I have a shell script RemoveFiles.sh
Inside this file, it only has two commands as below:
rm -f ../../reportToday/temp/*
rm -f ../../report/*
My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Discussion started by: cheongww
2 Replies
5. Solaris
Hello.
I have created a FS /u00/ and created a non-root login under this FS. Also, disabled direct root login. Now is it possible or worth moving this login over to the root partition or allowing mount/umount + fsck from a standard account. As I am not able to run fsck for this FS.
How to... (5 Replies)
Discussion started by: panchpan
5 Replies
6. UNIX for Dummies Questions & Answers
so i am pretty dumb when it comes to unix. but i am in the navy and the system i work on is unix based. and we have come across this problem.
COULD NOT FIX FILE SYSTEM WITH fsck -P, RUN fsck INTERACTIVELY! LOGGING IN AS root FOR MANUAL fsk, ENTER ^D WHEN FILE SYSTEM FIXED
(in bcheckrc)#
... (4 Replies)
Discussion started by: afouts
4 Replies
7. Shell Programming and Scripting
The script checks for free space stats on Oracle. If there are any tablespaces with more than 85% usage it prints the details of the tablespace. If all the tablespaces have more than 15% free space, then "All tablespaces have more than 15 pct free space" must be printed on the screen.
When I run... (2 Replies)
Discussion started by: RoshniMehta
2 Replies
8. UNIX for Dummies Questions & Answers
If i run fsck on one filesystem and fsck need to repair some things then this partition must be unmounted
correct ?
So running fsck on root file system isn't possible within same OS ? correct ?
What is the best way to do that, live cd ?
BR,
Jurif (5 Replies)
Discussion started by: jurif
5 Replies
9. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
10. Solaris
NOTICE: /: unexpected free inode 45262, run fsck(1M)
fsck: cannot open vfstab
Looks like /etc/vfstab (and a few other files has gone)
Any ideas?
Boot from cd, mount disk and recreate vfstab so that I can run fsck? (1 Reply)
Discussion started by: psychocandy
1 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)