pxeboot - EXT3-fs:unable to read superblock

[Grey Kuyper]

Steve:
 
It is trying to mount a remote NFS.
The HDD had NOT beed disconnected.
I disconnected the HDD and rebooted. There is no change in behaviour.
 
I also did the following:
 
1) I created a /nfs subdirectory on the server.
2) I copied the ENTIRE contents of the client's / directory to the server's /nfs directory.
3) here are the contents of the /etc/exports file:
     /nfs      192.168.0.100(ro,no_root_squash,sync)
4) I restarted the nfd daemon with service nfs restart.
5) I added root=/nfs to the append line in the /tftpdboot/pxelinux.cfg/default file. The complete line now reads:
     APPEND initrd=initrd-2.4.20-6.img root=/nfs
 
To me this should export the server's /nfs as a point to mount on the client. It should be identical to what the client sees when it boots from its own hard disk (since it is a copy of that hard disc that has beed placed inn  the /nfs directory of the server and then exported via nfs)

This did change the error message. It now says:
 
   VFS: Cannot open root device "/nfs" or 00:00
   please append a correct "root=" boot option.
 
I guess this is progress!  I just read a half a dozen posts on the internet re this message but nothing usable yet.

Steve <steve at focb.co.nz> wrote:

If it is a diskless workstation then it probably wont have either an ext2 
OR an ext3 filesystem - it would be normal to mount the root filesystem as 
a remote NFS mount I believe.

If you did infact just copy the initrd and vmlinuz images across to the 
server and boot off these with no modification then it is quite possibly 
still trying to mount the local hard drive - is this still in the machine 
?

Another thing to note - just because you used the same CD's and it is the 
same distro, does not mean that the filesystems are the same - you should 
know what you created the filesystems as - and if the filesystems were 
already created on one of the boxes, depending on the options used this 
may well be ext2.

A bit more information would probably be a good idea (is the hard drive 
still in the machine for a start ? )

-- 
Steve.


On Wed, 16 Jun 2004, Grey Kuyper wrote:

> Need a little help after 48 hours of looking at FAQs and mailing lists.
> Obviously I am blind to the answer.
>
> I have a working Linux computer. I simply wish to make it diskless. To
> do this I have another linux server which I set up as a DHCP/TFTP server
> with pxebooot.
>
> I have gotten to the point where pxe boots and the vmlinuz and boot
> images are read. But then there is a problem:
> 
> Mounting root filesystem
> EXT3-fs:unable to read superblock
> mount: error 22 mounting ext3
> pivotroot: pivot_root (/sysroot /sysroot/initrd) failed 2:
> 
> etc.
>
> This implies an ext2 vs. ext3 mismatch (according to the copious posts
> all over the internet). HOWEVER ...
> 
> 1) I created the server on one computer and the client on the HD of another computer with THE SAME CDs (therefore the same version of Linux).
> 2) I copied the vmlinuz and initrd from the client computer's HDD to the /tftpboot directory of the server computer.
> 3) I then told the client to boot from LAN rather than from the HDD.
> 
> THEORETICALLY, the images should be matched, whatever they are supposed to be (ext2 or ext3).
> 
> Here is my /tftpboot/pxelinux.cfg/defalut file's contents:
> 
> LABEL linux
> KERNEL vmlinuz-2.4.20-6
> APPEND initrd=initrd-2.4.20-6.img
> IPAPPEND 1
> prompt 1
> timeout 100
> 
> 
> Where is my logic or knowledge hole so I can get past this problem please.
> 
> Thanks!
> Grey
> 
> 
> 
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - Helps protect you from nasty viruses.
> 


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

		
---------------------------------
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.