This is a discussion on Disksuite 4.2.1 problems within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> I am brand new to DiskSuite, but I managed to get it installed and working according to these instructions: ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am brand new to DiskSuite, but I managed to get it installed and working according to these instructions: (http://unixway.com/vm/disksuite/mirroros.html). I have been able to reboot it with both disks in place, but here is where I run into a problem: I bring it down to the OK prompt, remove disk 1 and replace it with a blank disk. Then I attempt to boot from disk 0. The following is the output I get: ******* ok boot sds-root Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args: SunOS Release 5.8 Version Generic_108528-13 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed NOTICE: /: bad dir ino 630913 at offset 0: mangled entry panic[cpu0]/thread=10408000: mod_hold_stub: Couldn't load stub module misc/strplumb 00000000104078a0 genunix:mod_hold_stub+1a8 (1, ffffffff, 10412818, 10412808, 300001d5e10, 0) %l0-3: 000000001045ead8 0000000000000000 00000300002d6ec0 0000000000000008 %l4-7: 00000000000000b0 0000000010412638 0000000000000000 0000000000000001 0000000010407950 unix:stubs_common_code+30 (0, 0, 0, 1, 10408004, 10407ffc) %l0-3: 0000000010407219 00000000104072f1 000000001f000000 0000000010435e28 %l4-7: 0000000000000000 0000000010412818 00000000000b7798 0000000000001798 0000000010407a20 genunix:main+dc (10410160, 2000, 10407ec0, 10408030, fff2, 1004ec8c) %l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000e9a %l4-7: 0000000010428c38 0000000010462360 00000000000cd4c0 0000000000000540 syncing file systems... done skipping system dump - no dump device configured rebooting... Resetting ... ******* I did a search on "NOTICE: /: bad dir ino 630913 at offset 0: mangled entry" in various forms and eventually came up with a page that mentioned two adjecent partitions were overlapping. However, I have checked the partition table and there are no problems there. After that error, when I try to boot from it again, it gives the following error: ******* ok boot sds-root Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args: Boot load failed. The file just loaded does not appear to be executable. ******* It seems that when that error occurs, something happens to the disk. I am completely lost and would appreciate any help. For anyone responding: Please be sure to read those instructions that I linked to. I know that you should not be able to boot with only half the state database replicas online. However, in those instructions, it gives a parameter that you can put in /etc/system to allow DiskSuite 4.2.1 to boot with only half the replicas online. I believe I tried an installation without this parameter, but I can't be sure at this point. Any help is greatly appreciated... and remember, I'm an extreme newbie at this, so please explain HOW to do what you are proposing. Thanks in advance! |
| |||
| On 30 Jul 2003 12:32:18 -0700, K.Rimsen <google@3113.com> wrote: > Thanks for the response. > >> Both disks? It might help if you described your layout better. >> If you only have 2 disks, how does your meta state db layout >> look? Can you post the output of "metadb"? > > I have an Ultra 60 with two internal hard drives, each 9GB capacity. I > have set up drive 0 to be the OS drive with a / partition, a swap > partition, then like 2 partitions of like 10MB each for the databases. > I can't post the output just yet, because all the drives I did this on > are trashed. I will reinstall/configure and I'll post it later on > today or tomorrow. > Did you set up the one way mirrors first and then reboot using the new metadevices before doing the metattach of the second submirror? If not, this may have caused some corruption. -- Barton Fisk Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ |
| ||||
| "K.Rimsen" wrote: > I have an Ultra 60 with two internal hard drives, each 9GB capacity. I > have set up drive 0 to be the OS drive with a / partition, a swap > partition, then like 2 partitions of like 10MB each for the databases. > I can't post the output just yet, because all the drives I did this on > are trashed. I will reinstall/configure and I'll post it later on > today or tomorrow. That's OK, I get the picture now. Rather than follow the doc you cited originally, I would suggest following the SDS docs at Sun's web site. The User's Guide has all the info you need. It is a PDF doc with the name 806-3205.pdf. Start by using the metadb command then the metaroot steps and reboot. Then the rest. > I did set that option in /etc/system. I also tried it once without the > option, but I got the same problem. Each disk has 2 slices of 10MB > each with 2 databases per slice. Do you mean you are using soft partitions? Or are you referring to the state db replicas? These don't take much space. Try a 3 MB slice for 2 replicas. > I can't get the latest patch because > I don't have a Sunsolve account... could that be it? The patch number is 108693. With 16 being the latest revision. Its hard to say if it will fix your problem but it does fix quite a few bugs so I would recommend it. -am © 2003 |