[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.deThu Aug 20 11:06:07 PDT 2009
- Previous message: [Beowulf] amd 3 and 6 core processors
- Next message: [Beowulf] moving of Linux HDD to other node: udev problem at boot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 20.08.2009 um 19:33 schrieb Mikhail Kuzminsky: > In message from Reuti <reuti at staff.uni-marburg.de> (Thu, 20 Aug > 2009 19:02:49 +0200): >> Am 20.08.2009 um 16:29 schrieb Mikhail Kuzminsky: >> >>> In message from Reuti <reuti at staff.uni-marburg.de> (Wed, 19 Aug >>> 2009 21:07:19 +0200): >>> >>>> 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? >>> >>> At the moment of problem /etc/fstab, as I understand, isn't >>> used. And /dev/sda* files are not created by udev :-( >> >> Is it the same motherboard/chipset in both machines? > > Of course, no - taking into account that one ("source" w/10.3) is w/ > Opteron 2350, and 2nd is based on Nehalem :-) > >> You might need a different initrd otherwise. > > AFAIK, initrd (as the kernel itself) is "universal" for EM64T/x86-64, The problem is not the type of CPU, but the chipset (i.e. the necessary kernel module) with which the HDD is accessed. -- Reuti
- Previous message: [Beowulf] amd 3 and 6 core processors
- 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
