Hi, We''ve servers in Amazon EC2. Recently we are trying to upload the Slackware 14 (64 bit) on it. getting the below error, xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 78.890483] Restarting system. After that I''ve changed the xvda1 to xvde1 as below /etc/fstab /dev/xvde1 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /boot/grub/menu.lst default 0 timeout 3 title kernel-2.6.34 root (hd0) kernel /boot/vmlinuz root=/dev/xvde1 xencons=xvde1 console=xvde1 ro After my console output is, XENBUS: Device with no driver: device/console/0 [ 4.205507] VFS: Cannot open root device "xvde1" or unknown-block(0,0) [ 4.205520] Please append a correct "root=" boot option; here are the available partitions: [ 4.205538] ca01 10485760 xvda1 driver: vbd [ 4.205549] ca02 156352512 xvda2 driver: vbd [ 4.205559] ca03 917504 xvda3 driver: vbd [ 4.205570] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 4.205581] Pid: 1, comm: swapper Not tainted 2.6.34 #1 suggestion pls... regards, sg _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
We''ve servers in Amazon EC2. Recently we are trying to upload the Slackware 14 (64 bit) on it. getting the below error, xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 78.890483] Restarting system. After that I''ve changed the xvda1 to xvde1 as below /etc/fstab /dev/xvde1 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /boot/grub/menu.lst default 0 timeout 3 title kernel-2.6.34 root (hd0) kernel /boot/vmlinuz root=/dev/xvde1 xencons=xvde1 console=xvde1 ro After my console output is, XENBUS: Device with no driver: device/console/0 [ 4.205507] VFS: Cannot open root device "xvde1" or unknown-block(0,0) [ 4.205520] Please append a correct "root=" boot option; here are the available partitions: [ 4.205538] ca01 10485760 xvda1 driver: vbd [ 4.205549] ca02 156352512 xvda2 driver: vbd [ 4.205559] ca03 917504 xvda3 driver: vbd [ 4.205570] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 4.205581] Pid: 1, comm: swapper Not tainted 2.6.34 #1 suggestion pls... regards, sg Hi, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Am Montag, 1. Juli 2013, 11:45:32 schrieb Geetha, ANGLER - EIT:> After that I''ve changed the xvda1 to xvde1 as below...> [ 4.205520] Please append a correct "root=" boot option; here are the > available partitions: [ 4.205538] ca01 10485760 xvda1 driver: vbd > > [ 4.205549] ca02 156352512 xvda2 driver: vbd > [ 4.205559] ca03 917504 xvda3 driver: vbdat least xvde1 is wrong as it seems there is just xvda available as storage device.> xenbus_dev_shutdown: device/console/0: Initialising != Connected, skippingThis "just" means that there is no console connected so that that is skipped - but this has nothing to do with your storage devices. Hmmm, not shure what you are doing there att. best regards, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, 2013-07-01 at 11:45 +0530, Geetha, ANGLER - EIT wrote:> We''ve servers in Amazon EC2. Recently we are trying to upload the > Slackware 14 (64 bit) on it. > > > getting the below error, > > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > skipping > [ 78.890483] Restarting system.No errors here, just a warning.> After that I''ve changed the xvda1 to xvde1 as belowWhy? Your device appears to be called xvda not xvde and the error message is pretty clear that xvda is present and xvde is not:> [ 4.205507] VFS: Cannot open root device "xvde1" or unknown-block(0,0) > [ 4.205520] Please append a correct "root=" boot option; here are the available partitions: > [ 4.205538] ca01 10485760 xvda1 driver: vbd > > [ 4.205549] ca02 156352512 xvda2 driver: vbd > [ 4.205559] ca03 917504 xvda3 driver: vbd > [ 4.205570] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)> suggestion pls...Don''t randomly change xvde into xvda? Ian.
----- Original Message ----- From: Ian Campbell To: ANGLER - EIT Geetha Sent: Mon, 1 Jul 2013 18:12:33 +0530 (IST) Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) Please keep the list CCd. On Mon, 2013-07-01 at 18:07 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > > Thanks for your suggestion. > > Actually I am got the below error as I changed xvda to xvde console > > Ref url: > > http://serverfault.com/questions/337695/reboot-fails-on-rhel-6-1-after-kernel-update-on-amazon-ec2 > > Error: > > Please stand by while rebooting the system... > md: stopping all md devices. > xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping > Restarting system. > > > > getting the below error, > > > > > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > > skipping > > [ 78.890483] Restarting system. > > No errors here, just a warning. > > but I could not login to my instance Ian.. > > > > > After that I''ve changed the xvda1 to xvde1 as below > > Why? Your device appears to be called xvda not xvde and the error > message is pretty clear that xvda is present and xvde is not: > > > [ 4.205507] VFS: Cannot open root device "xvde1" or > unknown-block(0,0) > > [ 4.205520] Please append a correct "root=" boot option; here are > the available partitions: > > [ 4.205538] ca01 10485760 xvda1 driver: vbd > > > > [ 4.205549] ca02 156352512 xvda2 driver: vbd > > [ 4.205559] ca03 917504 xvda3 driver: vbd > > [ 4.205570] Kernel panic - not syncing: VFS: Unable to mount root > fs on unknown-block(0,0) > > > suggestion pls... > > Don''t randomly change xvde into xvda? > > Ian. > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, 2013-07-01 at 18:27 +0530, Geetha, ANGLER - EIT wrote:> On Mon, 2013-07-01 at 18:07 +0530, Geetha, ANGLER - EIT wrote: > > Ian, > > > > > > Thanks for your suggestion. > > > > Actually I am got the below error as I changed xvda to xvde console > > > > Ref url: > > > > > http://serverfault.com/questions/337695/reboot-fails-on-rhel-6-1-after-kernel-update-on-amazon-ec2That seems to deal with RHEL. I expect it has nothing to do with your issue. At least I can''t see any correlation based upon the limited info you have given.> > > > Error: > > > > Please stand by while rebooting the system... > > md: stopping all md devices. > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > skipping > > Restarting system. > > > > > > > getting the below error, > > > > > > > > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > > > skipping > > > [ 78.890483] Restarting system. > > > > No errors here, just a warning. > > > > but I could not login to my instance Ian..Well, it''s rebooted, so of course not. Are you saying that it reboots automatically every time you start it? If so then I think you need to provide complete logs of the guest boot, since what you have provided only covers the consequences of the issue, not the actual issue. This highlights the importance of explaining fully and clearly the behaviour you are seeing when reporting an issue. Ian.
Ian, Please find the attachment of console output. root@slack64:~/us-east# ssh -i sg_mykey -v ec2-23-20-223-66.compute-1.amazonaws.com OpenSSH_5.5p1, OpenSSL 0.9.8n 24 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to ec2-23-20-223-66.compute-1.amazonaws.com [23.20.223.66] port 22. debug1: connect to address 23.20.223.66 port 22: Connection timed out ssh: connect to host ec2-23-20-223-66.compute-1.amazonaws.com port 22: Connection timed out Regards, SG -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: Monday, July 01, 2013 6:37 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Mon, 2013-07-01 at 18:27 +0530, Geetha, ANGLER - EIT wrote:> On Mon, 2013-07-01 at 18:07 +0530, Geetha, ANGLER - EIT wrote: > > Ian, > > > > > > Thanks for your suggestion. > > > > Actually I am got the below error as I changed xvda to xvde console > > > > Ref url: > > > > > http://serverfault.com/questions/337695/reboot-fails-on-rhel-6-1-after > -kernel-update-on-amazon-ec2That seems to deal with RHEL. I expect it has nothing to do with your issue. At least I can''t see any correlation based upon the limited info you have given.> > > > Error: > > > > Please stand by while rebooting the system... > > md: stopping all md devices. > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > skipping > > Restarting system. > > > > > > > getting the below error, > > > > > > > > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, > > > skipping > > > [ 78.890483] Restarting system. > > > > No errors here, just a warning. > > > > but I could not login to my instance Ian..Well, it''s rebooted, so of course not. Are you saying that it reboots automatically every time you start it? If so then I think you need to provide complete logs of the guest boot, since what you have provided only covers the consequences of the issue, not the actual issue. This highlights the importance of explaining fully and clearly the behaviour you are seeing when reporting an issue. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Ian, The instance is rebooting it self I think so... The below is the end of my console output.. There is no more Ian,,, [ 78.569862] xenbus_dev_shutdown: device/console/0: Initialising !Connected, skipping [ 78.890483] Restarting system. We are running servers in Amazon aws... I am working with slackware since 11.0 version (2008 to till date).... Now we need to update the slackware 13.7 to slackware 14 64 bit version. I''ve built the own kernel package of slackare and upload the server which I''ve sent the documentation in previous mail... I am trying a lot to set up the slackware 14 64 bit on Amazon aws.. I''ve changed the pv-grub kernel which bundle the image.. But no use.. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedkernels.html# UsingUserProvidedKernel I could not get into the slackware 14 as I followed the same steps of configuration in old versions.. This is my scenio Ian... Regards Geetha -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: Tuesday, July 02, 2013 2:24 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Tue, 2013-07-02 at 11:06 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Please find the attachment of console output."Command line: root=/dev/xvda1 xencons=xvda1 console=xvda1 ro" is odd. You want something like "root=/dev/xvda1 xencons=hvc console=hvc0" that might better let you see what is going on. Your domain is continually rebooting but since you are providing next to no information about what you are doing it is very hard for me to know if this is because you are rebooting it manually or if it is doing it itself. If you want to get useful help from a mailing list then you need to be precise about the actions you are performing and describe things clearly and fully. Unless you can do this then I''m not sure how much more help I can give. Ian.
On Tue, 2013-07-02 at 11:06 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Please find the attachment of console output."Command line: root=/dev/xvda1 xencons=xvda1 console=xvda1 ro" is odd. You want something like "root=/dev/xvda1 xencons=hvc console=hvc0" that might better let you see what is going on. Your domain is continually rebooting but since you are providing next to no information about what you are doing it is very hard for me to know if this is because you are rebooting it manually or if it is doing it itself. If you want to get useful help from a mailing list then you need to be precise about the actions you are performing and describe things clearly and fully. Unless you can do this then I''m not sure how much more help I can give. Ian.
Ian, Got any suggestion on my issue? Regards, SG -----Original Message----- From: Geetha, ANGLER - EIT [mailto:geetha@angleritech.com] Sent: Tuesday, July 02, 2013 2:15 PM To: ''Ian Campbell'' Cc: ''xen-users@lists.xen.org'' Subject: RE: [Xen-users] Amazon EC2+Slackware 14(64 bit) Ian, The instance is rebooting it self I think so... The below is the end of my console output.. There is no more Ian,,, [ 78.569862] xenbus_dev_shutdown: device/console/0: Initialising !Connected, skipping [ 78.890483] Restarting system. We are running servers in Amazon aws... I am working with slackware since 11.0 version (2008 to till date).... Now we need to update the slackware 13.7 to slackware 14 64 bit version. I''ve built the own kernel package of slackare and upload the server which I''ve sent the documentation in previous mail... I am trying a lot to set up the slackware 14 64 bit on Amazon aws.. I''ve changed the pv-grub kernel which bundle the image.. But no use.. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedkernels.html# UsingUserProvidedKernel I could not get into the slackware 14 as I followed the same steps of configuration in old versions.. This is my scenio Ian... Regards Geetha -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: Tuesday, July 02, 2013 2:24 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Tue, 2013-07-02 at 11:06 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Please find the attachment of console output."Command line: root=/dev/xvda1 xencons=xvda1 console=xvda1 ro" is odd. You want something like "root=/dev/xvda1 xencons=hvc console=hvc0" that might better let you see what is going on. Your domain is continually rebooting but since you are providing next to no information about what you are doing it is very hard for me to know if this is because you are rebooting it manually or if it is doing it itself. If you want to get useful help from a mailing list then you need to be precise about the actions you are performing and describe things clearly and fully. Unless you can do this then I''m not sure how much more help I can give. Ian.
On Tue, 2013-07-02 at 14:15 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > The instance is rebooting it self I think so... > > The below is the end of my console output.. There is no more Ian,,,Did you try adjusting your command line as I suggested? Unless doing that gives some hint then I''m afraid I am out of ideas.> I''ve built the own kernel package of slackareHave you tried with a known good kernel?
Ian, Thanks for the reply... I''ve changed the command line as you said.. I enabled the udev options (below mentioned) in config and uploaded the server, still getting an error. INIT: version 2.88 booting proc on /proc type proc (rw) [ 4.394948] mount used greatest stack depth: 4408 bytes left [ 4.413682] grep used greatest stack depth: 4400 bytes left sysfs on /sys type sysfs (rw) tmpfs on /run type tmpfs (rw,mode=0755) Sorry, but you need devtmpfs support in the kernel to use udev. Both of these options are needed: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y FATAL: Refusing to run /etc/rc.d/rc.udev. grep: /etc/hardwareclock: No such file or directory Setting system time from the hardware clock (localtime): hwclock: Cannot access the Hardware Clock via any known method. hwclock: Use the --debug option to see the details of our search for an access method. Tue Jul 2 12:10:46 Local time zone must be set--see zic manual page 2013 Testing root filesystem status: read-only filesystem Checking root filesystem: fsck from util-linux 2.21.2 /sbin/e2fsck: No such file or directory while trying to open /dev/xvda1 Possibly non-existent device? *********************************************************** *** An error occurred during the root filesystem check. *** *** You will now be given a chance to log into the *** *** system in single-user mode to fix the problem. *** *** *** *** If you are using the ext2 filesystem, running *** *** ''e2fsck -v -y <partition>'' might help. *** *********************************************************** Once you exit the single-user shell, the system will reboot. Type control-d to proceed with normal startup, (or give root password for system maintenance):Unmounting file systems. Rebooting system. [ 78.412771] xenbus_dev_shutdown: device/console/0: Initialising !Connected, skipping [ 79.027419] Restarting system. -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: Tuesday, July 02, 2013 3:29 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Tue, 2013-07-02 at 14:15 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > The instance is rebooting it self I think so... > > The below is the end of my console output.. There is no more Ian,,,Did you try adjusting your command line as I suggested? Unless doing that gives some hint then I''m afraid I am out of ideas.> I''ve built the own kernel package of slackareHave you tried with a known good kernel?
On Tue, 2013-07-02 at 17:55 +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Thanks for the reply... > > > I''ve changed the command line as you said.. > > > I enabled the udev options (below mentioned) in config and uploaded the > server, still getting an error.Did you read it (all of it)? Because it tells you exactly what you need to do.> > INIT: version 2.88 booting > proc on /proc type proc (rw) > [ 4.394948] mount used greatest stack depth: 4408 bytes left > [ 4.413682] grep used greatest stack depth: 4400 bytes left > sysfs on /sys type sysfs (rw) > tmpfs on /run type tmpfs (rw,mode=0755) > Sorry, but you need devtmpfs support in the kernel to use udev. > Both of these options are needed: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y > > FATAL: Refusing to run /etc/rc.d/rc.udev. > grep: /etc/hardwareclock: No such file or directory > Setting system time from the hardware clock (localtime): hwclock: Cannot > access the Hardware Clock via any known method. > hwclock: Use the --debug option to see the details of our search for an > access method. > Tue Jul 2 12:10:46 Local time zone must be set--see zic manual page 2013 > Testing root filesystem status: read-only filesystem > Checking root filesystem: > fsck from util-linux 2.21.2 > /sbin/e2fsck: No such file or directory while trying to open /dev/xvda1 > Possibly non-existent device? > > *********************************************************** > *** An error occurred during the root filesystem check. *** > *** You will now be given a chance to log into the *** > *** system in single-user mode to fix the problem. *** > *** *** > *** If you are using the ext2 filesystem, running *** > *** ''e2fsck -v -y <partition>'' might help. *** > *********************************************************** > > Once you exit the single-user shell, the system will reboot. > > > Type control-d to proceed with normal startup, > (or give root password for system maintenance):Unmounting file systems. > Rebooting system. > [ 78.412771] xenbus_dev_shutdown: device/console/0: Initialising !> Connected, skipping > [ 79.027419] Restarting system. > > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: Tuesday, July 02, 2013 3:29 PM > To: Geetha, ANGLER - EIT > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Tue, 2013-07-02 at 14:15 +0530, Geetha, ANGLER - EIT wrote: > > Ian, > > > > The instance is rebooting it self I think so... > > > > The below is the end of my console output.. There is no more Ian,,, > > Did you try adjusting your command line as I suggested? > > Unless doing that gives some hint then I''m afraid I am out of ideas. > > > I''ve built the own kernel package of slackare > > Have you tried with a known good kernel? > > >
On Tue, Jul 02, 2013 at 05:55:26PM +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Thanks for the reply... > > > I''ve changed the command line as you said.. > > > I enabled the udev options (below mentioned) in config and uploaded the > server, still getting an error. > > > INIT: version 2.88 booting > proc on /proc type proc (rw) > [ 4.394948] mount used greatest stack depth: 4408 bytes left > [ 4.413682] grep used greatest stack depth: 4400 bytes left > sysfs on /sys type sysfs (rw) > tmpfs on /run type tmpfs (rw,mode=0755) > Sorry, but you need devtmpfs support in the kernel to use udev. > Both of these options are needed: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y > > FATAL: Refusing to run /etc/rc.d/rc.udev.I think the above lines give you clear idea why udev didn''t run.> grep: /etc/hardwareclock: No such file or directory > Setting system time from the hardware clock (localtime): hwclock: Cannot > access the Hardware Clock via any known method. > hwclock: Use the --debug option to see the details of our search for an > access method. > Tue Jul 2 12:10:46 Local time zone must be set--see zic manual page 2013 > Testing root filesystem status: read-only filesystem > Checking root filesystem: > fsck from util-linux 2.21.2 > /sbin/e2fsck: No such file or directory while trying to open /dev/xvda1 > Possibly non-existent device? >And of course as udev didn''t run, it didn''t create the device node for you, so that you could not find xvda1.> *********************************************************** > *** An error occurred during the root filesystem check. *** > *** You will now be given a chance to log into the *** > *** system in single-user mode to fix the problem. *** > *** *** > *** If you are using the ext2 filesystem, running *** > *** ''e2fsck -v -y <partition>'' might help. *** > *********************************************************** > > Once you exit the single-user shell, the system will reboot. > > > Type control-d to proceed with normal startup, > (or give root password for system maintenance):Unmounting file systems. > Rebooting system. > [ 78.412771] xenbus_dev_shutdown: device/console/0: Initialising !> Connected, skipping > [ 79.027419] Restarting system. > > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: Tuesday, July 02, 2013 3:29 PM > To: Geetha, ANGLER - EIT > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Tue, 2013-07-02 at 14:15 +0530, Geetha, ANGLER - EIT wrote: > > Ian, > > > > The instance is rebooting it self I think so... > > > > The below is the end of my console output.. There is no more Ian,,, > > Did you try adjusting your command line as I suggested? > > Unless doing that gives some hint then I''m afraid I am out of ideas. > > > I''ve built the own kernel package of slackare > > Have you tried with a known good kernel? > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Hi Liu, Thanks for your suggestions. I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y and uploaded the server, but still getting the same error. I would compile the kernel with udev option and build the package and let me know. Regards, SG ----- Original Message ----- From: "Wei Liu" <wei.liu2@citrix.com> To: "ANGLER - EIT Geetha" <geetha@angleritech.com> Cc: "Ian Campbell" <Ian.Campbell@citrix.com>, xen-users@lists.xen.org, "wei liu2" <wei.liu2@citrix.com> Sent: Wednesday, July 3, 2013 1:56:03 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Tue, Jul 02, 2013 at 05:55:26PM +0530, Geetha, ANGLER - EIT wrote:> Ian, > > Thanks for the reply... > > > I''ve changed the command line as you said.. > > > I enabled the udev options (below mentioned) in config and uploaded the > server, still getting an error. > > > INIT: version 2.88 booting > proc on /proc type proc (rw) > [ 4.394948] mount used greatest stack depth: 4408 bytes left > [ 4.413682] grep used greatest stack depth: 4400 bytes left > sysfs on /sys type sysfs (rw) > tmpfs on /run type tmpfs (rw,mode=0755) > Sorry, but you need devtmpfs support in the kernel to use udev. > Both of these options are needed: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y > > FATAL: Refusing to run /etc/rc.d/rc.udev.I think the above lines give you clear idea why udev didn''t run.> grep: /etc/hardwareclock: No such file or directory > Setting system time from the hardware clock (localtime): hwclock: Cannot > access the Hardware Clock via any known method. > hwclock: Use the --debug option to see the details of our search for an > access method. > Tue Jul 2 12:10:46 Local time zone must be set--see zic manual page 2013 > Testing root filesystem status: read-only filesystem > Checking root filesystem: > fsck from util-linux 2.21.2 > /sbin/e2fsck: No such file or directory while trying to open /dev/xvda1 > Possibly non-existent device? >And of course as udev didn''t run, it didn''t create the device node for you, so that you could not find xvda1.> *********************************************************** > *** An error occurred during the root filesystem check. *** > *** You will now be given a chance to log into the *** > *** system in single-user mode to fix the problem. *** > *** *** > *** If you are using the ext2 filesystem, running *** > *** ''e2fsck -v -y <partition>'' might help. *** > *********************************************************** > > Once you exit the single-user shell, the system will reboot. > > > Type control-d to proceed with normal startup, > (or give root password for system maintenance):Unmounting file systems. > Rebooting system. > [ 78.412771] xenbus_dev_shutdown: device/console/0: Initialising != > Connected, skipping > [ 79.027419] Restarting system. > > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: Tuesday, July 02, 2013 3:29 PM > To: Geetha, ANGLER - EIT > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Tue, 2013-07-02 at 14:15 +0530, Geetha, ANGLER - EIT wrote: > > Ian, > > > > The instance is rebooting it self I think so... > > > > The below is the end of my console output.. There is no more Ian,,, > > Did you try adjusting your command line as I suggested? > > Unless doing that gives some hint then I''m afraid I am out of ideas. > > > I''ve built the own kernel package of slackare > > Have you tried with a known good kernel? > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, 2013-07-03 at 17:19 +0530, Geetha, ANGLER - EIT wrote:> Hi Liu, > > Thanks for your suggestions. > > I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y > CONFIG_DEVTMPFS_MOUNT=y > and uploaded the server, but still getting the same error.Yes, because those are kernel build options not command line options.> I would compile the kernel with udev option and build the package and > let me know.Yes, this is what you should do. Ian.
Hi Ian and Liu, I''ve bad luck... I done kernel compilation and uploaded the same... GNU GRUB version 0.97 (1740800K lower / 0K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grubdom> Thanks Sg ----- Original Message ----- From: "Ian Campbell" <Ian.Campbell@citrix.com> To: "ANGLER - EIT Geetha" <geetha@angleritech.com> Cc: "Wei Liu" <wei.liu2@citrix.com>, xen-users@lists.xen.org Sent: Wednesday, July 3, 2013 5:23:12 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Wed, 2013-07-03 at 17:19 +0530, Geetha, ANGLER - EIT wrote:> Hi Liu, > > Thanks for your suggestions. > > I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y > CONFIG_DEVTMPFS_MOUNT=y > and uploaded the server, but still getting the same error.Yes, because those are kernel build options not command line options.> I would compile the kernel with udev option and build the package and > let me know.Yes, this is what you should do. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, 2013-07-03 at 17:43 +0530, Geetha, ANGLER - EIT wrote:> Hi Ian and Liu, > > I''ve bad luck... > > I done kernel compilation and uploaded the same...This is now a completely different sort of error to the original error, and I don''t immediately know the answer. I suggest you try a websearch etc. If that fails then perhaps you can find someone locally within your organisation who can offer you better guidance, perhaps the person who initially selected and deployed slackware for your use case.> GNU GRUB version 0.97 (1740800K lower / 0K upper memory) > > [ Minimal BASH-like line editing is supported. For > the first word, TAB lists possible command > completions. Anywhere else TAB lists the possible > completions of a device/filename. ] > > grubdom> > > Thanks > Sg > > ----- Original Message ----- > From: "Ian Campbell" <Ian.Campbell@citrix.com> > To: "ANGLER - EIT Geetha" <geetha@angleritech.com> > Cc: "Wei Liu" <wei.liu2@citrix.com>, xen-users@lists.xen.org > Sent: Wednesday, July 3, 2013 5:23:12 PM GMT +05:30 Chennai, Kolkata, > Mumbai, New Delhi > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Wed, 2013-07-03 at 17:19 +0530, Geetha, ANGLER - EIT wrote: > > Hi Liu, > > > > Thanks for your suggestions. > > > > I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y > > CONFIG_DEVTMPFS_MOUNT=y > > and uploaded the server, but still getting the same error. > > Yes, because those are kernel build options not command line options. > > > I would compile the kernel with udev option and build the package > and > > let me know. > > Yes, this is what you should do. > > Ian. > > > >
On Wed, Jul 03, 2013 at 05:43:38PM +0530, Geetha, ANGLER - EIT wrote:> Hi Ian and Liu, > > I''ve bad luck... > > I done kernel compilation and uploaded the same... > > GNU GRUB version 0.97 (1740800K lower / 0K upper memory) > > [ Minimal BASH-like line editing is supported. For > the first word, TAB lists possible command > completions. Anywhere else TAB lists the possible > completions of a device/filename. ] >This is a configuration problem of your image, not a Xen problem. To be honest I don''t know why your grub went wrong. It didn''t even show grub menu? I''m afraid you''re on your own to figure it out. Wei.> grubdom> > > Thanks > Sg > > ----- Original Message ----- > From: "Ian Campbell" <Ian.Campbell@citrix.com> > To: "ANGLER - EIT Geetha" <geetha@angleritech.com> > Cc: "Wei Liu" <wei.liu2@citrix.com>, xen-users@lists.xen.org > Sent: Wednesday, July 3, 2013 5:23:12 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Wed, 2013-07-03 at 17:19 +0530, Geetha, ANGLER - EIT wrote: > > Hi Liu, > > > > Thanks for your suggestions. > > > > I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y > > CONFIG_DEVTMPFS_MOUNT=y > > and uploaded the server, but still getting the same error. > > Yes, because those are kernel build options not command line options. > > > I would compile the kernel with udev option and build the package and > > let me know. > > Yes, this is what you should do. > > Ian. > > >
Thanks for the reply.. I am working on this issue and web search too. I grateful to you both experts supporting me to sort out the issue so far... I would try my best.. Regards, Sg -----Original Message----- From: Wei Liu [mailto:wei.liu2@citrix.com] Sent: Wednesday, July 03, 2013 6:13 PM To: Geetha, ANGLER - EIT Cc: Ian Campbell; Wei Liu; xen-users@lists.xen.org Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) On Wed, Jul 03, 2013 at 05:43:38PM +0530, Geetha, ANGLER - EIT wrote:> Hi Ian and Liu, > > I''ve bad luck... > > I done kernel compilation and uploaded the same... > > GNU GRUB version 0.97 (1740800K lower / 0K upper memory) > > [ Minimal BASH-like line editing is supported. For the first word, TAB > lists possible command completions. Anywhere else TAB lists the > possible completions of a device/filename. ] >This is a configuration problem of your image, not a Xen problem. To be honest I don''t know why your grub went wrong. It didn''t even show grub menu? I''m afraid you''re on your own to figure it out. Wei.> grubdom> > > Thanks > Sg > > ----- Original Message ----- > From: "Ian Campbell" <Ian.Campbell@citrix.com> > To: "ANGLER - EIT Geetha" <geetha@angleritech.com> > Cc: "Wei Liu" <wei.liu2@citrix.com>, xen-users@lists.xen.org > Sent: Wednesday, July 3, 2013 5:23:12 PM GMT +05:30 Chennai, Kolkata, > Mumbai, New Delhi > Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit) > > On Wed, 2013-07-03 at 17:19 +0530, Geetha, ANGLER - EIT wrote: > > Hi Liu, > > > > Thanks for your suggestions. > > > > I''ve added the following options in /boot/config CONFIG_DEVTMPFS=y > > CONFIG_DEVTMPFS_MOUNT=y and uploaded the server, but still getting > > the same error. > > Yes, because those are kernel build options not command line options. > > > I would compile the kernel with udev option and build the package > > and let me know. > > Yes, this is what you should do. > > Ian. > > >