-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I did some configuration changes on a XenServer 5.6 (Which I believe is running CentOS 5.5 under the hood). After a reboot, the server failed to come back up. Connecting to the serial console, I see that it hangs right after setting hostname:
Setting hostname somehostname: [ OK ] INFO: task nash:5282 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task nash:5282 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
the last two lines keep repeating.
How can I get this server to boot up? Do I need to use a cd and go into rescue mode?
Any help would be greatly appreciated,
Russ
(2010/06/09 15:06), Ruslan Sivak wrote:
INFO: task nash:5282 blocked for more than 120 seconds.
some guy faces the same problem on citrix's forum. He find that he removes 2-sata disks, It's booting fine.
the nash(finding volumes in boot sequences) has many limits with boot device recognition.
resolution back to old kernel(5.5) rebuilding ramdisk(mkinitrd) with latest device driver.(if you have vendor/raid equipment) back to storage configurations.
changing grub/boot parameter with "noquiet" options show you debug messages. these message can let you change your booting conditions.
-Tsuyoshi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/9/2010 4:29 AM, Tsuyoshi Nagata wrote:
(2010/06/09 15:06), Ruslan Sivak wrote:
INFO: task nash:5282 blocked for more than 120 seconds.
some guy faces the same problem on citrix's forum. He find that he removes 2-sata disks, It's booting fine.
the nash(finding volumes in boot sequences) has many limits with boot device recognition.
resolution back to old kernel(5.5) rebuilding ramdisk(mkinitrd) with latest device driver.(if you have vendor/raid equipment) back to storage configurations.
changing grub/boot parameter with "noquiet" options show you debug messages. these message can let you change your booting conditions.
-Tsuyoshi
Thank you. I found the post, but it wasn't very helpful. I have only 2 drives in a raid 1, so removing them is not an option.
I'm pretty sure I know what's wrong, but I need to get into a shell to fix it.
I tried adding noquiet to the boot parameters, but it didn't seem to help. Am I doing it right?
Original boot line:
mboot.c32 /boot/xen.gz com1=115200,8n1 console=com1,vga dom0_mem=752M
lowmem_e mergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6-xen root=LABEL=root-j uaihdrs ro console=tty0 xencons=hvc console=hvc0 --- /boot/initrd-2.6-xen.img
Updated boot line:
mboot.c32 /boot/xen.gz com2=57600,8n1 console=com2,vga dom0_mem=752M
lowmem_em ergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6-xen root=LABEL=root-ju aihdrs ro console=tty0 xencons=hvc console=hvc0 noquiet --- /boot/initrd-2.6-xen .img
Russ
-
Ruslan Sivak -
Tsuyoshi Nagata