WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Need help..

Ok, I replaced the LABEL=/ by /dev/hda5 and LABEL=/usr by /dev/hda6
in dom-0 /etc/fstaba. Now system does try to boot dom-1 but has prolems
with fsck of /dev/hda7 (/dev/sda6) and suggets to run fsck manually.
If fsck.ext3 is run from dom-0 on /dev/hda7 it says that file system is clean!
I plan to try /usr readonly tomorrow.

-ishwar

--output of mount in dom0--
/dev/hda5 on / type ext3 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
/dev/hda6 on /usr type ext3 (rw)

----output on xen_read_console during creation of dom1--
[1] Linux version 2.4.26-xeno (xenod@xxxxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.
20030222 (Red Hat Linux 3.2.2-5)) #2 Tue Apr 20 03:24:19 BST 2004
[1] On node 0 totalpages: 16384
[1] zone(0): 4096 pages.
[1] zone(1): 12288 pages.
[1] zone(2): 0 pages.
[1] Kernel command line: ip=141.209.170.222:169.254.1.0:141.209.170.1:255.255.
5.0::eth0:off root=/dev/sda1 ro 4 VMID=1 usr=/dev/sda6
[1] Initializing CPU#0
[1] Xen reported: 501.155 MHz processor.
[1] Calibrating delay loop... 1998.84 BogoMIPS
[1] Memory: 62880k/65536k available (1288k kernel code, 2656k reserved, 245k d
a, 60k init, 0k highmem)
[1] Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
[1] Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
[1] Mount cache hash table entries: 512 (order: 0, 4096 bytes)
[1] Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
[1] Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
[1] CPU: L1 I cache: 16K, L1 D cache: 16K
[1] CPU: L2 cache: 128K
[1] CPU: Intel Celeron (Mendocino) stepping 05
[1] POSIX conformance testing by UNIFIX
[1] Linux NET4.0 for Linux 2.4
[1] Based upon Swansea University Computer Society NET3.039
[1] Initializing RT netlink socket
[1] Starting kswapd
[1] Journalled Block Device driver loaded
[1] Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
[1] Xeno console successfully installed
[1] Starting Xeno Balloon driver
[1] pty: 256 Unix98 ptys configured
[1] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
[1] loop: loaded (max 8 devices)
[1] NET4: Linux TCP/IP 1.0 for NET4.0
[1] IP Protocols: ICMP, UDP, TCP
[1] IP: routing cache hash table of 512 buckets, 4Kbytes
[1] TCP: Hash tables configured (established 4096 bind 8192)
[1] IP-Config: Complete:
[1]       device=eth0, addr=141.209.170.222, mask=255.255.255.0, gw=141.209.17
1,
[1]      host=141.209.170.222, domain=, nis-domain=(none),
[1]      bootserver=169.254.1.0, rootserver=169.254.1.0, rootpath=
[1] ip_conntrack version 2.1 (512 buckets, 4096 max) - 288 bytes per conntrack
[1] ip_tables: (C) 2000-2002 Netfilter core team
[1] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
[1] root_device_name = sda1
[1] EXT3-fs: INFO: recovery required on readonly filesystem.
[1] EXT3-fs: write access will be enabled during recovery.
[1] kjournald starting.  Commit interval 5 seconds
[1] EXT3-fs: recovery complete.
[1] EXT3-fs: mounted filesystem with ordered data mode.
[1] VFS: Mounted root (ext3 filesystem) readonly.
[1] Freeing unused kernel memory: 60k freed
[1] INIT: version 2.85 booting
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty1: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty2: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty3: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty4: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty5: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 34: /dev/tty6: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 38: /dev/tty7: No such device
[1] modprobe: modprobe: Can't locate module char-major-4
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty8: No such device
[1] Welcome to Fedora Core
[1] Press 'I' to enter interactive startup.
[1] Configuring kernel parameters:  [  OK  ]
[1] modprobe: modprobe: Can't locate module char-major-10-135
[1] modprobe: modprobe: Can't locate module char-major-4
[1] hwclock is unable to get I/O port access:  the iopl(3) call failed.
[1] Setting clock  (localtime): Wed Apr 21 19:57:00 EDT 2004 [  OK  ]
[1] Setting hostname localhost.localdomain:  [  OK  ]
[1] Checking root filesystem
[1] [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
[1] /dev/sda1: clean, 23916/122624 files, 53024/244983 blocks
[1] [  OK  ]
[1] Remounting root filesystem in read-write mode:  [  OK  ]
[1] Activating swap partitions:  [  OK  ]
[1] Finding module dependencies:  [  OK  ]
[1] Checking filesystems
[1] Checking all file systems.
[1] [/sbin/fsck.ext3 (1) -- /usr] fsck.ext3 -a /dev/sda6
[1] /dev/sda6: clean, 29742/122624 files, 201088/244983 blocks
[1] Error writing block 488 (Attempt to write block from filesystem resulted i
short write).  Error writing block 488 (Attempt to write block from filesystem
esulted in short write).
[1]
[1] /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
[1] (i.e., without -a or -p options)
[1]
[1]
[1] /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
[1] (i.e., without -a or -p options)
[1] [FAILED]
[1]
[1] *** An error occurred during the file system check.
[1] *** Dropping you to a shell; the system will reboot
[1] *** when you leave the shell.
[1] Give root password for maintenance
^C
[root@pe-dyn221 ir]#
----

On Wed, 21 Apr 2004, Rolf Neugebauer wrote:

>
>
> On Wed, 2004-04-21 at 18:21, I RATTAN wrote:
> > I am confused:
> >
> > dom0 /usr is /dev/hda6
> >
> > and
> >
> > dom1 /usr is /dev/sd6 which is mapped to /dev/hda7
> >
> > does it mean even these are separate physical entities, they
> > have to mounted read-only?
>
> if they are separate physical partitions mounting rw should be fine. We
> normally just use one /usr partition and mount it ro to all domains.
>
> to things to get closer to the root of your problem:
>
> can you show us the output of 'mount' in dom0?
>
> can you change the LABEL= entries in /etc/fstab to contain the /dev/hda*
> partition names.
>
> depending on how you created your partitions you might have multiple
> partitions with the same label. I generally avoid using labels and use
> the explicit devices.
>
> Thanks
> Rolf


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel