Sponsored Content
Operating Systems Solaris ultra 10 boot warning---corrupt label Post 302219216 by itik on Monday 28th of July 2008 12:36:24 PM
Old 07-28-2008
I found the problem. The second HD which was configured previously with another filesystem, I created a newfs and the WARNING is now remove.

Case closed!
 

10 More Discussions You Might Find Interesting

1. Linux

Help! Boot failure - corrupt superblock

Hi everyone, OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here. Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies

2. Solaris

Ultra 60 won't boot

I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies

3. Solaris

Warning: No Disk Label

Hi Fellows, I am trying to mirror 2 identical disks on a SUN Ultra 10 machines (with new installation of Solaris 8). In the process, I found 2 issues: 1. prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 Result: Disk partitions between the 2 disks do not match up. 2. manually... (2 Replies)
Discussion started by: o51974
2 Replies

4. Solaris

Corrupt label bad geometry

Hi, I have a Sun X4200, when I try to reboot the machine it's not detecting the drive and it shows the following error when I try to rebuilt it. I am not sure whether its a bad HD or something else. Label says 983040 blocks: Drive says 983039 blocks WARNING:... (1 Reply)
Discussion started by: gunnervarma
1 Replies

5. Solaris

corrupt label - wrong magic number

I have created 1 LUN. 1)LUN 00BB 200GB /dev/rdsk/c1t3d44 /dev/rdsk/c2t28d44 /dev/rdsk/c3t19d44 /dev/rdsk/c4t12d44 2) Already added the new entry into sd.conf and rebooted. 3) Already done these: powercf –q power config 4) power display dev=all I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies

6. UNIX for Advanced & Expert Users

Linux on vmware won't boot due to corrupt library file!

We have an issue here: The libc.so.6 file (link) is corrupted and it causes the system unbootable. It even doesn't boot to single user mode. How can we boot the system to fix the library file? Or is there any other solutions for this issue? Here are some boot messages:... (6 Replies)
Discussion started by: aixlover
6 Replies

7. Filesystems, Disks and Memory

Original SAN to a New Solaris Server: Corrupt Label

I've seen several posts that are similar to what I'm trying to do but no dice. I have a server (SunFire V215) that went belly up. I've set up a new one. I'm getting a corrupt label: wrong magic number error. Everything I'm seeing says label the drives, but if I do I'm afraid I'll lose the data... (0 Replies)
Discussion started by: tnelson
0 Replies

8. Emergency UNIX and Linux Support

Ubuntu filesystem error corrupt GPT label

Need help/advice urgently.:wall: I really shot myself in the foot this time. Here is the scenario Have a Solaris server Solaris 10 x86 Update 8. Installed an LSI MegaRaid 9280 raid controller and attached a 16 bay JBOD box to it, created a RAID6 virtual drive with 1 hot spare. Created a... (2 Replies)
Discussion started by: ccj4467
2 Replies

9. Solaris

Ultra 45 Boot Loop

I am trying to get an old Ultra 45 to boot and it is stuck in a loop. I cannot get anything to come up on a monitor, so when I hook up a serial connection to the TTYa interface I see the following output: @(#)OBP 4.21.2 2005/12/22 17:17 Sun Ultra 45 Workstation Clearing TLBs Loading... (0 Replies)
Discussion started by: Madrox72
0 Replies

10. Solaris

Sun Ultra 30 boot problems

Hi all, I've just replaced the eprom battery on my Sun Ultra-30 and having boot issues. For some reason its trying to boot off the network instead of the DISK1. Howe can I change it so the open boot does not default to the boot device: NET Thanks, Rob (3 Replies)
Discussion started by: robbo007
3 Replies
newfs(8)						      System Manager's Manual							  newfs(8)

Name
       newfs - construct a new file system

Syntax
       /etc/newfs [ -N ] [ -n ] [ -v ] [ mkfs-options ] special disk-type

Description
       The command is a front-end to the program.  The program looks up the type of disk a file system is being created on in the disk description
       file calculates the appropriate parameters to use in calling then builds the file system by forking If the file system is a root partition,
       installs the necessary bootstrap program in the initial 16 sectors of the device.

       If there is no disk description for the specified disk type in the file, the program will use the subroutine to derive disk geometry infor-
       mation from the controlling device driver.  This functionality is provided for MSCP and SCSI disks.

Options
       -N	 Runs in no update mode.  In this mode, will not write to

       -n	 Prevents the bootstrap program from being installed.

       -v	 Instructs to print out its actions, including the parameters passed to

       Options which may be used to override default parameters passed to are:

       -s size	 The size of the file system in sectors.

       -b block-size
		 The block size of the file system in bytes.

       -f frag-size
		 The fragment size of the file system in bytes.

       -t #tracks/cylinder
       -c #cylinders/group
		 The number of cylinders per cylinder group in a file system.  The default value used is 16.

       -m free space %
		 The percentage of space reserved from normal users; the minimum free space threshold.	The default value used is 10%.

       -o optimization
		 Specifies whether the file system will optimize for space or for time.

       -r revolutions/minute
		 The speed of the disk in revolutions per minute (normally 3600).

       -S sector-size
		 The size of a sector in bytes (almost never anything but 512).

       -i number of bytes per inode
		 This specifies the density of inodes in the file system.  The default is to create an inode for each 2048 bytes  of  data  space.
		 If fewer inodes are desired, a larger number should be used; to create more inodes a smaller number should be given.

Files
       For disk geometry and file system partition information

       To actually build the file system

       For boot strapping program

See Also
       disktab(5), fs(5), chpt(8), fsck(8), format(8v), creatediskbyname(3x), mkfs(8), tunefs(8)
       "A Fast File System for UNIX", Supplementary Documents, Volume 3: System Manager

																	  newfs(8)
All times are GMT -4. The time now is 11:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy