Hello Ryan,
Once again, I tried to re-imageunzip again after I read "Timothy
Ficarra's email about the imageunzip command issue". Previously, I did
not use the "\" back slash in my imageunzip command, because I thought
it was just a line change symbol. But this time, after I added the "\"
in:
sudo ssh pc1 imageunzip -s 1 - /dev/$DSK \ <
/usr/testbed/images/FBSD64-GENERIC.ndz
Then, I could see all the partitions as below:
# ls -l /dev/sda*
brw-rw---- 1 root disk 8, 0 Nov 10 16:39 /dev/sda
brw-r----- 1 root root 8, 1 Nov 10 16:36 /dev/sda1
brw-r----- 1 root root 8, 2 Nov 10 16:36 /dev/sda2
brw-r----- 1 root root 8, 3 Nov 10 16:36 /dev/sda3
brw-r----- 1 root root 8, 4 Nov 10 16:36 /dev/sda4
brw-r----- 1 root root 8, 5 Nov 10 16:36 /dev/sda5
brw-r----- 1 root root 8, 6 Nov 10 16:36 /dev/sda6
brw-r----- 1 root root 8, 7 Nov 10 16:36 /dev/sda7
brw-r----- 1 root root 8, 8 Nov 10 16:36 /dev/sda8
However, I still can't mount mount sda{5,7,8}:
# mount /dev/sda5 /mnt
mount: mounting /dev/sda5 on /mnt failed: No such file or directory
# mount /dev/sda7 /mnt/var
mount: mounting /dev/sda7 on /mnt/var failed: No such file or directory
# mount /dev/sda8 /mnt/usr
mount: mounting /dev/sda8 on /mnt/usr failed: No such file or directory
Those are just what I got for reference. Thanks.
Best Regards,
Cheng Cui
. Frey Computing Services Center . Baton Rouge, LA 70803
-----Original Message-----
From: Cheng Cui [mailto:ccui1@tigers.lsu.edu]
Sent: Monday, November 02, 2009 7:52 PM
To: 'Ryan Jackson'
Cc: 'Testbed-admins@flux.utah.edu'
Subject: RE: [Testbed-admins] Booting error in Customizing the Generic
Image
Ryan,
Thanks a lot for your reply.
My disk type under BSD is 'accd', so it is 'sda' under Linux. And I have
successfully imageunzipped both FreeBSD and Fedora images into the disk
partition 1 and 2, by using my DSK=sda.
However, after re-read the partition in linux MFS, it seems not to have
the expected /dev/sda{5,6,7,8}. My /dev has only 4 sda device files
which makes me unable to "mount /dev/${DSK}5 /mnt", see:
# ls -l /dev/sda*
brw-rw---- 1 root disk 8, 0 Nov 2 18:27 /dev/sda
brw-r----- 1 root root 8, 2 Nov 2 13:16 /dev/sda2
brw-r----- 1 root root 8, 3 Nov 2 13:16 /dev/sda3
brw-rw---- 1 root disk 8, 4 Nov 2 18:33 /dev/sda4
But my dmesg shows:
# dmesg | grep sda
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda: sda1
sda1: <bsd: sda5 sda6 sda7 sda8 sda9 >
sd 13:0:0:0: [sda] Attached SCSI removable disk
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda:
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda:
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda: sda4
sda4: <bsd:bad subpartition - ignored
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda: sda4
sda4: <bsd:bad subpartition - ignored
sd 13:0:0:0: [sda] 1146040320 512-byte hardware sectors (586773 MB)
sd 13:0:0:0: [sda] Write Protect is off
sd 13:0:0:0: [sda] Mode Sense: 06 00 10 00
sd 13:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports
DPO and FUA
sda: sda4
sda4: <bsd:bad subpartition - ignored
******************************************************************
Does the kernel support my RAID controller or SAS disks? Thanks.
Best Regards,
Cheng Cui
. Frey Computing Services Center . Baton Rouge, LA 70803
-----Original Message-----
From: 'Ryan Jackson' [mailto:rdjackso@flux.utah.edu]
Sent: Monday, November 02, 2009 2:49 PM
To: Cheng Cui
Cc: Testbed-admins@flux.utah.edu
Subject: Re: [Testbed-admins] Booting error in Customizing the Generic
Image
* Cheng Cui <ccui1@tigers.lsu.edu> [091102 12:40]:
What did you change, and what did you change it to?
I'm not sure I understand what you were able to get working and what
you weren't. It looks like the admin mfs works, but I am not clear
on
if you were able to actually load an image onto a node or not. Can
you clarify that for me?
I thought it was just some typo in your "create_linux_mfs_descriptors"
and those "grub.cfg" because your descriptor tells the database to
record the path='/frisbee_linux', not '/tftpboot/Frisbee_linux', and
so
in the grub.cfg. I just modified them correspondingly because I put
the
'frisbee_linux' under /tftpboot.
I guess it depends on how your tftpd is configured. The configuration
I sent you works here, so I'm a bit surprised it doesn't work for you
as-is. Regardless, I'm glad it's working now.
Now, the only problem I may have is how to customize a general image,
like Freebsd6.4 or Fedora8 under linux admin MFS. All the instructions
for doing this were based on FreeBSD MFS. I am not sure if those still
works under linux MFS. Would you please give some advice? Thanks a
lot.
Yes. There are a few changes you need to know about:
1. Make sure you know what FreeBSD will call your disk. Even if
you're using the Linux MFS, the Emulab code right now requires the
FreeBSD name to be stored in the database. When using the FreeBSD
MFS, this value is used as-is, but the Linux MFS must convert it to
something Linux understands. Generally, it will probably be called
'sda' under Linux so if you're not sure what FreeBSD calls it you can
use 'da0' as a default. Step 1 in "Customizing the Generic Image"
discusses how to make sure the correct value is specified in the
database. When the directions tell you to set the DSK environment
variable, use the correct Linux name for it and not the FreeBSD one if
you're using the Linux MFS.
2. The FreeBSD MFS will automatically detect the BSD disklabel when
you've loaded a FreeBSD image. Linux does not, so you will need to
tell the kernel to re-scan the partition table for that disk before
customizing FreeBSD. Right now the easiest way to do this from the
MFS is to run this command after you've finished step 1: 'hdparm -z
${DSK}'. If this doesn't work, use 'echo w | /sbin/fdisk ${DSK}'
instead.
3. Linux names FreeBSD partitions differently than FreeBSD does.
Under our standard partition layout, the following describes the
mapping between the FreeBSD name and the Linux name (assuming that
FreeBSD thinks your disk is /dev/da0 and Linux thinks it's /dev/sda):
/dev/da0s1a -> /dev/sda5 (mounts on /mnt)
/dev/da0s1b -> /dev/sda6 (do not mount (swap partition))
/dev/da0s1e -> /dev/sda7 (mounts on /mnt/var)
/dev/da0s1f -> /dev/sda8 (mounts on /mnt/usr)
So in step 2 (Customize FreeBSD) when it tells you to mount the
FreeBSD partitions, use the mapping above to mount them.
Some of our newer FreeBSD images don't have a FreeBSD swap partition,
but share the Linux swap partition. For those, the following map
would apply:
/dev/da0s1a -> /dev/sda5 (mounts on /mnt)
/dev/da0s1e -> /dev/sda6 (mounts on /mnt/var)
/dev/da0s1f -> /dev/sda7 (mounts on /mnt/usr)
I should probably automate this for at least the Linux MFS since its
device naming is somewhat less predictable than that of the FreeBSD
one.
Other than the above, the process should basically be the same.
I haven't run through the initial image customization yet using the
Linux MFS, although there's really no reason it shouldn't work. Make
sure that the Linux MFS recognizes your disk first. You can send me
the output of dmesg if it doesn't appear to be found (it'll probably
be recognized as /dev/sda).
Let me know if you have any further questions or problems.
_______________________________________________
Testbed-admins mailing list
Testbed-admins@flux.utah.edu
http://www.flux.utah.edu/mailman/listinfo/testbed-admins