> > -------- Forwarded Message -------- > > From: Camaleón <noela...@gmail.com> > > To: debian-user@lists.debian.org > > Subject: Re: restoring MBR > > Date: Sun, 31 Jul 2011 12:06:14 +0000 (UTC)
> > > On Sat, July 30, 2011 6:40 am, Camaleón wrote: > > >>>>> One of my (home made) overnight cron jobs does this: Very important is "overnight cron jobs"! From time to time I backup my MBR manually, btw. also using dd and adding the date to the file name, but before I restore an MBR from an backup I try to see how software guess the partition table should be restored. > > >>>>> dd if=/dev/sda \ > > >>>>> of=$DST/mbr_backup.bin \ > > >>>>> bs=512 \ > > >>>>> count=1 >> $LOG 2>&1 Since this list allows HTML, we should use it, instead of using cryptic lines including the backslash :p. The spams use HTML, but we don't :(. I suspect the original script is without backslashes. And btw. there're additionally some cryptic thingies that are not needed to explain how to use dd to backup and restore a MBR using dd. "$DST", ">> $LOG 2>&1" :D. Ok, I didn't read the whole thread, but some people might use Google to find help and they also won't read the whole thread. > email message attachment > > > -------- Forwarded Message -------- > > From: Luke Kenneth Casson Leighton <luke.leigh...@gmail.com> > > To: debian-user@lists.debian.org > > Subject: 2.6.39-amd64 lvm-based root: fails to boot > > Date: Sun, 31 Jul 2011 12:58:20 +0100 > > > > > > folks, hi, > > > > bug reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636123 > > > > i was wondering if anyone else has a similar configuration (booting > > off of root LVM partitions) and had encountered similar issues of root > > filesystems being unrecognised. > > > > l. Some days ago I needed to turn of and on the power of my computer, before Debian was able to do a complete startup. I thought it was time again to reconnect the SATA cables. There was no kernel change. I used my very old, self-build 2.6.39-amd64. The issue disappeared after some upgrades without reconnecting cables. I didn't fear a broken HDD, since there were no click-click noises and it's a very new, durable HDD. I guess I didn't upgrade GRUB, but usually I don't shutdown and startup my computer, so I anyway guess that GRUB2 is the devil and nothing else, because sometimes there even was no GRUB menu, while the BIOS displayed that all HDDs were available. Yes, I couldn't resist to shutdown and startup several times, after this issue appeared. Oh, didn't read the bugreport, since it's something similar to a complete hwinfo.
