Re: Reading later boot files failed
Thanks a lot ! 2011/2/27 Camaleón > On Mon, 28 Feb 2011 03:08:39 +0800, waterloo wrote: > > > 2011/2/28 Camaleón > > > >> On Mon, 28 Feb 2011 02:02:16 +0800, waterloo wrote: > >> > >> > Mon Feb 28 01:57:45 2011: Reading early boot files > >> > >> A quick Google search returns that this message can be related to > >> "readahead" (or "readahead-fedora") package. Do you have it installed? > > > Yes , I install readahead-fedora . > > How to make readahead-fedora work correctly ? Thanks a lot ! > > To be sincere, I don't even know what is that package intended for (this > is the first time I see it). But if you have it in your system it must be > for something, right? I think it is not installed by default ;-) > > There must be information on how this daemon works in the manual or > README file and if you don't need it, you can disable it via "/etc/ > default/readahead-fedora" file. > > Greetings, > > -- > Camaleón > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/pan.2011.02.27.19.22...@gmail.com > >
Re: Reading later boot files failed
On Mon, 28 Feb 2011 03:08:39 +0800, waterloo wrote: > 2011/2/28 Camaleón > >> On Mon, 28 Feb 2011 02:02:16 +0800, waterloo wrote: >> >> > Mon Feb 28 01:57:45 2011: Reading early boot files >> >> A quick Google search returns that this message can be related to >> "readahead" (or "readahead-fedora") package. Do you have it installed? > Yes , I install readahead-fedora . > How to make readahead-fedora work correctly ? Thanks a lot ! To be sincere, I don't even know what is that package intended for (this is the first time I see it). But if you have it in your system it must be for something, right? I think it is not installed by default ;-) There must be information on how this daemon works in the manual or README file and if you don't need it, you can disable it via "/etc/ default/readahead-fedora" file. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.27.19.22...@gmail.com
Re: Reading later boot files failed
Yes , I install readahead-fedora . How to make readahead-fedora work correctly ? Thanks a lot ! 2011/2/28 Camaleón > On Mon, 28 Feb 2011 02:02:16 +0800, waterloo wrote: > > > Below is my /var/log/boot file . Thanks > > Keeping the interesting data and removing the rest of the logs: > > > Mon Feb 28 01:57:45 2011: Reading later boot files > (...) > > Mon Feb 28 01:57:45 2011: Reading later boot files... > > ^[[31mfailed!^[[39;49m > (...) > > Mon Feb 28 01:57:45 2011: Reading early boot files > > A quick Google search returns that this message can be related to > "readahead" (or "readahead-fedora") package. Do you have it installed? > > Greetings, > > -- > Camaleón > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/pan.2011.02.27.18.31...@gmail.com > >
Re: Reading later boot files failed
On Mon, 28 Feb 2011 02:02:16 +0800, waterloo wrote: > Below is my /var/log/boot file . Thanks Keeping the interesting data and removing the rest of the logs: > Mon Feb 28 01:57:45 2011: Reading later boot files (...) > Mon Feb 28 01:57:45 2011: Reading later boot files... > ^[[31mfailed!^[[39;49m (...) > Mon Feb 28 01:57:45 2011: Reading early boot files A quick Google search returns that this message can be related to "readahead" (or "readahead-fedora") package. Do you have it installed? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.27.18.31...@gmail.com
Re: Reading later boot files failed
Below is my /var/log/boot file . Thanks > Mon Feb 28 01:57:43 2011: Setting parameters of disc: (none). > > Mon Feb 28 01:57:43 2011: Setting preliminary keymap...done. > > Mon Feb 28 01:57:43 2011: Activating swap...done. > > Mon Feb 28 01:57:43 2011: Checking root file system...fsck from >> util-linux-ng 2.17.2 > > Mon Feb 28 01:57:43 2011: debian: clean, 378129/1321920 files, >> 3426756/5280512 blocks > > Mon Feb 28 01:57:43 2011: done. > > Mon Feb 28 01:57:43 2011: Cleaning up ifupdown > > Mon Feb 28 01:57:43 2011: Setting up networking > > Mon Feb 28 01:57:43 2011: Loading kernel modules...done. > > Mon Feb 28 01:57:43 2011: Setting up LVM Volume Groups Reading all >> physical volumes. This may take a while... > > Mon Feb 28 01:57:43 2011: No volume groups found > > Mon Feb 28 01:57:43 2011: No volume groups found > > Mon Feb 28 01:57:43 2011: No volume groups found > > Mon Feb 28 01:57:43 2011: . > > Mon Feb 28 01:57:43 2011: Activating lvm and md swap...done. > > Mon Feb 28 01:57:43 2011: Checking file systems...fsck from util-linux-ng >> 2.17.2 > > Mon Feb 28 01:57:43 2011: done. > > Mon Feb 28 01:57:43 2011: Mounting local filesystems...done. > > Mon Feb 28 01:57:44 2011: Activating swapfile swap...done. > > Mon Feb 28 01:57:44 2011: Cleaning up temporary files > > Mon Feb 28 01:57:44 2011: Configuring network interfaces...done. > > Mon Feb 28 01:57:44 2011: Starting portmap daemon > > Mon Feb 28 01:57:44 2011: Starting NFS common utilities: statd. > > Mon Feb 28 01:57:44 2011: Cleaning up temporary files > > Mon Feb 28 01:57:44 2011: Setting up ALSA...done. > > Mon Feb 28 01:57:44 2011: Setting console screen modes and fonts. > > Mon Feb 28 01:57:44 2011: ^[]R^[[9;30]^[[14;30]Setting up console font and >> keymap...done. > > Mon Feb 28 01:57:45 2011: Skip starting firewall: ufw (not enabled)...done. > > Mon Feb 28 01:57:45 2011: Setting kernel variables ...done. > > Mon Feb 28 01:57:45 2011: Reading later boot files > > Mon Feb 28 01:57:45 2011: Setting sensors limits. > > Mon Feb 28 01:57:45 2011: INIT: Entering runlevel: 2 > > Mon Feb 28 01:57:45 2011: Using makefile-style concurrent boot in runlevel >> 2. > > Mon Feb 28 01:57:45 2011: Setting sensors limits. > > Mon Feb 28 01:57:45 2011: Reading later boot files... >> ^[[31mfailed!^[[39;49m > > Mon Feb 28 01:57:45 2011: Enabling additional executable binary formats: >> binfmt-support. > > Mon Feb 28 01:57:45 2011: Starting NFS common utilities: statd. > > Mon Feb 28 01:57:45 2011: Reading early boot files > > Mon Feb 28 01:57:45 2011: Starting enhanced syslogd: rsyslogd. > > Mon Feb 28 01:57:45 2011: Starting polipo: polipo. > > Mon Feb 28 01:57:45 2011: Checking battery state...done. > > Mon Feb 28 01:57:45 2011: Starting portmap daemon...Already running.. > > Mon Feb 28 01:57:45 2011: Starting system message bus: dbus. > > Mon Feb 28 01:57:45 2011: Starting anac(h)ronistic cron: anacron. > > Mon Feb 28 01:57:45 2011: Starting network connection manager: >> NetworkManager. > > Mon Feb 28 01:57:45 2011: Starting deferred execution scheduler: atd. > > Mon Feb 28 01:57:45 2011: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. > > Mon Feb 28 01:57:45 2011: Mon Feb 28 01:57:45 2011: Starting hdapsd > > Mon Feb 28 01:57:45 2011: Mon Feb 28 01:57:45 2011: Selected interface: >> HDAPS > > Mon Feb 28 01:57:45 2011: Mon Feb 28 01:57:45 2011: Selected HDAPS input >> device: /dev/input/event16 > > Mon Feb 28 01:57:45 2011: Starting GNOME Display Manager: gdm3. > > Mon Feb 28 01:57:46 2011: Starting bluetooth: bluetoothd. > > Mon Feb 28 01:57:46 2011: Starting ACPI services > > Mon Feb 28 01:57:46 2011: Starting acpi_fakekey daemon...done. > > Mon Feb 28 01:57:46 2011: Starting preload: preload. > > Mon Feb 28 01:57:46 2011: Starting ClamAV virus database updater: >> freshclam. > > Mon Feb 28 01:57:46 2011: Starting Common Unix Printing System: cupsd. > > Mon Feb 28 01:57:46 2011: Starting DNS forwarder and DHCP server: dnsmasq. > > Mon Feb 28 01:57:47 2011: Setting parameters of disc: (none). > > Mon Feb 28 01:57:47 2011: Starting web server: apache2apache2: Could not >> reliably determine the server's fully qualified domain name, using 127.0.1.1 >> for ServerName > > Mon Feb 28 01:57:47 2011: . > > Mon Feb 28 01:57:47 2011: Starting periodic command scheduler: cron. > > Mon Feb 28 01:57:47 2011: Starting mouse interface server: gpm. > > Mon Feb 28 01:57:47 2011: Starting Hardware abstraction layer: hald. > > Mon Feb 28 01:57:48 2011: Starting
Re: Reading later boot files failed
On Sat, 26 Feb 2011 13:00:10 +0800, waterloo wrote: > when boot , I see an error : Reading later boot files failed . What is > the matter ? Enable boot log and send it here. In "/etc/default/bootlogd" file you have to set "BOOTLOGD_ENABLE=Yes". Reboot and review /var/log/boot. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.26.12.00...@gmail.com
Reading later boot files failed
when boot , I see an error : Reading later boot files failed . What is the matter ? I use Debian 6 amd64 . Thanks
Re: deleted /boot files
At Friday, 31 December 2004, you wrote: are there suggestions on how to get the fa311 netgear nic working w/ 2.2.20-compact? >>> >>>sounds like you need to tell it to load the tulip driver for fa311 >>> >>>and than tell i upgrade the kernel and it'd run lilo/grub >>>and you're back in biz >>> >> >>i tried to load tulip but i get a failure error. i even reboot w/ >>the 2.2.20-compact rescue.bin and root.bin floppies, try to install >>the tulip driver and still have a failure. >> >> > I ended up using the idepci recovery disks. I remember reading that the natsemi.o module in the compact driver disks would not work w/ the netgear fa311 nics. ... on to upgrading the kernel to the latest now that i have a network connection. -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
Harland Christofferson wrote: > Before I created this mess, I was running the 2.4.18-bf2.4 kernel. > I tried the rescue.bin and root.bin floppies from the Debian site > but I was not able to boot w/ them. I was able to boot w/ the 2.2. > 20-compact floppies however. > > Now, using 2.2.20-compact, I cannot get the Netgear FA311 NIC working > and the tulip module will not load. I still have the /lib/modules/2. > 4.18-bf2.4 directory intact. > > Considering I can boot on that machine w/ the 2.2.20-compact kernel, > and the only way I can get code onto it is via floppy at this point > (unless I can get tulip to load which is dismal), and I have an intact > /lib/modules/2.4.18-bf2.4 dir, can I get only the files: > > boot/System.map-2.4.18-bf2.4 > boot/config-2.4.18-bf2.4 > boot/vmlinuz-2.4.18-bf2.4 > > from the package, save them to floppy individually, put them on the > other machine, change lilo.conf to reflect the 2.4.18-bf2.4 kernel, > run lilo and reboot to the 2.4.18-bf2.4 kernel? If so, how can I > get only the three files from the package I wish? Use 'dpkg -x [package file]', then just copy the files you need. This is documented in the dpkg man page. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
>> >>sounds like raid is working ?? .. >> - in the future, do NOT copy files from one disk to another >> ( that is not how raid mirroring works ) > >> >>> are there suggestions on how to get the fa311 netgear nic working >>> w/ 2.2.20-compact? >> >>sounds like you need to tell it to load the tulip driver for fa311 >> >>and than tell i upgrade the kernel and it'd run lilo/grub >>and you're back in biz >> > >i tried to load tulip but i get a failure error. i even reboot w/ >the 2.2.20-compact rescue.bin and root.bin floppies, try to install >the tulip driver and still have a failure. > > Before I created this mess, I was running the 2.4.18-bf2.4 kernel. I tried the rescue.bin and root.bin floppies from the Debian site but I was not able to boot w/ them. I was able to boot w/ the 2.2. 20-compact floppies however. Now, using 2.2.20-compact, I cannot get the Netgear FA311 NIC working and the tulip module will not load. I still have the /lib/modules/2. 4.18-bf2.4 directory intact. Considering I can boot on that machine w/ the 2.2.20-compact kernel, and the only way I can get code onto it is via floppy at this point (unless I can get tulip to load which is dismal), and I have an intact /lib/modules/2.4.18-bf2.4 dir, can I get only the files: boot/System.map-2.4.18-bf2.4 boot/config-2.4.18-bf2.4 boot/vmlinuz-2.4.18-bf2.4 from the package, save them to floppy individually, put them on the other machine, change lilo.conf to reflect the 2.4.18-bf2.4 kernel, run lilo and reboot to the 2.4.18-bf2.4 kernel? If so, how can I get only the three files from the package I wish? -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
At Monday, 27 December 2004, Alvin Oga <[EMAIL PROTECTED] com> wrote: >On Mon, 27 Dec 2004, Harland Christofferson wrote: > >> what i did try was Alan's suggestion of the Debian rescue disk. I >> have never used it in a capacity such as this. I used the 2.2.20- >> compact rescue, root, driver-1 and driver-2 binaries. I am able to >> boot from the hard drive (woohoo) but the natsemi module doesn't >> seem to play well w/ the netgear nic i have at eth0 > >sounds like raid is working ?? .. > - in the future, do NOT copy files from one disk to another > ( that is not how raid mirroring works ) > >> are there suggestions on how to get the fa311 netgear nic working >> w/ 2.2.20-compact? > >sounds like you need to tell it to load the tulip driver for fa311 > >and than tell i upgrade the kernel and it'd run lilo/grub >and you're back in biz > i tried to load tulip but i get a failure error. i even reboot w/ the 2.2.20-compact rescue.bin and root.bin floppies, try to install the tulip driver and still have a failure. -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
On Mon, 27 Dec 2004, Harland Christofferson wrote: > what i did try was Alan's suggestion of the Debian rescue disk. I > have never used it in a capacity such as this. I used the 2.2.20- > compact rescue, root, driver-1 and driver-2 binaries. I am able to > boot from the hard drive (woohoo) but the natsemi module doesn't > seem to play well w/ the netgear nic i have at eth0 sounds like raid is working ?? .. - in the future, do NOT copy files from one disk to another ( that is not how raid mirroring works ) > are there suggestions on how to get the fa311 netgear nic working > w/ 2.2.20-compact? sounds like you need to tell it to load the tulip driver for fa311 and than tell i upgrade the kernel and it'd run lilo/grub and you're back in biz c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
> >I have never done what I am about to suggest, but try this: > >1. copy the whole contents of the directory /lib/modules/xxx/ from the >computer where you got your replacement /boot onto the computer that >you are trying to get going again. Here 'xxx' represents the kernel version >string of the kernel that you hope to use. > >2. Make sure the soft link in the / directory does point to the kernel binary >that you want to use in /boot. And make sure that /initrd.img hot link points >to the new initrd.img... in /boot > >3. run lilo again after you have done the above > >4. reboot and see what happens. > >HTH >-- >Paul E Condon >[EMAIL PROTECTED] > Well, I didn't try it either ;) what i did try was Alan's suggestion of the Debian rescue disk. I have never used it in a capacity such as this. I used the 2.2.20- compact rescue, root, driver-1 and driver-2 binaries. I am able to boot from the hard drive (woohoo) but the natsemi module doesn't seem to play well w/ the netgear nic i have at eth0 i am hopeful, if i can get eth0 working, i can upgrade the kernel to the latest and move on past this to raid1 on this machine. are there suggestions on how to get the fa311 netgear nic working w/ 2.2.20-compact? thanks to all! Harland -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
On Mon, Dec 27, 2004 at 06:31:49PM -0500, Harland Christofferson wrote: > At Monday, 27 December 2004, you wrote: > > >On Mon, Dec 27, 2004 at 01:59:53PM -0500, Harland Christofferson wrote: > >> At Monday, 27 December 2004, Alexander Schmehl <[EMAIL PROTECTED] > >> info> wrote: > >> > >> >* Harland Christofferson <[EMAIL PROTECTED]> [041227 > >> 17:47]: > >> > > >> >> >cat /etc/lilo.conf > >> >[..] > >> >> image=/vmlinuz > >> >> label=Linux > >> >> read-only > >> >> # restricted > >> >> # alias=1 > >> >> initrd=/initrd.img > >> > > >> >You need to symlink boot/initrd.img-2.4.18-k7 to /initrd.img > >> > > >> > >> okay, tried this symlink for /boot and / but the kernel continues > >> to panic. > >> > > > >I'm coming in late on this thread, so have missed earlier info., but > >is the kernel that you loaded into /boot the exact same kernel that > >you were using before you wiped out /boot? If not, you have > >mis-matching modules in /lib/modules. Under /lib/modules there should > >be a directory for each kernel version that you have ever run on > >this computer. Make sure you have a directory for whatever kernel > >version you are attempting to use now. > > > >HTH > > > > > > they are indeed mismatched kernels ... does this mean i need to reinstall? > > i am copying tomsrtbt now in hope that i can get the system running > I have never done what I am about to suggest, but try this: 1. copy the whole contents of the directory /lib/modules/xxx/ from the computer where you got your replacement /boot onto the computer that you are trying to get going again. Here 'xxx' represents the kernel version string of the kernel that you hope to use. 2. Make sure the soft link in the / directory does point to the kernel binary that you want to use in /boot. And make sure that /initrd.img hot link points to the new initrd.img... in /boot 3. run lilo again after you have done the above 4. reboot and see what happens. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
On Mon, 27 Dec 2004, Harland Christofferson wrote: > while getting ready to build a raid 1 array, i accidentally deleted > the /boot files. the partition is still there however and is still > flagged as boot partition. > > although i have a boot floppy for this machine, i could not retrieve > a backup of the /boot partition from another hard disk i have. in > a novice attempt to resolve this, i copied the /boot partition from > another machine and reboot. upon rebooting w/ the boot floppy, i > ran lilo to try to rebuild the MBR. lilo complains: you CANNNOT copy /boot from one disk to another ... -- you just destroyed /boot on the other disk you copied onto and so its right, that it panics -- to recover ... - i assume the kernel from the other disk is the same as what oyu need on your current disk - i assume your floppy boots insert floppy and tell it "root=/dev/md1" or whatever you have as your / for your system - if you cannot boot off of floppy, insert a debian install floppy/cd or knoppix cd - manually build /dev/md0 ( if that is /boot ) - mdadm [options] /dev/hdaxx /dev/hdcxxx .. ( options would change depending on what the problem is ) - google for examples that matches your problem - mke2fs -j /dev/md0 - mount /dev/md0 /boot - copy the files from a working /boot onto the raid /boot - required files in /boot: vmlinuz map and any other files used by lilo.conf or (grub)menu.lst - run lilo or grub and reboot > > Fatal: First sector of /dev/hda1 doesn't have a valid boot signature correct > how can i fix my /boot partition so that the machine can boot without > the files in the boot or root partitions that originally were part > of this machine? /boot is NOT needed to boot ... you can "boot" off anything ( floppy, cd, network, ... ) / ( the rootfs ) must be working c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
At Monday, 27 December 2004, you wrote: >On Mon, Dec 27, 2004 at 01:59:53PM -0500, Harland Christofferson wrote: >> At Monday, 27 December 2004, Alexander Schmehl <[EMAIL PROTECTED] >> info> wrote: >> >> >* Harland Christofferson <[EMAIL PROTECTED]> [041227 >> 17:47]: >> > >> >> >cat /etc/lilo.conf >> >[..] >> >> image=/vmlinuz >> >> label=Linux >> >> read-only >> >> # restricted >> >> # alias=1 >> >> initrd=/initrd.img >> > >> >You need to symlink boot/initrd.img-2.4.18-k7 to /initrd.img >> > >> >> okay, tried this symlink for /boot and / but the kernel continues >> to panic. >> > >I'm coming in late on this thread, so have missed earlier info., but >is the kernel that you loaded into /boot the exact same kernel that >you were using before you wiped out /boot? If not, you have >mis-matching modules in /lib/modules. Under /lib/modules there should >be a directory for each kernel version that you have ever run on >this computer. Make sure you have a directory for whatever kernel >version you are attempting to use now. > >HTH > > they are indeed mismatched kernels ... does this mean i need to reinstall? i am copying tomsrtbt now in hope that i can get the system running -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
On Mon, Dec 27, 2004 at 01:59:53PM -0500, Harland Christofferson wrote: > At Monday, 27 December 2004, Alexander Schmehl <[EMAIL PROTECTED] > info> wrote: > > >* Harland Christofferson <[EMAIL PROTECTED]> [041227 > 17:47]: > > > >> >cat /etc/lilo.conf > >[..] > >> image=/vmlinuz > >> label=Linux > >> read-only > >> # restricted > >> # alias=1 > >> initrd=/initrd.img > > > >You need to symlink boot/initrd.img-2.4.18-k7 to /initrd.img > > > > okay, tried this symlink for /boot and / but the kernel continues > to panic. > I'm coming in late on this thread, so have missed earlier info., but is the kernel that you loaded into /boot the exact same kernel that you were using before you wiped out /boot? If not, you have mis-matching modules in /lib/modules. Under /lib/modules there should be a directory for each kernel version that you have ever run on this computer. Make sure you have a directory for whatever kernel version you are attempting to use now. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
At Monday, 27 December 2004, Alexander Schmehl <[EMAIL PROTECTED] info> wrote: >* Harland Christofferson <[EMAIL PROTECTED]> [041227 17:47]: > >> >cat /etc/lilo.conf >[..] >> image=/vmlinuz >> label=Linux >> read-only >> # restricted >> # alias=1 >> initrd=/initrd.img > >You need to symlink boot/initrd.img-2.4.18-k7 to /initrd.img > okay, tried this symlink for /boot and / but the kernel continues to panic. -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
* Harland Christofferson <[EMAIL PROTECTED]> [041227 17:47]: > >cat /etc/lilo.conf [..] > image=/vmlinuz > label=Linux > read-only > # restricted > # alias=1 > initrd=/initrd.img You need to symlink boot/initrd.img-2.4.18-k7 to /initrd.img signature.asc Description: Digital signature
Re: deleted /boot files
At Monday, 27 December 2004, Laurent CARON <[EMAIL PROTECTED]> wrote:
>Harland Christofferson wrote:
>
>>an update to my saga is that i was able to run lilo. however, when
>>trying to boot, i see:
>>
>>request_module{block-major-3]: root fs not mounted
>>VFS: Cannot open root device "303" or 03:03
>>Please append correct "root=" boot option
>>Kernel Panic: VFS: Unable to mount root fs on 03:03
>>
>>
>>my root= option is set to /dev/hda3 which is the root partition.
>>
>>suggestions?
>>
>>At Monday, 27 December 2004, Harland Christofferson <[EMAIL PROTECTED]
>
>>com> wrote:
>>
>>
>>
>>>while getting ready to build a raid 1 array, i accidentally deleted
>>>the /boot files. the partition is still there however and is still
>>>flagged as boot partition.
>>>
>>>although i have a boot floppy for this machine, i could not retrieve
>>>a backup of the /boot partition from another hard disk i have. in
>>>a novice attempt to resolve this, i copied the /boot partition from
>>>another machine and reboot. upon rebooting w/ the boot floppy, i
>>>ran lilo to try to rebuild the MBR. lilo complains:
>>>
>>>
>>>
>>>>Added Linux *
>>>>Skipping /vmlinux.old
>>>>Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
>>>>
>>>>
>>>how can i fix my /boot partition so that the machine can boot
without
>>>the files in the boot or root partitions that originally were part
>>>of this machine?
>>>
>>>harland
>>>
>>>
>>>
>fdisk -l
Disk /dev/hda: 255 heads, 63 sectors, 4998 cylinders
Units = cylinders of 16065 * 512 bytes
Device BootStart EndBlocks Id System
/dev/hda1 * 1 4 32098+ 83 Linux
/dev/hda2 535249007+ 82 Linux swap
/dev/hda336 2223 17575110 83 Linux
/dev/hda4 2224 4998 2290187+ 5 Extended
/dev/hda5 2224 3242 8988336 83 Linux
/dev/hda6 3243 4461 8988336 83 Linux
/dev/hda7 4462 4998 4313421 83 Linux
>
>cat /proc/mdstat
Personalities:
read_ahead not set
md0: not active
md1: not active
md2: not active
md3: not active
>
>ls -al /
drwxr-xr-x2 root root 4096 Nov 28 22:48 bin
drwxr-xr-x3 root root 1024 Dec 27 10:20 boot
drwxr-xr-x2 root root 4096 Jan 30 2004 cdrom
drwxr-xr-x 10 root root24576 Dec 26 06:47 dev
drwxr-xr-x 117 root root 8192 Dec 27 00:15 etc
drwxr-xr-x2 root root 4096 Jan 30 2004 floppy
drwxr-xr-x 25 root root 4096 Dec 13 09:24 home
drwxr-xr-x1 root root 268 Jan 30 2004 initrd
drwxr-xr-x8 root root 4096 Dec 6 23:14 lib
drwx--2 root root 4096 Jun 6 2004 lost+found
drwxr-xr-x 14 root root 4096 Dec 27 00:08 mnt
drwxr-xr-x3 root root 4096 Sep 4 2002 opt
dr-xr-xr-x 219 root root0 Dec 16 06:39 proc
drwxr-xr-x 17 root root 4096 Dec 23 15:22 root
drwxr-xr-x2 root root 4096 Dec 6 23:14 sbin
drwxr-xr-x2 root root 4096 Jul 30 18:07 sys
drwxrwxrwt 21 root root20480 Dec 27 12:00 tmp
drwxr-xr-x 16 root root 4096 Sep 12 08:55 usr
drwxr-xr-x 17 root root 4096 Sep 28 19:08 var
lrwxrwxrwx1 root root 22 Dec 26 23:58 vmlinuz -> boot/vmlinuz-
2.4.18-k7
the vmlinuz is there b/c i put the link back after i wiped out the
/boot contents.
>ls -al /boot
-rw-r--r-- 1 root root 7020544 Mar 25 2004 System.map-2.2.20
-rw-r--r-- 1 root root 409179 Apr 14 2002 System.map-2.4.18-k7
-rw-r--r-- 1 root root7988 Sep 2 2002 boot-bmp.b
-rw-r--r-- 1 root root6204 Sep 2 2002 boot-compat.b
-rw-r--r-- 1 root root7964 Sep 2 2002 boot-menu.b
-rw-r--r-- 1 root root6204 Sep 2 2002 boot-text.b
-rw-r--r-- 1 root root 512 Sep 2 2002 boot.0300
-rw-r--r-- 1 root root 512 Dec 27 10:58 boot.0301
-rw-r--r-- 1 root root 728 Sep 2 2002 chain.b
-rw-r--r-- 1 root root 14979 Sep 2 2002 config-2.2.20
-rw-r--r-- 1 root root 37096 Apr 13 2002 config-2.4.18-k7
-rw-r--r-- 1 root root 2719744 Jan 6 2003 initrd.img-2.4.18-k7
drwx-- 2 root root 12288 Aug 26 2002 lost+found
-rw--- 1 root root 49664 Jan 6 2003 map
-rw-r--r-- 1 root root 94428 Nov 12 12:37 memtest86+.bin
-rw-r--r-- 1 root root 656 Sep 2 2002 os2_d.b
lrwxrwxrwx 1 root root 14 Dec 27 10:46 vmlinuz -> vmlinuz-
2.4.18-k7
-rw-r--r-- 1 root root 1005181 Aug 26 2002 vmlinuz-2.2.20
-rw-r--r-- 1 root root 643025 Apr 14 2002 vmlinuz-2.4.18-k7
keep in mind, the contents of /boot are the result of a tarball i
moved on to this m
Re: deleted /boot files
Harland Christofferson wrote:
an update to my saga is that i was able to run lilo. however, when
trying to boot, i see:
request_module{block-major-3]: root fs not mounted
VFS: Cannot open root device "303" or 03:03
Please append correct "root=" boot option
Kernel Panic: VFS: Unable to mount root fs on 03:03
my root= option is set to /dev/hda3 which is the root partition.
suggestions?
At Monday, 27 December 2004, Harland Christofferson <[EMAIL PROTECTED]
com> wrote:
while getting ready to build a raid 1 array, i accidentally deleted
the /boot files. the partition is still there however and is still
flagged as boot partition.
although i have a boot floppy for this machine, i could not retrieve
a backup of the /boot partition from another hard disk i have. in
a novice attempt to resolve this, i copied the /boot partition from
another machine and reboot. upon rebooting w/ the boot floppy, i
ran lilo to try to rebuild the MBR. lilo complains:
Added Linux *
Skipping /vmlinux.old
Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
how can i fix my /boot partition so that the machine can boot without
the files in the boot or root partitions that originally were part
of this machine?
harland
fdisk -l
cat /proc/mdstat
ls -al /
ls -al /boot
cat /etc/fstab
cat /etc/lilo.conf
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: deleted /boot files
an update to my saga is that i was able to run lilo. however, when
trying to boot, i see:
request_module{block-major-3]: root fs not mounted
VFS: Cannot open root device "303" or 03:03
Please append correct "root=" boot option
Kernel Panic: VFS: Unable to mount root fs on 03:03
my root= option is set to /dev/hda3 which is the root partition.
suggestions?
At Monday, 27 December 2004, Harland Christofferson <[EMAIL PROTECTED]
com> wrote:
>while getting ready to build a raid 1 array, i accidentally deleted
>the /boot files. the partition is still there however and is still
>flagged as boot partition.
>
>although i have a boot floppy for this machine, i could not retrieve
>a backup of the /boot partition from another hard disk i have. in
>a novice attempt to resolve this, i copied the /boot partition from
>another machine and reboot. upon rebooting w/ the boot floppy, i
>ran lilo to try to rebuild the MBR. lilo complains:
>
>> Added Linux *
>> Skipping /vmlinux.old
>> Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
>
>how can i fix my /boot partition so that the machine can boot without
>the files in the boot or root partitions that originally were part
>of this machine?
>
>harland
>
>--
>Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems
>
>http://www.zerocrossings.com/
>
>--
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian.org
>
--
Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems
http://www.zerocrossings.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
deleted /boot files
while getting ready to build a raid 1 array, i accidentally deleted the /boot files. the partition is still there however and is still flagged as boot partition. although i have a boot floppy for this machine, i could not retrieve a backup of the /boot partition from another hard disk i have. in a novice attempt to resolve this, i copied the /boot partition from another machine and reboot. upon rebooting w/ the boot floppy, i ran lilo to try to rebuild the MBR. lilo complains: > Added Linux * > Skipping /vmlinux.old > Fatal: First sector of /dev/hda1 doesn't have a valid boot signature how can i fix my /boot partition so that the machine can boot without the files in the boot or root partitions that originally were part of this machine? harland -- Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems http://www.zerocrossings.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /boot files
On Fri, Oct 27, 2000 at 09:41:01AM +0300, Petteri Heinonen wrote: > Hello there. > I'd like to know what is purpose of all those files in my /boot and if they > are needed there or not. Files in my /boot are: > > System.map-2.2.15 symbol maps for kernel image 2.2.15, used mostly for debugging, but some utilities may use them too (ps top iirc) there should be one of these for each kernel you have installed (of differing versions anyway) > boot.0300 backup copy of the MBR from /dev/hda, created by lilo. > boot.0303 backup copy of the MBR from /dev/hda3, created by lilo. > boot.b lilo second stage bootstrap. > bzImage kernel image you installed yourself. debian kernel-package names this vmlinuz-X.Y.ZZ. > chain.b lilo chain loader, used to chain load a foreign OS's bootblock. (DOG, BSD etc) > config-2.2.15 the kernel config file for 2.2.15 kernel image. this is the .config created by make config|menuconfig|xconfig > map blocklists for image files lilo will boot. > mbr.b basic but functional MBR replacement, aka GRAVE SECURITY HOLD. (go look for a thread with that subject in debian-devel archives) ;-) > os2_d.b an older lilo chain loader, used for os/2 i believe. > vmlinuz-2.2.15 the kenrel image that goes with the above config and System.map files. > I know kernel files, but the rest are at least partial mystery to me. I > think that .b files are different MBR images, but what about boot.0300 and > boot.0303? And what is purpose of map file? When I made new kernel and > modules (and modules_install), the map files was also made again. And one see above. > question about kernels: what if I want several kernels with same version > number, how can I make them use a different directories for modules? And add something to the EXTRAVERSION field in the main kernel Makefile. this is used to create the preX suffixes on pre kernels, but unused on proper releases. > last: my new kernel works out just fine, except that when I try to load > modules (ppp module for example), I get many 'unresolved symbol' lines. What > should I do to help this, kernel-howto doesn't say anything about this. sounds like modules not matching the installed kernel, when installing a new kernel over an existing kernel of the same version you should move /lib/modules/`uname -r` out of the way, otherwise some modules will be left that don't match the new kernel. other then that try running depmod -a. also use kernel-package to create kernel .deb images, this makes things much simpler and prevents some screwups. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpcZs5XjOE4e.pgp Description: PGP signature
/boot files
Hello there. I'd like to know what is purpose of all those files in my /boot and if they are needed there or not. Files in my /boot are: System.map-2.2.15 boot.0300 boot.0303 boot.b bzImage chain.b config-2.2.15 map mbr.b os2_d.b vmlinuz-2.2.15 I know kernel files, but the rest are at least partial mystery to me. I think that .b files are different MBR images, but what about boot.0300 and boot.0303? And what is purpose of map file? When I made new kernel and modules (and modules_install), the map files was also made again. And one question about kernels: what if I want several kernels with same version number, how can I make them use a different directories for modules? And last: my new kernel works out just fine, except that when I try to load modules (ppp module for example), I get many 'unresolved symbol' lines. What should I do to help this, kernel-howto doesn't say anything about this. thanks in advance, Petteri Heinonen email: [EMAIL PROTECTED] tel.: +358 (0)50 3363 286 addr.: Pehkusuonkatu 21 B 38 33820 Tampere, FIN
Re: Boot Files
On Sun, 30 Mar 1997, Robert D. Hilliard wrote: > Is it necessary, or even useful, to have the System.map-x.x.xx > file in the /boot directory if loadlin is used for booting? > > Is there any need to have a kernel in / or /boot unless lilo is > being used? It is, as you have surmised, not necessary to have the kernel images. I'm not sure, but the System.map may still be useful but probably not necessary. However, if you happen to go the way I did, you'll use loadin for quite a while thinking it's the best way for you to boot, then you'll change your mind and use LILO or some other boot manager that allows you to bypass booting DOS/Windoze when you want to go straight to Linux. That's when I was happy that I always kept a copy of my current zImage in /. Cheers. Syrus. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.
Re: Boot Files
"Robert D. Hilliard" <[EMAIL PROTECTED]> writes: > > Is it necessary, or even useful, to have the System.map-x.x.xx > file in the /boot directory if loadlin is used for booting? Yes, there are a lot of utilities referencing it - most notably ps. > Is there any need to have a kernel in / or /boot unless lilo is > being used? Don't know about this one, I'm using lilo and I don't care about < 700K for the current and previous kernels. Siggy -- Siggy Brentrup <[EMAIL PROTECTED]> aka: [EMAIL PROTECTED] *** PGP public key available from keyservers *** PGP fingerprint = C8 95 66 8C 75 7E 10 A2 05 61 C7 7F 05 B6 A4 DF
Boot Files
Is it necessary, or even useful, to have the System.map-x.x.xx file in the /boot directory if loadlin is used for booting? Is there any need to have a kernel in / or /boot unless lilo is being used? Bob
