[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What happened to debian - does "stable" keep having any meaning?


Boyd Stephen Smith Jr. wrote:
> On 2011-03-23 00:59:49 Geronimo wrote:
> >Hello,
> >
> >Boyd Stephen Smith Jr. wrote:
> >> Now, moving between 6.0.0 and 6.0.1 shouldn't have been a problem, but I
> >> suspect you actually would have had issues rebooting your 6.0.0 system
> >> even without the 6.0.1 updates, since you didn't have your fstab in
> >> order.
> >
> >Grub can't be wrong, cause it is working in your system.
> I didn't say that.  

I know. It was kind of provacative black/white conclusion
Don't take me too serious!

> >On a complex system (yes, for me, linux is quite a complex system) the
> >truth may be somewhat different. May be, we both are wrong.
> How complex is your set up?  I'm using mdadm RAID 1 for "/boot" and GRUB
> mbr, mdadm RAID 1 + mdadm RAID 5 inside a LVM2 volume group that provides
> separate LVs for /, /usr, /usr/local, /opt, /srv, /var, /var/cache,
> /var/tmp, and /home plus /tmp on tmpfs.

I use raid on my servers only, which I did not update to 6.0.1 - and I won't 
do that, til the bug has been found and eliminated.

On my desktop system, fstab has 40 active entries.

> Maybe we both a wrong is probably the most likely case. :(


As Tom stated, grub has not been updated, so the only remaining possibility 
is, that a kernel change makes grub fail ...

So I took a closer look to dpkg.log and the kernel has been changed.
I did not find a log-entry for execution of update-grub, but I'm quite sure, 
that this has been run (isn't this true for every kernel change?).

I remember old days, where kernel had a parameter like "boot from externals 
first". As today it's most probabely, that internal controllers (from mainbord) 
are faster than external controllers, an option like "internal controller 
always is first" would be quite a good option.

May be, that UUID and Label relaxes harddisk handling, but surely there's stil 
a lot of software around, that uses /dev/sdxx, or like grub (hd#, partition#).
It's quite annoying, booting from debian installer in rescue mode and at the 
menue, where a root partition has to be choosen, you have to select i.e. 
/dev/sda1 - and after starting a shell into that root partition, the device 
suddenly is /dev/sde1 - and "mount", "cat /proc/partition" and "df -T" all 
show different device names for the same partition.

kind regards


Reply to: