Re: dd hung up by disk errors
If your bad sectors are local to a particular area of the disk, you could read sections starting at the end, and moving towards the beginning after each section is completed. Later you would concatenate the sections that were recoverable. Give either iseek=n or skip=n to dd to skip over a portion of the disk. Also download, burn and boot off the SystemRescueCd - it has a lot of tools for this sort of thing: http://www.sysresccd.org/Main_Page Don Quixote -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com Dulcinea Technologies: Software of Elegance and Beauty. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: kernel compile - Unable to mount root fs
On Sat, Jul 18, 2009 at 5:39 AM, Soren Orelsoren.o...@gmail.com wrote: hmmm.. it works, but I have to hit Ctrl+D at every boot... :D On some of your vmlinux lines in your menu.lst you have the word single. That boots you into single-user mode, that you exit from by hitting Ctrl-D. Remove just the word single and you should be good to go. Don Quixote -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: resize2fs: Either the superblock or the partition table is likely to be corrupt!
On Sun, Jul 19, 2009 at 8:31 PM, Mark Allumsm...@allums.com wrote: Protection by isolaton, partly. I do the same thing. Maybe it's just superstition, but it's fairly rare to lose a whole hard drive, but fairly common to corrupt a filesystem. Such corruption usually happens when you (intentionally) write to a filesystem. It could happen otherwise, because of some wildly buggy kernel code writing outside the proper partition, but I would expect that to be rare. So if you have separate filesystems, /tmp, /var and /home are likely to get corrupted, but /boot and / aren't so likely. In the event of this kind of corruption, you should still be able to boot. Don Quixote -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: kernel compile - Unable to mount root fs
Did you build and install your initrd? You might need to load a module to mount your root filesystem, and if so it should be in the initrd. The initrd also needs to be named in your grub entry. It's not enough just to build and install the module, because those are accessible only after your root fs is mounted! -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: kernel compile - Unable to mount root fs
In your Grub menu.lst file, there are some lines that look like this one: initrd /initrd.img-2.6.26-2-686 You need a line like that just below the item for the kernel you're trying to boot, except that you want the initrd version to match the new kernel version. initrd stands for Initial RAM Disk. It's a compressed archive that contains the contents of a small initial root filesystem, with just enough in it to to load the modules you're going to need to mount your root filesystem. In particular it needs to have the modules for your lvm and any RAID controllers. I've never made an initrd on Debian, but on Fedora the command is mkinitrd. Don Quixote -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
