[Beowulf] moving of Linux HDD to other node: udev problem at boot
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Reuti reuti at staff.uni-marburg.deWed Aug 19 12:07:19 PDT 2009
- Previous message: [Beowulf] moving of Linux HDD to other node: udev problem at boot
- Next message: [Beowulf] moving of Linux HDD to other node: udev problem at boot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 19.08.2009 um 19:12 schrieb Mikhail Kuzminsky: > As it was discussed here, there are NUMA problems w/Nehalem on a > set of Linux distributions/kernels. I was informed that may be old > OpenSuSE 10.3 default kernel (2.6.22) works w/Nehalem OK in the > sense of NUMA, i.e. gives right /sys/devices/system/node content. > > I moved Western Digital SATA HDD w/SuSE 10.3 installed (on dual > Barcelona server) to dual Nehalem server (master HDD on Nehalem > server) with Supermicro X8DTi mobo. > > But loading of SuSE 10.3 on Nehalem server was not successful. Grub > loader (which menu.lst configuration uses "by-id" identification of > disk partitions) works OK. But linux kernel booting didn't finish > successfully: /boot/04-udev.sh script (which task is udev > initialization) - I think, it's from initrd content - do not see > root partition (1st partition on HDD) ! > At the boot I see the messages > .... > SCSI subsystem initialized > ACPI Exception (processor_core_0787): Processor device isn't present > .... > <a set of messages about usb> > ... > Trying manual resume from /dev/sda2 /* it's > swap partition*/ > resume device /dev/sda2 not found (ignoring) There might be an entry "append resume=..." either in lilo.conf or grub's menu.lst > ... > Waiting for device /dev/disk/by-id/scsi-SATA-WDC_WD<name_of_disk>- > part1 ... /* echo from udev.sh */ Maybe the disk id is different form the one recored in /etc/fstab. What about using plain /dev/sda1 or alike, or mounting by volume label? -- Reuti > > and then the proposal to try again. After finish of this script I > don't see any HDDs in /dev. > > > BIOS setting for this SATA device is "enhanced". "compatible" mode > gives the same result. > > What may be the source of the problem ? May be HDD driver used by > initrd ? > Mikhail Kuzminsky > Computer Assistance to Chemical Research Center > Zelinsky Institute of Organic Chemistry RAS > Moscow > PS. If I see (after finish of udev.sh script) the content of /sys > - it's right in NUMA sense, i.e. > /sys/devices/system/node contains normal node0 and node1. > > _______________________________________________ > Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin > Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf
- Previous message: [Beowulf] moving of Linux HDD to other node: udev problem at boot
- Next message: [Beowulf] moving of Linux HDD to other node: udev problem at boot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
