Re: HEADS-UP: bdevs have been assimilated.
In message [EMAIL PROTECTED], Matthew Jacob writes: Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps. Any failed command causes the single user shell to exit. This doesn't sound like a /dev related problem to me. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
In message [EMAIL PROTECTED], Matthew Jacob writes: Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps. Any failed command causes the single user shell to exit. This doesn't sound like a /dev related problem to me. You're probably right about this. Maybe we should all call it "Matt's really bad day where he got vicious" and we'll try again tomorrow after a new update/nightly build. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.
In message [EMAIL PROTECTED], Matthew Jacob writes: Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' Bruce and Mike smith took out a testing-shim a little early which allowed us to test with /dev/r* in /etc/fstab. Change your /etc/fstab to read /dev/ad0a and you should be happy again. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.
In message [EMAIL PROTECTED], Matthew Jacob writes: Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' Bruce and Mike smith took out a testing-shim a little early which allowed us to test with /dev/r* in /etc/fstab. Change your /etc/fstab to read /dev/ad0a and you should be happy again. Actually, no, I'm not- the 'rad' was less worrisome than the other stuff (like fsck core dumping, mount dyings, etc.). but, but we'll see what happens tomorrow. I'll be up to date and have a fresh build with the new mount.h and I'll make it work if it doesn't (I have to as I have too many other things backed up behind this toe stub). I probably should have used an i386 to test this change first rather than an alpha. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
With todays' build, the previous problems went away. Other problems have replaced them (sio's wierd again for alpha), but that's a different story. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
Excerpts from FreeBSD-Current: 2-Dec-99 Re: HEADS-UP: bdevs have be.. by "David O'Brien"@FreeBSD. At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live files system for the Alpha. Nor can you even boot sysinstall and get a shell if you use a serial console. All-in-all recovery on the Alpha is "lacking". Yup, at the times when I trashed my alpha install the install disk and NFS have been my only friends (the emergency shell is just enough to get you to mount_nfs a snapshot sitting elsewhere, albeit not in a friendly way not even having 'ls' :) One could make an NFS-client bootdisk for rescue, although a live cdrom fits the bill far better... is there room on the i386 disk for alpha bits? It would save having to ship an extra disk if that's an issue. It's no big deal to cd /cdrom/alpha, maybe toss a few symlinks around, to easilly recover the system. Tom (who is joyful enough since floppy support appeared on the alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
On Thursday, 2 December 1999 at 17:21:55 -0800, Matthew Jacob wrote: Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps. Any failed command causes the single user shell to exit. What can I do to get out of this disaster other than attempt a reinstall? Can't you boot from the old kernel? Or have you already wiped the bdevs? If so, how about the fixit floppy/CD-ROM? Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
Can't you boot from the old kernel? Or have you already wiped the I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped all block devs, so swapon, etc. ,fail.. However, this is the conundrum- it's not safe to do a 'make installworld' on a two week old kernel, but the new kernel with old mount, fsck, etc., obviously cannot cope with the new 'raw-only' devices. An experience like this will move users to OpenBSD. This kind of jump up is completely unacceptable. bdevs? If so, how about the fixit floppy/CD-ROM? This is alpha, and no floppy. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
Matthew Jacob writes: Can't you boot from the old kernel? Or have you already wiped the I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped all block devs, so swapon, etc. ,fail.. However, this is the conundrum- it's not safe to do a 'make installworld' on a two week old kernel, but the new kernel with old mount, fsck, etc., obviously cannot cope with the new 'raw-only' devices. An experience like this will move users to OpenBSD. This kind of jump up is completely unacceptable. Slow down. You are getting screwed by a combination of things. It isn't all phk's fault. The bdev elimination is one factor, but the most important one (the fsck/mount segv) is due to int/long breakage introduced version 1.85 of mount.h. This happened at the worst possible time (just after the bdev elimination). If I wasn't such a timid committer, I would have just committed the damned fix yesterday, before running it by Kirk you wouldn't have had this problem. I tried to be vocal about it (messages to -alpha and -committers), but I guss that wasn't enought. Sorry, Drew -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.
Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 But then, there's an older system on da0: Mounting root from ufs:da0a WARNING: clock gained 14 days -- CHECK AND RESET THE DATE! swapon: adding /dev/da0b as swap device which makes it less of a bad bad but still very very annoying. It's hard to find out what's going on because even though there is some vague attempts to stop the loader (whereupon you get a phony 'ok' prompt), no passing of variables set there occurs (so no 'bootverbose'). So, it's conceivable that this is just edge case alpha breakage. With 2 weeks to feature freeze for 4.0 it is very hard for some of us who attempt to make sure things we deliver actually work on both platforms if the second platform is broken. I'm plenty pissed off, but, c'est la vie... -matt On Thu, 2 Dec 1999, Matthew Jacob wrote: Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps. Any failed command causes the single user shell to exit. What can I do to get out of this disaster other than attempt a reinstall? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
(removed from general list) Slow down. You are getting screwed by a combination of things. It isn't all phk's fault. The bdev elimination is one factor, but the most important one (the fsck/mount segv) is due to int/long breakage introduced version 1.85 of mount.h. This happened at the worst possible time (just after the bdev elimination). If I wasn't such a timid committer, I would have just committed the damned fix yesterday, before running it by Kirk you wouldn't have had this problem. I tried to be vocal about it (messages to -alpha and -committers), but I guss that wasn't enought. Well, I wasn't back in town until last night with 5000 messages to catch up on. Sorry for not getting your questions first. There are other things broken too. Oh well- I really shouldn't get wired. *BSD will get taken as a serious effort as much as it deserves based upon what actually *occurs*, not what I would *wish* to actually occur -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.
Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' You never mount 'r' devices. That should be '/dev/ad0a', and you can override the default with either: set vfs.root.mountfrom="ufs:/dev/ad0a" in the loader at the 'ok' prompt, or by entering 'ufs:/dev/ad0a' at the emergency recovery prompt that you get after the error messages you've quoted above. But then, there's an older system on da0: Mounting root from ufs:da0a WARNING: clock gained 14 days -- CHECK AND RESET THE DATE! swapon: adding /dev/da0b as swap device which makes it less of a bad bad but still very very annoying. It's hard to find out what's going on because even though there is some vague attempts to stop the loader (whereupon you get a phony 'ok' prompt), no passing of variables set there occurs (so no 'bootverbose'). The variable's name is boot_verbose, but the Alpha has never supported it (a combination of oversight and overbusiness on both my part and Doug's). You'll find that 'boot -v' and 'load kernel -v' will achieve the desired results in the meantime, and I'll try to get it working "right" soon now that I have a 'real' alpha to work on. I'm also curious as to what's "phony" about the 'ok' prompt? Is it just that things aren't 'ok'? 8) So, it's conceivable that this is just edge case alpha breakage. With 2 weeks to feature freeze for 4.0 it is very hard for some of us who attempt to make sure things we deliver actually work on both platforms if the second platform is broken. I'm plenty pissed off, but, c'est la vie... So we should, like, feature freeze before we feature freeze? That's not so good. I don't mean to be insulting or anything, but so far most of your problems appear to be pilot error. If you take them out of the picture, it's not _really_ that bad. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP: bdevs have been assimilated.
On Thu, Dec 02, 1999 at 08:24:19PM -0500, Greg Lehey wrote: Can't you boot from the old kernel? Or have you already wiped the bdevs? If so, how about the fixit floppy/CD-ROM? At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live files system for the Alpha. Nor can you even boot sysinstall and get a shell if you use a serial console. All-in-all recovery on the Alpha is "lacking". -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message