From: Geoffrey M. <li...@se...> - 2010-04-16 14:34:40
|
I was attempting to upgrade my kernel and now when I boot, I get: grub That's it. I don't understand this as I don't know what the kernel update would do that would cause this to happen. My steps: 1. download kernel from kernel.org 2. unpack 3. configure 4. make modules 5. make 6. make modules_install 7. make install 8. reboot Any suggestions would be greatly appreciated. -- until later, Geof |
From: Justin P. m. <jus...@gm...> - 2010-04-16 14:48:28
|
On 04/16/2010 07:34 AM, Geoffrey Myers wrote: > I was attempting to upgrade my kernel and now when I boot, I get: > > grub > > > That's it. I don't understand this as I don't know what the kernel update would do that would cause this to happen. My steps: > > 1. download kernel from kernel.org > 2. unpack > 3. configure > 4. make modules > 5. make > 6. make modules_install > 7. make install > 8. reboot > > Any suggestions would be greatly appreciated. > > -- > until later, Geof > > if you just get the grub screen and no movement likely tell's me you need to do and update-grub or if using lilo /sbin/lilo which updates the kernel's etc.. as for the building of the kernel you should make menuconfig make make modules(although you probably don't because its already done) make modules_install make install(if using lilo, the update automatically happens) grub you need to update-grub hope this helps Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-16 15:37:11
|
cyberdork33 wrote: > It sounds like GRUB stage 1 lost track of where the stage 2 files > are. > > http://www.gnu.org/software/grub/manual/html_node/Installing-GRUB-natively.html#Installing-GRUB-natively > Okay, got grub reinstalled and booting to original kernel. Now I get the following when I attempt to boot the new kernel: mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.33.2 #1 Call Trace: . . > > On Apr 16, 2010, at 9:34 AM, Geoffrey Myers wrote: > >> I was attempting to upgrade my kernel and now when I boot, I get: >> >> grub >> >> >> That's it. I don't understand this as I don't know what the kernel >> update would do that would cause this to happen. My steps: >> >> 1. download kernel from kernel.org 2. unpack 3. configure 4. make >> modules 5. make 6. make modules_install 7. make install 8. reboot >> >> Any suggestions would be greatly appreciated. >> >> -- until later, Geof >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval Try the new software >> tools for yourself. Speed compiling, find bugs proactively, and >> fine-tune applications for parallel performance. See why Intel >> Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ 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 |
From: Justin P. m. <jus...@gm...> - 2010-04-16 16:16:23
|
On 04/16/2010 08:37 AM, Geoffrey wrote: > cyberdork33 wrote: >> It sounds like GRUB stage 1 lost track of where the stage 2 files >> are. >> >> http://www.gnu.org/software/grub/manual/html_node/Installing-GRUB-natively.html#Installing-GRUB-natively >> > > Okay, got grub reinstalled and booting to original kernel. Now I get > the following when I attempt to boot the new kernel: > > mount: could not find filesystem '/dev/root' > Setting up other filesystems. > Setting up new root fs > setuproot: moving /dev failed: No such file or directory > no fstab.sys, mounting internal defaults > setuproot: error mounting /proc: No such file or directory > setuproot: error mounting /sys: No such file or directory > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init! > Pid: 1, comm: init Not tainted 2.6.33.2 #1 > Call Trace: > . > never have seen this before.. doing a quick google gave me this: http://www.linuxquestions.org/questions/fedora-installation-39/fc6-mount-could-not-find-filesystem-dev-root-497332/ looking through the thread it seems it's the uuid of the device(but could be wrong). check /boot/grub/* and /etc/fstab to make sure the device is set correctly, also check in your .config that ext2/3/4(whatever your filesystem is that you build the module in the kernel i.g. y" instead of "m". (but looking at the error that might not be the case). Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 13:55:47
|
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 -- 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 |
From: Geoffrey <li...@se...> - 2010-04-21 14:04:00
|
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 |
From: cyberdork33 <cyb...@gm...> - 2010-04-21 14:08:08
|
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. What does your Partition Table Look like? Are the GPT and MBR table out-of-sync? 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 |
From: Geoffrey <li...@se...> - 2010-04-21 14:28:22
|
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. That label works for my current working kernel. > > What does your Partition Table Look like? Are the GPT and MBR table > out-of-sync? > > 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 |
From: Geoffrey <li...@se...> - 2010-04-21 14:20:40
|
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 |
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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 15:36:10
|
On 04/21/2010 06:55 AM, 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) > > check your /etc/fstab and make sure that it's /dev/sda* instead of /dev/hda* (if your using the older ati-piix it's should be /dev/hda* but using the new ati-piix it's /dev/sda*)but could be wrong). Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 16:11:53
|
Justin P. Mattock wrote: > On 04/21/2010 06:55 AM, 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) >> >> > > check your /etc/fstab and make sure > that it's /dev/sda* instead of /dev/hda* > (if your using the older ati-piix it's should > be /dev/hda* but using the new ati-piix it's > /dev/sda*)but could be wrong). Actually it's using the LABEL nomenclature, do you think this could be my problem? LABEL=/ / ext3 defaults 1 1 > > Justin P. Mattock > > ------------------------------------------------------------------------------ > _______________________________________________ > 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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 16:15:46
|
On 04/21/2010 09:11 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 06:55 AM, 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) >>> >>> >> >> check your /etc/fstab and make sure >> that it's /dev/sda* instead of /dev/hda* >> (if your using the older ati-piix it's should >> be /dev/hda* but using the new ati-piix it's >> /dev/sda*)but could be wrong). > > Actually it's using the LABEL nomenclature, do you think this could be > my problem? > > LABEL=/ / ext3 defaults 1 1 > > could be.. here's what I have: cat /etc/fstab # file system mount-point type options dump fsck # order /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 /dev/sda4 swap swap pri=1 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 devpts /dev/pts devpts gid=4,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 #none /selinux selinuxfs defaults 0 0 # End /etc/fstab does changing LABEL=/ to your device do anything? Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 16:30:32
|
Justin P. Mattock wrote: > On 04/21/2010 09:11 AM, Geoffrey wrote: >> Justin P. Mattock wrote: >>> On 04/21/2010 06:55 AM, 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) >>>> >>>> >>> >>> check your /etc/fstab and make sure >>> that it's /dev/sda* instead of /dev/hda* >>> (if your using the older ati-piix it's should >>> be /dev/hda* but using the new ati-piix it's >>> /dev/sda*)but could be wrong). >> >> Actually it's using the LABEL nomenclature, do you think this could be >> my problem? >> >> LABEL=/ / ext3 defaults 1 1 >> >> > > could be.. > here's what I have: > cat /etc/fstab > > # file system mount-point type options dump fsck > # order > > /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr > 1 1 > /dev/sda4 swap swap pri=1 0 0 > /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 > 0 0 > proc /proc proc defaults 0 0 > sysfs /sys sysfs defaults 0 0 > devpts /dev/pts devpts gid=4,mode=620 0 0 > tmpfs /dev/shm tmpfs defaults 0 0 > #none /selinux selinuxfs defaults 0 0 > # End /etc/fstab > > does changing LABEL=/ to your device do anything? Just tried that, no difference. > > Justin P. Mattock > -- 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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 16:40:10
|
On 04/21/2010 09:30 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:11 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 06:55 AM, 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) >>>>> >>>>> >>>> >>>> check your /etc/fstab and make sure >>>> that it's /dev/sda* instead of /dev/hda* >>>> (if your using the older ati-piix it's should >>>> be /dev/hda* but using the new ati-piix it's >>>> /dev/sda*)but could be wrong). >>> >>> Actually it's using the LABEL nomenclature, do you think this could be >>> my problem? >>> >>> LABEL=/ / ext3 defaults 1 1 >>> >>> >> >> could be.. >> here's what I have: >> cat /etc/fstab >> >> # file system mount-point type options dump fsck >> # order >> >> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >> /dev/sda4 swap swap pri=1 0 0 >> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >> proc /proc proc defaults 0 0 >> sysfs /sys sysfs defaults 0 0 >> devpts /dev/pts devpts gid=4,mode=620 0 0 >> tmpfs /dev/shm tmpfs defaults 0 0 >> #none /selinux selinuxfs defaults 0 0 >> # End /etc/fstab >> >> does changing LABEL=/ to your device do anything? > > Just tried that, no difference. > >> >> Justin P. Mattock >> > > hm.. I'm wondering if your hitting something with grub and the kernel i.g. I remember hitting something similar because I had no bzimage just raw make install vmlinuz(ended up having to upgrade to grub2 so that grub(*) was able to read the extra bits and so forth or something in that area). Also hit another issue similar as well with PCI_MMCONFIG [=y] (but this could already be fixed). Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 16:57:57
|
Justin P. Mattock wrote: > On 04/21/2010 09:30 AM, Geoffrey wrote: >> Justin P. Mattock wrote: >>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>> Justin P. Mattock wrote: >>>>> On 04/21/2010 06:55 AM, 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) >>>>>> >>>>>> >>>>> >>>>> check your /etc/fstab and make sure >>>>> that it's /dev/sda* instead of /dev/hda* >>>>> (if your using the older ati-piix it's should >>>>> be /dev/hda* but using the new ati-piix it's >>>>> /dev/sda*)but could be wrong). >>>> >>>> Actually it's using the LABEL nomenclature, do you think this could be >>>> my problem? >>>> >>>> LABEL=/ / ext3 defaults 1 1 >>>> >>>> >>> >>> could be.. >>> here's what I have: >>> cat /etc/fstab >>> >>> # file system mount-point type options dump fsck >>> # order >>> >>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>> /dev/sda4 swap swap pri=1 0 0 >>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>> proc /proc proc defaults 0 0 >>> sysfs /sys sysfs defaults 0 0 >>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>> tmpfs /dev/shm tmpfs defaults 0 0 >>> #none /selinux selinuxfs defaults 0 0 >>> # End /etc/fstab >>> >>> does changing LABEL=/ to your device do anything? >> >> Just tried that, no difference. >> >>> >>> Justin P. Mattock >>> >> >> > > hm.. I'm wondering if your hitting something > with grub and the kernel i.g. I remember hitting something > similar because I had no bzimage just raw make install > vmlinuz(ended up having to upgrade to grub2 so that grub(*) > was able to read the extra bits and so forth or something > in that area). > > Also hit another issue similar as well with > PCI_MMCONFIG [=y] > (but this could already be fixed). I changed my grub entry for root from: root=LABEL=/ to root=/dev/sda8 Now I get a spontaneous reboot. I tried to snap a photo of it before it reboot, but it's blurred. I'll try again. Weird thing is that it says something about wacom driver and then a reference to reiserfs or some such. I don't know what the wacom driver would have to do with reiserfs, but I'm not using reiserfs anyway. > > Justin P. Mattock > -- 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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 17:23:30
|
On 04/21/2010 09:57 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:30 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>> Justin P. Mattock wrote: >>>>>> On 04/21/2010 06:55 AM, 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) >>>>>>> >>>>>>> >>>>>> >>>>>> check your /etc/fstab and make sure >>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>> (if your using the older ati-piix it's should >>>>>> be /dev/hda* but using the new ati-piix it's >>>>>> /dev/sda*)but could be wrong). >>>>> >>>>> Actually it's using the LABEL nomenclature, do you think this could be >>>>> my problem? >>>>> >>>>> LABEL=/ / ext3 defaults 1 1 >>>>> >>>>> >>>> >>>> could be.. >>>> here's what I have: >>>> cat /etc/fstab >>>> >>>> # file system mount-point type options dump fsck >>>> # order >>>> >>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>> /dev/sda4 swap swap pri=1 0 0 >>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>> proc /proc proc defaults 0 0 >>>> sysfs /sys sysfs defaults 0 0 >>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>> #none /selinux selinuxfs defaults 0 0 >>>> # End /etc/fstab >>>> >>>> does changing LABEL=/ to your device do anything? >>> >>> Just tried that, no difference. >>> >>>> >>>> Justin P. Mattock >>>> >>> >>> >> >> hm.. I'm wondering if your hitting something >> with grub and the kernel i.g. I remember hitting something >> similar because I had no bzimage just raw make install >> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >> was able to read the extra bits and so forth or something >> in that area). >> >> Also hit another issue similar as well with >> PCI_MMCONFIG [=y] >> (but this could already be fixed). > > I changed my grub entry for root from: > > root=LABEL=/ > > to > > root=/dev/sda8 > > Now I get a spontaneous reboot. I tried to snap a photo of it before it > reboot, but it's blurred. I'll try again. Weird thing is that it says > something about wacom driver and then a reference to reiserfs or some > such. I don't know what the wacom driver would have to do with reiserfs, > but I'm not using reiserfs anyway. > > so changing your grub at-least takes care of the unable to find VFS thing?! and now the system boots up, and then instantly reboot's? I have seen reports of things like that, but have never hit something like that(if you can try early debugging with a remote machine to grab dmesg) Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 18:36:07
|
Justin P. Mattock wrote: > On 04/21/2010 09:57 AM, Geoffrey wrote: >> Justin P. Mattock wrote: >>> On 04/21/2010 09:30 AM, Geoffrey wrote: >>>> Justin P. Mattock wrote: >>>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>>> Justin P. Mattock wrote: >>>>>>> On 04/21/2010 06:55 AM, 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) >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> check your /etc/fstab and make sure >>>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>>> (if your using the older ati-piix it's should >>>>>>> be /dev/hda* but using the new ati-piix it's >>>>>>> /dev/sda*)but could be wrong). >>>>>> >>>>>> Actually it's using the LABEL nomenclature, do you think this >>>>>> could be >>>>>> my problem? >>>>>> >>>>>> LABEL=/ / ext3 defaults 1 1 >>>>>> >>>>>> >>>>> >>>>> could be.. >>>>> here's what I have: >>>>> cat /etc/fstab >>>>> >>>>> # file system mount-point type options dump fsck >>>>> # order >>>>> >>>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>>> /dev/sda4 swap swap pri=1 0 0 >>>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>>> proc /proc proc defaults 0 0 >>>>> sysfs /sys sysfs defaults 0 0 >>>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>>> #none /selinux selinuxfs defaults 0 0 >>>>> # End /etc/fstab >>>>> >>>>> does changing LABEL=/ to your device do anything? >>>> >>>> Just tried that, no difference. >>>> >>>>> >>>>> Justin P. Mattock >>>>> >>>> >>>> >>> >>> hm.. I'm wondering if your hitting something >>> with grub and the kernel i.g. I remember hitting something >>> similar because I had no bzimage just raw make install >>> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >>> was able to read the extra bits and so forth or something >>> in that area). >>> >>> Also hit another issue similar as well with >>> PCI_MMCONFIG [=y] >>> (but this could already be fixed). >> >> I changed my grub entry for root from: >> >> root=LABEL=/ >> >> to >> >> root=/dev/sda8 >> >> Now I get a spontaneous reboot. I tried to snap a photo of it before it >> reboot, but it's blurred. I'll try again. Weird thing is that it says >> something about wacom driver and then a reference to reiserfs or some >> such. I don't know what the wacom driver would have to do with reiserfs, >> but I'm not using reiserfs anyway. >> >> > > so changing your grub at-least takes care of the unable to find > VFS thing?! > and now the system boots up, and then instantly > reboot's? I have seen reports of things like that, > but have never hit something like that(if you can try early debugging > with a remote machine to grab dmesg) Not exactly sure how to go about that. I will try to video the boot process so I can provide better info. > > Justin P. Mattock > -- 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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 18:59:58
|
On 04/21/2010 11:35 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:57 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 09:30 AM, Geoffrey wrote: >>>>> Justin P. Mattock wrote: >>>>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>>>> Justin P. Mattock wrote: >>>>>>>> On 04/21/2010 06:55 AM, 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) >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> check your /etc/fstab and make sure >>>>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>>>> (if your using the older ati-piix it's should >>>>>>>> be /dev/hda* but using the new ati-piix it's >>>>>>>> /dev/sda*)but could be wrong). >>>>>>> >>>>>>> Actually it's using the LABEL nomenclature, do you think this >>>>>>> could be >>>>>>> my problem? >>>>>>> >>>>>>> LABEL=/ / ext3 defaults 1 1 >>>>>>> >>>>>>> >>>>>> >>>>>> could be.. >>>>>> here's what I have: >>>>>> cat /etc/fstab >>>>>> >>>>>> # file system mount-point type options dump fsck >>>>>> # order >>>>>> >>>>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>>>> /dev/sda4 swap swap pri=1 0 0 >>>>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>>>> proc /proc proc defaults 0 0 >>>>>> sysfs /sys sysfs defaults 0 0 >>>>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>>>> #none /selinux selinuxfs defaults 0 0 >>>>>> # End /etc/fstab >>>>>> >>>>>> does changing LABEL=/ to your device do anything? >>>>> >>>>> Just tried that, no difference. >>>>> >>>>>> >>>>>> Justin P. Mattock >>>>>> >>>>> >>>>> >>>> >>>> hm.. I'm wondering if your hitting something >>>> with grub and the kernel i.g. I remember hitting something >>>> similar because I had no bzimage just raw make install >>>> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >>>> was able to read the extra bits and so forth or something >>>> in that area). >>>> >>>> Also hit another issue similar as well with >>>> PCI_MMCONFIG [=y] >>>> (but this could already be fixed). >>> >>> I changed my grub entry for root from: >>> >>> root=LABEL=/ >>> >>> to >>> >>> root=/dev/sda8 >>> >>> Now I get a spontaneous reboot. I tried to snap a photo of it before it >>> reboot, but it's blurred. I'll try again. Weird thing is that it says >>> something about wacom driver and then a reference to reiserfs or some >>> such. I don't know what the wacom driver would have to do with reiserfs, >>> but I'm not using reiserfs anyway. >>> >>> >> >> so changing your grub at-least takes care of the unable to find >> VFS thing?! >> and now the system boots up, and then instantly >> reboot's? I have seen reports of things like that, >> but have never hit something like that(if you can try early debugging >> with a remote machine to grab dmesg) > > Not exactly sure how to go about that. I will try to video the boot > process so I can provide better info. > I usually use the ohci1394_dma=early boot option via firwire. that is if the machine crashes early I can see whats going on. (hopefully) In your case you probably already have dmesg since the machine starts up(if this is the case), and then after done with everything reboots(saving the log file (but could be wrong)). also looking through bugzilla I think your hitting this: https://bugzilla.kernel.org/show_bug.cgi?id=14952 (maybe revert this commit and see if you boot up) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=patch;h=1373411ae4cd0caf2e1a35fb801dd9a00b64dea2 Justin P. Mattock |
From: Justin P. M. <jus...@gm...> - 2010-04-21 19:09:41
|
are you sure your not using winxp? http://www.huffingtonpost.com/2010/04/21/mcafee-windows-xp-update-_n_546422.html (just messn!!) Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 19:54:33
|
Justin P. Mattock wrote: > are you sure your not using winxp? > http://www.huffingtonpost.com/2010/04/21/mcafee-windows-xp-update-_n_546422.html No, but I'm not using Mcafee... :))))) > > > (just messn!!) > > Justin P. Mattock > -- 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 |
From: Geoffrey <li...@se...> - 2010-04-21 14:27:40
|
Justin P. mattock wrote: > On 04/16/2010 07:34 AM, Geoffrey Myers wrote: >> I was attempting to upgrade my kernel and now when I boot, I get: >> >> grub >> >> >> That's it. I don't understand this as I don't know what the kernel update would do that would cause this to happen. My steps: >> >> 1. download kernel from kernel.org >> 2. unpack >> 3. configure >> 4. make modules >> 5. make >> 6. make modules_install >> 7. make install >> 8. reboot >> >> Any suggestions would be greatly appreciated. >> >> -- >> until later, Geof >> >> > > if you just get the grub screen and no movement > likely tell's me you need to do and update-grub > or if using lilo /sbin/lilo which updates the kernel's > etc.. > > as for the building of the kernel > you should > make menuconfig > make > make modules(although you probably don't because its already done) > make modules_install > make install(if using lilo, the update automatically happens) > grub you need to update-grub So when I run 'make install' I see this: WARNING: No module ehci-hcd found for kernel 2.6.33.2, continuing anyway WARNING: No module ohci-hcd found for kernel 2.6.33.2, continuing anyway WARNING: No module uhci-hcd found for kernel 2.6.33.2, continuing anyway WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway But in my kernel config I have: CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB_UHCI_HCD=y CONFIG_ATA_PIIX=y Is this an issue? > > hope this helps > > Justin P. Mattock > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > 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 |
From: Justin P. M. <jus...@gm...> - 2010-04-21 15:33:18
|
On 04/21/2010 07:27 AM, Geoffrey wrote: > Justin P. mattock wrote: >> On 04/16/2010 07:34 AM, Geoffrey Myers wrote: >>> I was attempting to upgrade my kernel and now when I boot, I get: >>> >>> grub >>> >>> >>> That's it. I don't understand this as I don't know what the kernel >>> update would do that would cause this to happen. My steps: >>> >>> 1. download kernel from kernel.org >>> 2. unpack >>> 3. configure >>> 4. make modules >>> 5. make >>> 6. make modules_install >>> 7. make install >>> 8. reboot >>> >>> Any suggestions would be greatly appreciated. >>> >>> -- >>> until later, Geof >>> >>> >> >> if you just get the grub screen and no movement >> likely tell's me you need to do and update-grub >> or if using lilo /sbin/lilo which updates the kernel's >> etc.. >> >> as for the building of the kernel >> you should >> make menuconfig >> make >> make modules(although you probably don't because its already done) >> make modules_install >> make install(if using lilo, the update automatically happens) >> grub you need to update-grub > > So when I run 'make install' I see this: > > WARNING: No module ehci-hcd found for kernel 2.6.33.2, continuing anyway > WARNING: No module ohci-hcd found for kernel 2.6.33.2, continuing anyway > WARNING: No module uhci-hcd found for kernel 2.6.33.2, continuing anyway > WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway > WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway > WARNING: No module ata_piix found for kernel 2.6.33.2, continuing anyway > > But in my kernel config I have: > > CONFIG_USB_ARCH_HAS_OHCI=y > CONFIG_USB_ARCH_HAS_EHCI=y > CONFIG_USB_UHCI_HCD=y > CONFIG_ATA_PIIX=y > > Is this an issue? > yeah it's just grub not realizing that the module is there it's just built-in the kernel. you should be o.k. Justin P. Mattock |