Re: FFS_ROOT is gone?
Tim Kientzle wrote this message on Tue, Jul 15, 2003 at 22:19 -0700: > John-Mark Gurney wrote: > >Harald Schmalzbauer wrote this message on Wed, Jul 16, 2003 at 02:58 +0200: > > > >>Let's see what Tim can contribute to this topic, since he also claimed to > >>have problems with "mountroot>" > > > >I have a possible patch that might address people's problems with > >mountroot. > > > >http://people.FreeBSD.org/~jmg/vfs_mount.diff > > I'm certain this won't address the problem > I saw. I was not using a serial console, > and I was not overflowing the buffer. > (So stripping parity bits and enforcing > buffer sizes won't help.) a) this effects all consoles, not just serial b) this doesn't just effect overflowing the buffer.. the return of -1 was being invalidated by c = cngetc() & 0177. You can't get -1 return on that. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
John-Mark Gurney wrote: Harald Schmalzbauer wrote this message on Wed, Jul 16, 2003 at 02:58 +0200: Let's see what Tim can contribute to this topic, since he also claimed to have problems with "mountroot>" I have a possible patch that might address people's problems with mountroot. http://people.FreeBSD.org/~jmg/vfs_mount.diff I'm certain this won't address the problem I saw. I was not using a serial console, and I was not overflowing the buffer. (So stripping parity bits and enforcing buffer sizes won't help.) Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
Harald Schmalzbauer wrote: Let's see what Tim can contribute to this topic, since he also claimed to have problems with "mountroot>" I installed FreeBSD (I think it was 5.0-RELEASE) on a hard disk attached to ad0. It worked, I tested it. I reconnected the hard disk to a separate IDE controller as ad4. The kernel booted, failed to mount root (as expected), and presented a "mountroot>" prompt. If I typed something invalid, the system rebooted. If I typed something valid, I got a "mountroot>" prompt again. In short, nothing I did would coerce the kernel into actually mounting root. Finally, I put the disk back on ad0, edited /etc/fstab and moved it back to ad4. That worked just fine. In short, "mountroot>" seems to do nothing if the kernel's initial attempt fails. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FFS_ROOT is gone?
John-Mark Gurney wrote: > Harald Schmalzbauer wrote this message on Wed, Jul 16, 2003 at > 02:58 +0200: > > Let's see what Tim can contribute to this topic, since he also > claimed to > > have problems with "mountroot>" > > I have a possible patch that might address people's problems with > mountroot. > > http://people.FreeBSD.org/~jmg/vfs_mount.diff > > try seeing if this patch improves things for you guys. Thanks a lot, I'll try this patch if i got my fileserver running back again. I hope this will ever be since there is my soekris image stored. Currently I don't have the time reproducing all teh stuff again. Thank you, -Harry > > -- > John-Mark GurneyVoice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
Harald Schmalzbauer wrote this message on Wed, Jul 16, 2003 at 02:58 +0200: > Let's see what Tim can contribute to this topic, since he also claimed to > have problems with "mountroot>" I have a possible patch that might address people's problems with mountroot. http://people.FreeBSD.org/~jmg/vfs_mount.diff try seeing if this patch improves things for you guys. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FFS_ROOT is gone?
Bernd Walter wrote: > > On Wed, Jul 16, 2003 at 02:38:18AM +0200, Harald Schmalzbauer wrote: > > *snip* > > > > > > The machine rebooted. No matter if I did "?" or any "ufs:xxYz". It's > > > > behaviour was like "empty line". > > > > > > That's the normal behavour if the line can't be parsed. > > > IIRC you can't correct typos on that line. > > > Even if a line corrected with backspace looks good - it is not. > > > > I'm very sure that I had a few attempts without any misstype > because I tried > > that some dozends and I was aware that I didn't use any backspace > > Another chance might be garbadge that went in. > E.g. I had a terminal server sending stop bytes when the kernel starts, > because the network was a bit to slow. > You'll never see those bytes because they are non-printable, but they > are there. That's really possible because my connection was a 38400 serial with a 3 meter cable. I had lots of line mesh with that connection. But it would mean that *all* my attempts had line failures, which could be possible but like I said they were near countless, so chances are good that at least one was correct?!?!? Let's see what Tim can contribute to this topic, since he also claimed to have problems with "mountroot>" > > -- > B.Walter BWCThttp://www.bwct.de > [EMAIL PROTECTED] [EMAIL PROTECTED] > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
On Wed, Jul 16, 2003 at 02:38:18AM +0200, Harald Schmalzbauer wrote: > *snip* > > > > The machine rebooted. No matter if I did "?" or any "ufs:xxYz". It's > > > behaviour was like "empty line". > > > > That's the normal behavour if the line can't be parsed. > > IIRC you can't correct typos on that line. > > Even if a line corrected with backspace looks good - it is not. > > I'm very sure that I had a few attempts without any misstype because I tried > that some dozends and I was aware that I didn't use any backspace Another chance might be garbadge that went in. E.g. I had a terminal server sending stop bytes when the kernel starts, because the network was a bit to slow. You'll never see those bytes because they are non-printable, but they are there. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FFS_ROOT is gone?
*snip* > > The machine rebooted. No matter if I did "?" or any "ufs:xxYz". It's > > behaviour was like "empty line". > > That's the normal behavour if the line can't be parsed. > IIRC you can't correct typos on that line. > Even if a line corrected with backspace looks good - it is not. I'm very sure that I had a few attempts without any misstype because I tried that some dozends and I was aware that I didn't use any backspace *snip* > > booting the kernel with only boot0, no loader. > > > > Has this feature been intentionally removed? > > The loader sets variables that are required for the kernel to run > such as reading device.hints. > You can still compile the variables staticaly into the kernel and > directly use boot2 (boot0 is the bootmanager). Ahhh, of course there is a new device.hint. Ok. I'll try that some time. (boot0 was wrong, I meant the stage taht usually loads the loader, like you said boot0!) Thanks, -Harry > > -- > B.Walter BWCThttp://www.bwct.de > [EMAIL PROTECTED] [EMAIL PROTECTED] > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
On Wed, Jul 16, 2003 at 01:47:59AM +0200, Harald Schmalzbauer wrote: > Bernd Walter wrote: > > On Tue, Jul 15, 2003 at 12:22:31PM -0700, Tim Kientzle wrote: > > > Harald Schmalzbauer wrote: > > > >The problem is solved. It was stupid, but I thought why should > > I have to > > > >set > > > >/ in /etc/fstab when the filesystem isn't mounted yet, so the > > file can't be > > > >read. > > > >But it seems the kernel reads this file "loader-like" *before* the > > > >filesystem is mounted. > > > > > > I believe that the loader actually reads this file (it > > > has to be able to locate and read files from UFS anyway > > > in order to load the kernel) and passes the root f/s > > > information to the kernel when it boots. This should > > > probably be documented in fstab(5) > > > > You can pass a filesystem at the loader prompt: > > vfs.root.mountfrom="" > > > > > >Considering the above to be correct I can't understand the > > ability to enter > > > >e. g. ufs:/dev/ad0a at "mountroot>" when it doesn't work. > > > > > > I've also been stung by the fact that the > > > "mountroot>" prompt is broken. > > > I looked briefly at the code, but the > > > bug is not particularly obvious. > > > > At least it wasn't broken a while ago. > > What happens exactly after entering the correct device? > > The machine rebooted. No matter if I did "?" or any "ufs:xxYz". It's > behaviour was like "empty line". That's the normal behavour if the line can't be parsed. IIRC you can't correct typos on that line. Even if a line corrected with backspace looks good - it is not. > That was mine dunno about Tim's > > Regarding loader reades /etc/fstab: Of course loader and even boot can read > from ufs but I verified that current device was disk0s1 (where my 165-ID > was) and also something like root-mount was set to disk0s1. > > Next thing is that boot0 could'nt boot my kernel (5.1-release). > Some time ago I built a little accesspoint with 4.6 and there was no problem > booting the kernel with only boot0, no loader. > > Has this feature been intentionally removed? The loader sets variables that are required for the kernel to run such as reading device.hints. You can still compile the variables staticaly into the kernel and directly use boot2 (boot0 is the bootmanager). -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FFS_ROOT is gone?
Bernd Walter wrote: > On Tue, Jul 15, 2003 at 12:22:31PM -0700, Tim Kientzle wrote: > > Harald Schmalzbauer wrote: > > >The problem is solved. It was stupid, but I thought why should > I have to > > >set > > >/ in /etc/fstab when the filesystem isn't mounted yet, so the > file can't be > > >read. > > >But it seems the kernel reads this file "loader-like" *before* the > > >filesystem is mounted. > > > > I believe that the loader actually reads this file (it > > has to be able to locate and read files from UFS anyway > > in order to load the kernel) and passes the root f/s > > information to the kernel when it boots. This should > > probably be documented in fstab(5) > > You can pass a filesystem at the loader prompt: > vfs.root.mountfrom="" > > > >Considering the above to be correct I can't understand the > ability to enter > > >e. g. ufs:/dev/ad0a at "mountroot>" when it doesn't work. > > > > I've also been stung by the fact that the > > "mountroot>" prompt is broken. > > I looked briefly at the code, but the > > bug is not particularly obvious. > > At least it wasn't broken a while ago. > What happens exactly after entering the correct device? The machine rebooted. No matter if I did "?" or any "ufs:xxYz". It's behaviour was like "empty line". That was mine dunno about Tim's Regarding loader reades /etc/fstab: Of course loader and even boot can read from ufs but I verified that current device was disk0s1 (where my 165-ID was) and also something like root-mount was set to disk0s1. Next thing is that boot0 could'nt boot my kernel (5.1-release). Some time ago I built a little accesspoint with 4.6 and there was no problem booting the kernel with only boot0, no loader. Has this feature been intentionally removed? Best regards, -Harry > > -- > B.Walter BWCThttp://www.bwct.de > [EMAIL PROTECTED] [EMAIL PROTECTED] > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
On Tue, Jul 15, 2003 at 12:22:31PM -0700, Tim Kientzle wrote: > Harald Schmalzbauer wrote: > >The problem is solved. It was stupid, but I thought why should I have to > >set > >/ in /etc/fstab when the filesystem isn't mounted yet, so the file can't be > >read. > >But it seems the kernel reads this file "loader-like" *before* the > >filesystem is mounted. > > I believe that the loader actually reads this file (it > has to be able to locate and read files from UFS anyway > in order to load the kernel) and passes the root f/s > information to the kernel when it boots. This should > probably be documented in fstab(5) You can pass a filesystem at the loader prompt: vfs.root.mountfrom="" > >Considering the above to be correct I can't understand the ability to enter > >e. g. ufs:/dev/ad0a at "mountroot>" when it doesn't work. > > I've also been stung by the fact that the > "mountroot>" prompt is broken. > I looked briefly at the code, but the > bug is not particularly obvious. At least it wasn't broken a while ago. What happens exactly after entering the correct device? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
Harald Schmalzbauer wrote: The problem is solved. It was stupid, but I thought why should I have to set / in /etc/fstab when the filesystem isn't mounted yet, so the file can't be read. But it seems the kernel reads this file "loader-like" *before* the filesystem is mounted. I believe that the loader actually reads this file (it has to be able to locate and read files from UFS anyway in order to load the kernel) and passes the root f/s information to the kernel when it boots. This should probably be documented in fstab(5) Considering the above to be correct I can't understand the ability to enter e. g. ufs:/dev/ad0a at "mountroot>" when it doesn't work. I've also been stung by the fact that the "mountroot>" prompt is broken. I looked briefly at the code, but the bug is not particularly obvious. Tim Kientzle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FFS_ROOT is gone?
Bernd Walter wrote: > On Sat, Jul 12, 2003 at 02:22:41AM +0200, Harald Schmalzbauer wrote: > > Hello, > > > > my kernel (5.1-REL) can't mount root (mountroot>) on my CF-card although > > it's booting fine and I can mount the card on my USB card reader. > > I had a look at GENERIC and saw that I didn't miss the option > FFS_ROOT but > > it doesn't exist any longer. > > Any ideas why I can't mount root? > > Any messages? > -can't mount- ist sparse input. > Does it mount the volume without being rootfs? The problem is solved. It was stupid, but I thought why should I have to set / in /etc/fstab when the filesystem isn't mounted yet, so the file can't be read. But it seems the kernel reads this file "loader-like" *before* the filesystem is mounted. Considering the above to be correct I can't understand the ability to enter e. g. ufs:/dev/ad0a at "mountroot>" when it doesn't work. But everything is fine now, thank you for your answer. Best regards, -Harry > > -- > B.Walter BWCThttp://www.bwct.de > [EMAIL PROTECTED] [EMAIL PROTECTED] > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FFS_ROOT is gone?
On Sat, Jul 12, 2003 at 02:22:41AM +0200, Harald Schmalzbauer wrote: > Hello, > > my kernel (5.1-REL) can't mount root (mountroot>) on my CF-card although > it's booting fine and I can mount the card on my USB card reader. > I had a look at GENERIC and saw that I didn't miss the option FFS_ROOT but > it doesn't exist any longer. > Any ideas why I can't mount root? Any messages? -can't mount- ist sparse input. Does it mount the volume without being rootfs? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FFS_ROOT is gone?
Hello, my kernel (5.1-REL) can't mount root (mountroot>) on my CF-card although it's booting fine and I can mount the card on my USB card reader. I had a look at GENERIC and saw that I didn't miss the option FFS_ROOT but it doesn't exist any longer. Any ideas why I can't mount root? The card is found correctly as ad0 Thanks, -Harry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
