From: cyberdork33 <cyb...@gm...> - 2010-04-21 14:28:56
|
parted is capable of printing the GPT information fdisk cannot read the GPT, so will tell you what the MBR table contains. From your output, it seems you are indeed have a GPT. A utility called 'gptsync' may help you if your MBR table doesn't match. It comes with rEFIt, and I know that it is available as a package in Ubuntu, but I am unsure where to obtain it for RH. On Apr 21, 2010, at 9:20 AM, Geoffrey wrote: > cyberdork33 wrote: >> Are you sure that you Partition Label is "/" ? Maybe you can change >> your kernel line to have root=/dev/sdXX instead of using the label. > > I'll give that a go. > >> What does your Partition Table Look like? Are the GPT and MBR table >> out-of-sync? > > How would I know? > > Model: ATA Hitachi HTS72202 (scsi) > Disk /dev/sda: 200GB > Sector size (logical/physical): 512B/512B > Partition Table: gpt > > Number Start End Size File system Name Flags > 1 20.5kB 210MB 210MB fat32 EFI System Partition boot > 2 210MB 98.9GB 98.7GB hfs+ Untitled > 4 99.0GB 109GB 10.3GB linux-swap > 3 109GB 109GB 105MB ext3 boot > 5 109GB 141GB 31.5GB ext3 > 6 141GB 162GB 21.0GB ext3 > 7 162GB 178GB 15.7GB ext3 > 8 178GB 193GB 15.7GB ext3 > 9 193GB 200GB 6712MB ext3 > >> On Apr 21, 2010, at 9:03 AM, Geoffrey wrote: >>> Geoffrey wrote: >>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>> still get a panic, although it is a different message: >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >>>> Here are my grub entries. The first is the new kernel, the >>>> second is my current working kernel. >>>> title Red Hat Enterprise Linux Client (2.6.33.2) root (hd0,2) kernel /vmlinuz-2.6.33.2 ro root=LABEL=/ irqpoll rhgb initrd >>>> /initrd-2.6.33.2.img title Red Hat Enterprise Linux Client >>>> (2.6.18-194.el5) root (hd0,2) kernel /vmlinuz-2.6.18-194.el5 ro >>>> root=LABEL=/ irqpoll rhgb quiet initrd /initrd-2.6.18-194.el5.img >>>> I still wonder if the fact that file returns different info about >>>> my current working kernel and this new kernel has anything to do >>>> with this issue? >>>> boot> file vmlinuz-2.6.33.2 vmlinuz-2.6.1 vmlinuz-2.6.33.2: >>>> Linux kernel x86 boot executable RO-rootFS, root_dev 0x808, >>>> swap_dev 0x3, Normal VGA vmlinuz-2.6.18-194.el5: ELF 64-bit LSB >>>> shared object, AMD x86-64, version 1, stripped >>> Googling this keeps pointing to the lack of file system support, >>> but I've got it in my config: >>> CONFIG_EXT3_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # >>> CONFIG_EXT3_FS_SECURITY is not set >>> -- Until later, Geoffrey >>> "I predict future happiness for America if they can prevent the >>> government from wasting the labors of the people under the pretense >>> of taking care of them." - Thomas Jefferson >>> ------------------------------------------------------------------------------ >>> _______________________________________________ Mactel-linux-users >>> mailing list Mac...@li... https://lists.sourceforge.net/lists/listinfo/mactel-linux-users >> ------------------------------------------------------------------------------ >> _______________________________________________ Mactel-linux-users >> mailing list Mac...@li... https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > > -- > Until later, Geoffrey > > "I predict future happiness for America if they can prevent > the government from wasting the labors of the people under > the pretense of taking care of them." > - Thomas Jefferson |