Re: non-root user can not create zfs filesystem?
This patch must be used in CURRENT?? cvsup src with tag=. put and upzip the patch to /usr/src usepatch zfs_20080727.patch to patch the file? Is it right? I have done following what I said,but find a few file in /usr/src -rw-r--r--1 root wheel 4166 Oct 23 13:37 sha256.c -rw-r--r--1 root wheel0 Oct 23 13:37 sha256.c.orig drwxr-xr-x 24 root wheel 26 Oct 23 12:25 share -rw-r--r--1 root wheel11391 Oct 23 13:37 spare.t -rw-r--r--1 root wheel10335 Oct 23 13:37 spare.t.orig drwxr-xr-x 56 root wheel 57 Oct 23 13:08 sys drwxr-xr-x 12 root wheel 15 Oct 12 10:48 tools -rw-r--r--1 root wheel55965 Oct 23 13:37 u8_textprep.c -rw-r--r--1 root wheel0 Oct 23 13:37 u8_textprep.c.orig drwxr-xr-x 228 root wheel 230 Oct 23 13:11 usr.bin drwxr-xr-x 195 root wheel 197 Oct 23 13:11 usr.sbin -rw-r--r--1 root wheel11075 Oct 23 13:37 zfs.c -rw-r--r--1 root wheel0 Oct 23 13:37 zfs.c.orig -rw-r--r--1 lhm wheel 4548386 Oct 23 13:27 zfs_20080727.patch -rw-r--r--1 root wheel19599 Oct 23 13:37 zfsboot.c -rw-r--r--1 root wheel0 Oct 23 13:37 zfsboot.c.orig -rw-r--r--1 root wheel31739 Oct 23 13:37 zfsimpl.c -rw-r--r--1 root wheel0 Oct 23 13:37 zfsimpl.c.orig -rw-r--r--1 root wheel39098 Oct 23 13:37 zfsimpl.h -rw-r--r--1 root wheel0 Oct 23 13:37 zfsimpl.h.orig -rw-r--r--1 root wheel12492 Oct 23 13:37 zfsldr.S -rw-r--r--1 root wheel0 Oct 23 13:37 zfsldr.S.orig -rw-r--r--1 root wheel 5531 Oct 23 13:37 zfssubr.c -rw-r--r--1 root wheel0 Oct 23 13:37 zfssubr.c.orig Is this correct?? 2008/10/23 Andrew Snow [EMAIL PROTECTED]: lhmwzy wrote: where is the patch? I can't find it in freebsd-fs@ and [EMAIL PROTECTED] http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.4 RC1 locks up solid on first reboot
On Thu, Oct 23, 2008 at 06:27:45AM +0200, Milan Obuch wrote: On Thursday 23 October 2008 01:32:27 Jo Rhett wrote: I haven't had time to investigate, but after installing 6.4RC1 on a machine I've been using with 6.3 for a few months, it installs painlessly but on the first and subsequent reboots you see BTX Loader 1.00 blah blah blah ... Loading /boot/defaults/loader.con \ At this point you have a hard refreeze -- no keyboard control, however I can reboot it from the Phantom card. System: Rackable C2004, dual Intel 2.66 processors, 4gb RAM, disk drive on built in SCSI port Absolutely nothing special, boots and runs 6.2 and 6.3 without a flaw. I'll have more time to investigate on Friday. Anything specific that would be more or less useful to debug in particular? I did not investigate on this issue too much, but there is an workaround - copy older /boot/loader over newer one. In my case, I am rebuilding whole world often, and now /boot/loader seems to not build correctly for me. Older one is ~ 250 kB, rebuilt will be ~ 185 kB, and freezes. In your case, you would write old /boot/loader from 6.3 over new installed with 6.4RC1 and it will boot normally again. I know it is only workaround, but it's quick and easy, and I have not too much time to investigate any further (not to mention I have no idea what to look for and where). Has anyone filed a PR on this problem, or contacted John Baldwin? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-root user can not create zfs filesystem?
On Thu, Oct 23, 2008 at 02:23:14PM +0800, lhmwzy wrote: This patch must be used in CURRENT?? Correct. This patch DOES NOT apply to RELENG_7 or earlier. cvsup src with tag=. Consider using csup, which comes with the base system. put and upzip the patch to /usr/src usepatch zfs_20080727.patch to patch the file? Is it right? I have done following what I said,but find a few file in /usr/src This looks correct. The .orig files are the originals. Ones which are zero bytes imply new files have been added. What you want to look for is .rej files, which are rejects (implying the patch did not apply cleanly). find /usr/src -name *.rej -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-root user can not create zfs filesystem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 lhmwzy wrote: This patch must be used in CURRENT?? cvsup src with tag=. put and upzip the patch to /usr/src usepatch zfs_20080727.patch to patch the file? Is it right? [...] No. Current has been progressed too much for this patch to apply. Cheers, -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkAGSQACgkQi+vbBBjt66CJIgCfQwnKSJZc/QeyjvW3J8pBoZyv LKkAnRx1B8MdXNYwWjj9oas9NgXI0vtk =qSC2 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-root user can not create zfs filesystem?
What's you mean? This patch is not suit for Current or Current has alreday have this patch? 2008/10/23 Xin LI [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 lhmwzy wrote: This patch must be used in CURRENT?? cvsup src with tag=. put and upzip the patch to /usr/src usepatch zfs_20080727.patch to patch the file? Is it right? [...] No. Current has been progressed too much for this patch to apply. Cheers, -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkAGSQACgkQi+vbBBjt66CJIgCfQwnKSJZc/QeyjvW3J8pBoZyv LKkAnRx1B8MdXNYwWjj9oas9NgXI0vtk =qSC2 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.4 RC1 locks up solid on first reboot
Jeremy Chadwick wrote: On Thu, Oct 23, 2008 at 06:27:45AM +0200, Milan Obuch wrote: I did not investigate on this issue too much, but there is an workaround - copy older /boot/loader over newer one. In my case, I am rebuilding whole I have experienced loader troubles in the past when using customized compiler options in /etc/make.conf . Rebuilding without compiler options fixed the issue. Joe Koberg joe at osoft dot us ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-root user can not create zfs filesystem?
On Thu, Oct 23, 2008 at 02:35:24PM +0800, lhmwzy wrote: What's you mean? This patch is not suit for Current or Current has alreday have this patch? The patch was made against CURRENT's code dated August 27th. There have been too many changes to CURRENT between August 27th and now for the patch to apply cleanly/correctly. Finally, this thread has gone from talking about user-error when creating a ZFS pool to how to patch CURRENT to present-day ZFS code. This is NOT the correct mailing list for CURRENT items. Please start a new thread on the freebsd-current mailing list instead. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: non-root user can not create zfs filesystem?
OK.close this thread.:) 2008/10/23 Jeremy Chadwick [EMAIL PROTECTED]: On Thu, Oct 23, 2008 at 02:35:24PM +0800, lhmwzy wrote: What's you mean? This patch is not suit for Current or Current has alreday have this patch? The patch was made against CURRENT's code dated August 27th. There have been too many changes to CURRENT between August 27th and now for the patch to apply cleanly/correctly. Finally, this thread has gone from talking about user-error when creating a ZFS pool to how to patch CURRENT to present-day ZFS code. This is NOT the correct mailing list for CURRENT items. Please start a new thread on the freebsd-current mailing list instead. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
gstat information on the CLI
Hello, Its me again bothering you with basic things I cant accomplish. I am planning on monitoring my disks, and the most important information for me is thorughput and lengh queue of operations. I can get the first information with iostat -w1 and sorta, which is perfect for scripting. However, I also need the L(q) information which FreeBSD gives me with gstat. However, this curses interface wont allow me to use grep+awk to get the information I need for the device (slices and disks, but not labels) I need. So I ask, how can I get this information other than gstat? Or, can gstat work in non-interactive mode? -- === Eduardo Meyer pessoal: [EMAIL PROTECTED] profissional: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gstat information on the CLI
On Thu, Oct 23, 2008 at 12:20:45PM -0200, Eduardo Meyer wrote: Hello, Its me again bothering you with basic things I cant accomplish. I am planning on monitoring my disks, and the most important information for me is thorughput and lengh queue of operations. I can get the first information with iostat -w1 and sorta, which is perfect for scripting. However, I also need the L(q) information which FreeBSD gives me with gstat. However, this curses interface wont allow me to use grep+awk to get the information I need for the device (slices and disks, but not labels) I need. Can you tell me what the L(q) field actually represents in gstat? The BUGS section of the gstat man page should indirectly answer your other question (re: non-curses). So I ask, how can I get this information other than gstat? Or, can gstat work in non-interactive mode? iostat -x should provide what you're looking for. And remember, the first sample data shown in iostat should be generally discarded. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gstat information on the CLI
On Thu, Oct 23, 2008 at 12:50 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Oct 23, 2008 at 12:20:45PM -0200, Eduardo Meyer wrote: Hello, Its me again bothering you with basic things I cant accomplish. I am planning on monitoring my disks, and the most important information for me is thorughput and lengh queue of operations. I can get the first information with iostat -w1 and sorta, which is perfect for scripting. However, I also need the L(q) information which FreeBSD gives me with gstat. However, this curses interface wont allow me to use grep+awk to get the information I need for the device (slices and disks, but not labels) I need. Can you tell me what the L(q) field actually represents in gstat? The BUGS section of the gstat man page should indirectly answer your other question (re: non-curses). Yes, I have read that. I am looking the source code for gstat. Its simple, small and clear. I guess can be asily modified to have what I want :) So I ask, how can I get this information other than gstat? Or, can gstat work in non-interactive mode? iostat -x should provide what you're looking for. And remember, the first sample data shown in iostat should be generally discarded. I need the queue lengh of pending disk operations. What L(q) shows is the lengh queue, the queued number of pending operations (I believe). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | -- === Eduardo Meyer pessoal: [EMAIL PROTECTED] profissional: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gstat information on the CLI
On Thu, Oct 23, 2008 at 01:11:55PM -0200, Eduardo Meyer wrote: On Thu, Oct 23, 2008 at 12:50 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Oct 23, 2008 at 12:20:45PM -0200, Eduardo Meyer wrote: Hello, Its me again bothering you with basic things I cant accomplish. I am planning on monitoring my disks, and the most important information for me is thorughput and lengh queue of operations. I can get the first information with iostat -w1 and sorta, which is perfect for scripting. However, I also need the L(q) information which FreeBSD gives me with gstat. However, this curses interface wont allow me to use grep+awk to get the information I need for the device (slices and disks, but not labels) I need. Can you tell me what the L(q) field actually represents in gstat? The BUGS section of the gstat man page should indirectly answer your other question (re: non-curses). Yes, I have read that. I am looking the source code for gstat. Its simple, small and clear. I guess can be asily modified to have what I want :) So I ask, how can I get this information other than gstat? Or, can gstat work in non-interactive mode? iostat -x should provide what you're looking for. And remember, the first sample data shown in iostat should be generally discarded. I need the queue lengh of pending disk operations. What L(q) shows is the lengh queue, the queued number of pending operations (I believe). It isn't documented, so I really have no idea what it means, hence my question. I'm curious why you're interested in that number; why does it matter? iostat -x provides the same kind of value, and you won't have to modify any code to get what you need: waittransactions queue length -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gstat information on the CLI
On Thu, Oct 23, 2008 at 1:52 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Oct 23, 2008 at 01:11:55PM -0200, Eduardo Meyer wrote: On Thu, Oct 23, 2008 at 12:50 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Oct 23, 2008 at 12:20:45PM -0200, Eduardo Meyer wrote: Hello, Its me again bothering you with basic things I cant accomplish. I am planning on monitoring my disks, and the most important information for me is thorughput and lengh queue of operations. I can get the first information with iostat -w1 and sorta, which is perfect for scripting. However, I also need the L(q) information which FreeBSD gives me with gstat. However, this curses interface wont allow me to use grep+awk to get the information I need for the device (slices and disks, but not labels) I need. Can you tell me what the L(q) field actually represents in gstat? The BUGS section of the gstat man page should indirectly answer your other question (re: non-curses). Yes, I have read that. I am looking the source code for gstat. Its simple, small and clear. I guess can be asily modified to have what I want :) So I ask, how can I get this information other than gstat? Or, can gstat work in non-interactive mode? iostat -x should provide what you're looking for. And remember, the first sample data shown in iostat should be generally discarded. I need the queue lengh of pending disk operations. What L(q) shows is the lengh queue, the queued number of pending operations (I believe). It isn't documented, so I really have no idea what it means, hence my question. I'm curious why you're interested in that number; why does it matter? iostat -x provides the same kind of value, and you won't have to modify any code to get what you need: waittransactions queue length Jeremy, thank you. They show the same information, reading the code I see both show DSM_QUEUE_LENGHT from devstat_compute_statistics(). Thanks again :) -- === Eduardo Meyer pessoal: [EMAIL PROTECTED] profissional: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Promise SX4060 on 7.1-BETA2
I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise SX4060 RAID controller and two Seagate 120GB ATA disk drives. The boot from CD keeps repeating the following (error) messages: (I'm retyping here) == ad4: WARNING - SETFEATURES SET TRANSFER MODE task queue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE task queue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE task queue timeout - completing request directly ad4: WARNING - SET_MULTI task queue timeout - completing request directly ad4: FAILURE - READ timed out LBA=0 ad4: FAILURE - READ retrying (1 retry left) LBA=0 ad4: FAILURE - READ timed out LBA=0 ad4: FAILURE - READ retrying (0 retries left) LBA=0 ad4: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad4: FAILURE - SETFEATURES ENABLE RCACHE timed out ad4: FAILURE - SETFEATURES ENABLE WCACHE timed out ad4: FAILURE - SETFEATURES SET_MULTI timed out ad4: 114473MB Seagate ST3120814A 3.AAJ at ata2-master PIO4 ad8: WARNING - SETFEATURES SET TRANSFER MODE task queue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE task queue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE WCACHE task queue timeout - completing request directly ad8: WARNING - SET_MULTI task queue timeout - completing request directly ad8: FAILURE - READ timed out LBA=0 ad8: FAILURE - READ retrying (1 retry left) LBA=0 ad8: FAILURE - READ timed out LBA=0 ad8: FAILURE - READ retrying (0 retries left) LBA=0 ad8: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad8: FAILURE - SETFEATURES ENABLE RCACHE timed out ad8: FAILURE - SETFEATURES ENABLE WCACHE timed out ad8: FAILURE - SETFEATURES SET_MULTI timed out ad8: 114473MB Seagate ST3120814A 3.AAJ at ata4-master PIO4 == and then these messages (and minor variants) keep repeating (I've let it go for at least one hour). I have about three dozen of these computers (from a failed M$ project) and would very much like to use them with FreeBSD. Any ideas? I'm game for almost anything. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise SX4060 on 7.1-BETA2
On Thu, Oct 23, 2008 at 02:01:55PM -0400, David Boyd wrote:
I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise
SX4060 RAID controller and two Seagate 120GB ATA disk drives.
The boot from CD keeps repeating the following (error) messages: (I'm
retyping here)
{snip -- for dmesg errors, see URL below}
You're the second person to report this problem recently. The other
person (see below) reported the same thing, also using a PATA
controller, and also using Seagate disks (though different models).
We now have two reproducible test cases where users are seeing continual
errors from the controller when attempting to set the transfer mode,
enable read and write caching, and SET_MULTI. The only similarity so
far is that they're both PATA users.
In Kristian's case, his disks were in a usable state, but we ultimately
determine the Silicon Image controller might be responsible for what he
was seeing (the SMART errors we saw in his logs could've been from any
time in the past; he saw errors on multiple disks, and not all of those
disks shown SMART log errors)... while David's not using a Silicon Image
controller at all.
Kristian's setup:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046023.html
http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046027.html
Silicon Image 0680 ATA100 (problem was also seen on Promise PDC20270)
ad4: Seagate ST3320620A 3.AAF at ata2-master PIO4
ad5: Seagate ST3320620A 3.AAF at ata2-slave PIO4
ad6: Seagate ST3750640A 3.AAE at ata3-master PIO4
ad7: Seagate ST3320620A 3.AAD at ata3-slave PIO4
David's setup (what we know so far):
http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046140.html
Promise SX4060
ad4: 114473MB Seagate ST3120814A 3.AAJ at ata2-master PIO4
ad8: 114473MB Seagate ST3120814A 3.AAJ at ata4-master PIO4
Soren/Andrey, can either of you comment on this? If at all possible, it
would be good to get this hammered out before 7.1-RELEASE is tagged.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
After an update stable doesn't boot
Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
After an update stable doesn't boot
Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.4 RC1 locks up solid on first reboot
On Thursday 23 October 2008 02:24:49 am Jeremy Chadwick wrote: On Thu, Oct 23, 2008 at 06:27:45AM +0200, Milan Obuch wrote: On Thursday 23 October 2008 01:32:27 Jo Rhett wrote: I haven't had time to investigate, but after installing 6.4RC1 on a machine I've been using with 6.3 for a few months, it installs painlessly but on the first and subsequent reboots you see BTX Loader 1.00 blah blah blah ... Loading /boot/defaults/loader.con \ At this point you have a hard refreeze -- no keyboard control, however I can reboot it from the Phantom card. System: Rackable C2004, dual Intel 2.66 processors, 4gb RAM, disk drive on built in SCSI port Absolutely nothing special, boots and runs 6.2 and 6.3 without a flaw. I'll have more time to investigate on Friday. Anything specific that would be more or less useful to debug in particular? I did not investigate on this issue too much, but there is an workaround - copy older /boot/loader over newer one. In my case, I am rebuilding whole world often, and now /boot/loader seems to not build correctly for me. Older one is ~ 250 kB, rebuilt will be ~ 185 kB, and freezes. In your case, you would write old /boot/loader from 6.3 over new installed with 6.4RC1 and it will boot normally again. I know it is only workaround, but it's quick and easy, and I have not too much time to investigate any further (not to mention I have no idea what to look for and where). Has anyone filed a PR on this problem, or contacted John Baldwin? Yes, but debugging these hangs is very non-trivial. It likely involves disassembling the BIOS and trying to see where it can get stuck in a loop. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
A little update. I can boot into freebsd using the life cd and can mount the disk when I'm in fixit. But from there on I have no idea what to do to fix this problem. Can any one please help Thanks On Thu, October 23, 2008 19:51, Reinhold wrote: Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
On Thu, 23 Oct 2008 21:40:23 +0100 (BST) Reinhold [EMAIL PROTECTED] wrote: A little update. I can boot into freebsd using the life cd and can mount the disk when I'm in fixit. But from there on I have no idea what to do to fix this problem. Some quick checks: - use fdisk (for example: fdisk ad0) to check if the correct slice is active - use boot0cfg -v to check the bootcode of the disk you are booting from HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
Reinhold [EMAIL PROTECTED] writes: A little update. I can boot into freebsd using the life cd and can mount the disk when I'm in fixit. But from there on I have no idea what to do to fix this problem. Try reinstalling the bootloader. You can do that by going into the sysinstall disk partitioning screens, but not changing any slice or partitioning settings. Can any one please help Thanks On Thu, October 23, 2008 19:51, Reinhold wrote: Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
On Thu, October 23, 2008 21:57, Torfinn Ingolfsen wrote: Some quick checks: - use fdisk (for example: fdisk ad0) to check if the correct slice is active - use boot0cfg -v to check the bootcode of the disk you are booting from Hi Thanks for getting back to me. Here is the info I have from fdisk and boot0cfg # fdisk ad12 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 312576642 (152625 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED and from # boot0cfg -v ad12 #flag start chstype end chsoffset size 10x80 0: 1: 10xa51023:254:63 63312576642 version=1.0 drive=0x80mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
On Thu, October 23, 2008 22:02, Lowell Gilbert wrote: Try reinstalling the bootloader. You can do that by going into the sysinstall disk partitioning screens, but not changing any slice or partitioning settings. Hi I tried to do this as well with no success, What I did notice was that it lists all the disks starting with ad10 ad12 ad18 ad22 ad6 and ad8 ad12 is where I have Freebsd installed on using UFS, the rest of the drives are all for a zfs pool Can any one please help Thanks On Thu, October 23, 2008 19:51, Reinhold wrote: Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After an update stable doesn't boot
Found the problem Its not Freebsd, its the pci raid controller. It was suggested to me on daemonforums.org to unplug all the drives and then plug them in one by one until it happened again, and it did, it happened when I plugged the first drive into the controller. Any ways, now I have to figure out how to get the controller to not want to boot the drives. Thanks for the suggestions On Thu, October 23, 2008 22:32, Reinhold wrote: On Thu, October 23, 2008 22:02, Lowell Gilbert wrote: Try reinstalling the bootloader. You can do that by going into the sysinstall disk partitioning screens, but not changing any slice or partitioning settings. Hi I tried to do this as well with no success, What I did notice was that it lists all the disks starting with ad10 ad12 ad18 ad22 ad6 and ad8 ad12 is where I have Freebsd installed on using UFS, the rest of the drives are all for a zfs pool Can any one please help Thanks On Thu, October 23, 2008 19:51, Reinhold wrote: Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
7.1 beta 2
I assume beta 2 is pretty darn close to what 7.1 release will be. Is there a list I can look at that details the outstanding issues/items being tested? I've checked the ERRATA and RELNOTES in the BETA2 directory, and didn't get much info. The goal is building a multi i/f router (just forwarding between connected networks) and dummynet enabled for WAN simulation. Broadcom gigE NIC's. Thanks Jim (the whiny kid in back who asks if we're there yet) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on i386/pc98
TB --- 2008-10-24 01:48:55 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 01:48:55 - starting RELENG_7_1 tinderbox run for i386/pc98 TB --- 2008-10-24 01:48:55 - mkdir /tinderbox/RELENG_7_1/i386/pc98 TB --- 2008-10-24 01:48:55 - cleaning the object tree TB --- 2008-10-24 01:48:55 - cvsupping the source tree TB --- 2008-10-24 01:48:55 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/i386/pc98/supfile TB --- 2008-10-24 01:54:48 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 01:54:48 - cd /src TB --- 2008-10-24 01:54:48 - ERROR: /src: No such file or directory TB --- 2008-10-24 01:54:48 - tinderbox aborted TB --- 1.94 user 1.02 system 353.20 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on ia64/ia64
TB --- 2008-10-24 01:54:48 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 01:54:48 - starting RELENG_7_1 tinderbox run for ia64/ia64 TB --- 2008-10-24 01:54:48 - mkdir /tinderbox/RELENG_7_1/ia64 TB --- 2008-10-24 01:54:48 - mkdir /tinderbox/RELENG_7_1/ia64/ia64 TB --- 2008-10-24 01:54:48 - cleaning the object tree TB --- 2008-10-24 01:54:48 - cvsupping the source tree TB --- 2008-10-24 01:54:48 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/ia64/ia64/supfile TB --- 2008-10-24 02:00:39 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 02:00:39 - cd /src TB --- 2008-10-24 02:00:39 - ERROR: /src: No such file or directory TB --- 2008-10-24 02:00:39 - tinderbox aborted TB --- 1.97 user 0.96 system 350.73 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on i386/i386
TB --- 2008-10-24 01:42:49 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 01:42:49 - starting RELENG_7_1 tinderbox run for i386/i386 TB --- 2008-10-24 01:42:49 - mkdir /tinderbox/RELENG_7_1/i386 TB --- 2008-10-24 01:42:49 - mkdir /tinderbox/RELENG_7_1/i386/i386 TB --- 2008-10-24 01:42:49 - cleaning the object tree TB --- 2008-10-24 01:42:49 - cvsupping the source tree TB --- 2008-10-24 01:42:49 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/i386/i386/supfile TB --- 2008-10-24 01:48:54 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 01:48:54 - cd /src TB --- 2008-10-24 01:48:54 - ERROR: /src: No such file or directory TB --- 2008-10-24 01:48:54 - tinderbox aborted TB --- 1.98 user 0.95 system 365.53 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on powerpc/powerpc
TB --- 2008-10-24 02:00:39 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 02:00:39 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc/powerpc TB --- 2008-10-24 02:00:39 - cleaning the object tree TB --- 2008-10-24 02:00:39 - cvsupping the source tree TB --- 2008-10-24 02:00:39 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-24 02:05:53 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 02:05:53 - cd /src TB --- 2008-10-24 02:05:53 - ERROR: /src: No such file or directory TB --- 2008-10-24 02:05:53 - tinderbox aborted TB --- 2.05 user 0.79 system 313.33 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on sparc64/sparc64
TB --- 2008-10-24 02:05:53 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 02:05:53 - starting RELENG_7_1 tinderbox run for sparc64/sparc64 TB --- 2008-10-24 02:05:53 - mkdir /tinderbox/RELENG_7_1/sparc64 TB --- 2008-10-24 02:05:53 - mkdir /tinderbox/RELENG_7_1/sparc64/sparc64 TB --- 2008-10-24 02:05:53 - cleaning the object tree TB --- 2008-10-24 02:05:53 - cvsupping the source tree TB --- 2008-10-24 02:05:53 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/sparc64/sparc64/supfile TB --- 2008-10-24 02:11:19 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 02:11:19 - cd /src TB --- 2008-10-24 02:11:19 - ERROR: /src: No such file or directory TB --- 2008-10-24 02:11:19 - tinderbox aborted TB --- 1.97 user 0.91 system 326.51 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_1 tinderbox] failure on amd64/amd64
TB --- 2008-10-24 01:37:06 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 01:37:06 - starting RELENG_7_1 tinderbox run for amd64/amd64 TB --- 2008-10-24 01:37:06 - mkdir /tinderbox/RELENG_7_1 TB --- 2008-10-24 01:37:06 - mkdir /tinderbox/RELENG_7_1/amd64 TB --- 2008-10-24 01:37:06 - mkdir /tinderbox/RELENG_7_1/amd64/amd64 TB --- 2008-10-24 01:37:06 - cleaning the object tree TB --- 2008-10-24 01:37:06 - cvsupping the source tree TB --- 2008-10-24 01:37:06 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/amd64/amd64/supfile TB --- 2008-10-24 01:42:49 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 01:42:49 - cd /src TB --- 2008-10-24 01:42:49 - ERROR: /src: No such file or directory TB --- 2008-10-24 01:42:49 - tinderbox aborted TB --- 1.95 user 0.97 system 343.08 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise SX4060 on 7.1-BETA2
David Boyd wrote: I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise SX4060 RAID controller and two Seagate 120GB ATA disk drives. Did you try to select Safe mode in boot menu or boot with ACPI disabled? Can you boot your system in verbose mode and show dmesg.boot? -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
