Re: Problem booting 5.4
On Sat, 14 May 2005, rduffner wrote: > Doug White writes: > > > On Thu, 12 May 2005, Rainer Duffner wrote: > > > >> Hi, > >> > >> I installed FreeBSD5.4 on a server with a 3ware 7006-2 controller and > >> two 120GB disks as RAID1 > >> I cannot boot this install. (I get some kind of panic or endless loop, > >> but the display is re-painted so fast I cannot read it). > >> What I *can* do is insert my SuSE9.2-pro cd1, boot from that and at the > >> grub-menu say "boot from harddisk". > >> That boots FreeBSD. > >> > >> On advice from IRC, I tried: > >> # boot0cfg -B twed0 > >> > >> -which leads to this output > >> > >> boot0cfg: write_mbr: /dev/twed0: No such file or directory > > > > This is a erroneous message. The actual problem is: > > > >484 boot0cfg NAMI "/dev/twed0" > >484 boot0cfg RET open -1 errno 1 Operation not permitted > > > > This is a known problem with certain MBR layouts. To work around this > > problem, set: > > > > sysctl kern.geom.debugflags=16 > > > > then try your boot0cfg. There's a protection mechanism that sometimes gets > > confused by certain partition table layouts. Flag 16 disables that > > protection. I don't recommend running this unless you are explicitly > > trying to updating something in a partition table-like area; its very easy > > to destroy your system with the flag set! > > > I booted from CD and ran the boot0cfg "offline" - however, this worked only > on one server. I have two more identical servers that now just beep > endlessly at the F1-prompt. > I was told it is a geometry problem, but what else can I do? boot0cfg -o packet adX -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting 5.4
Doug White writes: On Thu, 12 May 2005, Rainer Duffner wrote: Hi, I installed FreeBSD5.4 on a server with a 3ware 7006-2 controller and two 120GB disks as RAID1 I cannot boot this install. (I get some kind of panic or endless loop, but the display is re-painted so fast I cannot read it). What I *can* do is insert my SuSE9.2-pro cd1, boot from that and at the grub-menu say "boot from harddisk". That boots FreeBSD. On advice from IRC, I tried: # boot0cfg -B twed0 -which leads to this output boot0cfg: write_mbr: /dev/twed0: No such file or directory This is a erroneous message. The actual problem is: 484 boot0cfg NAMI "/dev/twed0" 484 boot0cfg RET open -1 errno 1 Operation not permitted This is a known problem with certain MBR layouts. To work around this problem, set: sysctl kern.geom.debugflags=16 then try your boot0cfg. There's a protection mechanism that sometimes gets confused by certain partition table layouts. Flag 16 disables that protection. I don't recommend running this unless you are explicitly trying to updating something in a partition table-like area; its very easy to destroy your system with the flag set! I booted from CD and ran the boot0cfg "offline" - however, this worked only on one server. I have two more identical servers that now just beep endlessly at the F1-prompt. I was told it is a geometry problem, but what else can I do? cheers, Rainer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting 5.4
On Thu, 12 May 2005, Rainer Duffner wrote: > Hi, > > I installed FreeBSD5.4 on a server with a 3ware 7006-2 controller and > two 120GB disks as RAID1 > I cannot boot this install. (I get some kind of panic or endless loop, > but the display is re-painted so fast I cannot read it). > What I *can* do is insert my SuSE9.2-pro cd1, boot from that and at the > grub-menu say "boot from harddisk". > That boots FreeBSD. > > On advice from IRC, I tried: > # boot0cfg -B twed0 > > -which leads to this output > > boot0cfg: write_mbr: /dev/twed0: No such file or directory This is a erroneous message. The actual problem is: 484 boot0cfg NAMI "/dev/twed0" 484 boot0cfg RET open -1 errno 1 Operation not permitted This is a known problem with certain MBR layouts. To work around this problem, set: sysctl kern.geom.debugflags=16 then try your boot0cfg. There's a protection mechanism that sometimes gets confused by certain partition table layouts. Flag 16 disables that protection. I don't recommend running this unless you are explicitly trying to updating something in a partition table-like area; its very easy to destroy your system with the flag set! -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem booting 5.4
Hi, I installed FreeBSD5.4 on a server with a 3ware 7006-2 controller and two 120GB disks as RAID1 I cannot boot this install. (I get some kind of panic or endless loop, but the display is re-painted so fast I cannot read it). What I *can* do is insert my SuSE9.2-pro cd1, boot from that and at the grub-menu say "boot from harddisk". That boots FreeBSD. On advice from IRC, I tried: # boot0cfg -B twed0 -which leads to this output boot0cfg: write_mbr: /dev/twed0: No such file or directory Of course, the device is there: # ll /dev/tw* crw--- 1 root operator 240, 0 May 12 18:15 /dev/twe0 crw-r- 1 root operator4, 12 May 12 18:15 /dev/twed0 crw-r- 1 root operator4, 14 May 12 18:15 /dev/twed0s1 crw-r- 1 root operator4, 15 May 12 20:15 /dev/twed0s1a crw-r- 1 root operator4, 16 May 12 18:15 /dev/twed0s1b crw-r- 1 root operator4, 17 May 12 18:15 /dev/twed0s1c crw-r- 1 root operator4, 18 May 12 20:15 /dev/twed0s1d crw-r- 1 root operator4, 19 May 12 20:15 /dev/twed0s1e crw-r- 1 root operator4, 20 May 12 20:15 /dev/twed0s1f I tried ktrace'ing it, and got that: ... 484 boot0cfg RET read 4096/0x1000 484 boot0cfg CALL mmap(0,0xda000,0x5,0x20002,0x3,0,0,0) 484 boot0cfg RET mmap 671576064/0x28077000 484 boot0cfg CALL mprotect(0x28137000,0x1000,0x7) 484 boot0cfg RET mprotect 0 484 boot0cfg CALL mprotect(0x28137000,0x1000,0x5) 484 boot0cfg RET mprotect 0 484 boot0cfg CALL mmap(0x28138000,0x5000,0x3,0x12,0x3,0,0xc,0) 484 boot0cfg RET mmap 672366592/0x28138000 484 boot0cfg CALL mmap(0x2813d000,0x14000,0x3,0x1012,0x,0,0,0) 484 boot0cfg RET mmap 672387072/0x2813d000 484 boot0cfg CALL close(0x3) 484 boot0cfg RET close 0 484 boot0cfg CALL mmap(0,0x158,0x3,0x1000,0x,0,0,0) 484 boot0cfg RET mmap 672468992/0x28151000 484 boot0cfg CALL munmap(0x28151000,0x158) 484 boot0cfg RET munmap 0 484 boot0cfg CALL mprotect(0x28077000,0xc1000,0x7) 484 boot0cfg RET mprotect 0 484 boot0cfg CALL mmap(0,0x5608,0x3,0x1000,0x,0,0,0) 484 boot0cfg RET mmap 672468992/0x28151000 484 boot0cfg CALL munmap(0x28151000,0x5608) 484 boot0cfg RET munmap 0 484 boot0cfg CALL mprotect(0x28077000,0xc1000,0x5) 484 boot0cfg RET mprotect 0 484 boot0cfg CALL sigaction(0x4,0xbfbfebb8,0xbfbfeb98) 484 boot0cfg RET sigaction 0 484 boot0cfg CALL sigprocmask(0x1,0,0x2806aafc) 484 boot0cfg RET sigprocmask 0 484 boot0cfg CALL sigaction(0x4,0xbfbfeb98,0) 484 boot0cfg RET sigaction 0 484 boot0cfg CALL sysarch(0x1,0xbfbfebc8) 484 boot0cfg RET sysarch 17/0x11 484 boot0cfg CALL sigprocmask(0x1,0x2806aaa0,0xbfbfebc8) 484 boot0cfg RET sigprocmask 0 484 boot0cfg CALL sigprocmask(0x3,0x2806aab0,0) 484 boot0cfg RET sigprocmask 0 484 boot0cfg CALL readlink(0x2813105b,0xbfbfe700,0x3f) 484 boot0cfg NAMI "/etc/malloc.conf" 484 boot0cfg RET readlink -1 errno 2 No such file or directory 484 boot0cfg CALL issetugid 484 boot0cfg RET issetugid 0 484 boot0cfg CALL mmap(0,0x1000,0x3,0x1002,0x,0,0,0) 484 boot0cfg RET mmap 672468992/0x28151000 484 boot0cfg CALL break(0x804c000) 484 boot0cfg RET break 0 484 boot0cfg CALL break(0x804d000) 484 boot0cfg RET break 0 484 boot0cfg CALL open(0x804c030,0,0) 484 boot0cfg NAMI "/dev/twed0" 484 boot0cfg RET open 3 484 boot0cfg CALL read(0x3,0xbfbfe9f0,0x200) 484 boot0cfg GIO fd 3 read 512 bytes 0x fc31 c08e c08e d88e d0bc 007c be1a 7cbf 1a06 b9e6 01f3 a4e9 008a 31f6 bbbe 07b1 0438 2f74 087f |.1.|..|...1..8/t..| 0x0026 7585 f675 7189 de80 c310 e2ef 85f6 7502 cd18 80fa 8072 0b8a 3675 0480 c680 38f2 7202 8a14 89e7 |u..uq.u..r..6u8.r.| 0x004c 8a74 018b 4c02 bb00 7cf6 06bd 0780 742d 5153 bbaa 55b4 41cd 1372 2081 fb55 aa75 1af6 c101 7415 |.t..L...|.t-QS..U.A..r ..U.ut.| 0x0072 5b66 6a00 66ff 7408 0653 6a01 6a10 89e6 b800 42eb 055b 59b8 0102 cd13 89fc 720f 81bf fe01 55aa |[fj.f.t..Sj.j.B..[Y...r.U.| 0x0098 750c ffe3 beb9 06eb 11be d106 eb0c bef0 06eb 07bb 0700 b40e cd10 ac84 c075 f4eb fe49 6e76 616c |uu...Inval| 0x00be 6964 2070 6172 7469 7469 6f6e 2074 6162 6c65 0045 7272 6f72 206c 6f61 6469 6e67 206f 7065 7261 |id partition table.Error loading opera| 0x00e4 7469 6e67 2073 7973 7465 6d00 4d69 7373 696e 6720 6f70 6572 6174 696e 6720 7379 7374 656d 0090 |ting system.Missing operating system..| 0x010a 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 |..| 0x0130 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 |..| 0x0156 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 9090 |
