Hello Ryan, For the test output: >If you could do the following tests I think I should be able to figure this out: > >1) Reboot into the admin MFS, capture the output of dmesg into a file, > and send it to me. Please refer to the attached file called 'dmesg_linux_adminMFS' >2) Write the generic image to the disk again but stop after you finish > runing the imgunzip command. Then run 'hdparm -z /dev/sda'. Send > me the output of that command (if any) plus any new dmesg output. The command output and the new dmesg output as attached 'dmesg_linux_adminMFS_after_hdparm' sudo ssh pc1 imageunzip -s 1 - /dev/$DSK < /usr/testbed/images/FBSD64-GENERIC.ndz Ignoring unknown relocation type 1 Wrote 3216052224 bytes (1316509184 actual) in 47 seconds 2546 max bufs, 18087936 max memory 2540 buffers split sudo ssh pc1 imageunzip -s 2 - /dev/$DSK < /usr/testbed/images/FEDORA8-STD.ndz Wrote 3216084480 bytes (1346203136 actual) in 46 seconds 727 max bufs, 19922944 max memory 722 buffers split # hdparm -z /dev/sda /dev/sda: re-reading partition table >3) Capture the output of '/sbin/fdisk -l -u /dev/sda' into a file and > send it to me. The output file is 'fdisk_linux_adminMFS' in the attachment. Thanks a lot. Best Regards, Cheng Cui . Frey Computing Services Center . Baton Rouge, LA 70803 -----Original Message----- From: 'Ryan Jackson' [mailto:rdjackso@flux.utah.edu] Sent: Tuesday, November 03, 2009 1:14 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 18:51]: > 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. Good, glad that worked for you (so far anyway). > 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 This is strange. The kernel clearly recognizes your disk, and from your dmesg output it initially sees a valid BSD disklabel on partition 1 with 5 sub partitions. Then later it sees something entirely different: only partition 4 with a bad BSD disklabel. This doesn't look right. Did you rescan the partition table using the hdparm command or fdisk? If you could do the following tests I think I should be able to figure this out: - Reboot into the admin MFS, capture the output of dmesg into a file, and send it to me. - Write the generic image to the disk again but stop after you finish runing the imgunzip command. Then run 'hdparm -z /dev/sda'. Send me the output of that command (if any) plus any new dmesg output. - Capture the output of '/sbin/fdisk -l -u /dev/sda' into a file and send it to me. Thanks.
Attachment:
dmesg_linux_adminMFS
Description: Binary data
Attachment:
dmesg_linux_adminMFS_after_hdparm
Description: Binary data
Attachment:
fdisk_linux_adminMFS
Description: Binary data