File system locked on upgrade

[NoOp]

On 07/17/2009 11:49 AM, David S Angulo wrote:
> On Thu, Jul 16, 2009 at 5:02 PM, NoOp<glgxg at sbcglobal.net> wrote:
> 
> Thanks, NoOp.  This was really helpful.
> 
>> - Again in recovery, try dpkg to see if any of the update packages borked.
> 
> I couldn't figure out how to use dpkg.  

>From the 8.04 recovery menu (recovery mode option at grub boot menu);
select 'dpkg Repair broken packages', Enter.

It will run a script to check your files & update your system. Follow
the prompt & say 'yes' to let it work. If nothing is broken, you will
simply get "Finished, please press ENTER".

However... that probably won't work if the drive is being mounted as ro.
But it might be worth a shot to see if the drive is writtable in
recovery mode.

If not, (also in recovery mode) select 'root Drop to a root shell prompt'.

# df
Check to see if perhaps the drive has run out of space. If not:
# mount -n -o remount,rw /
  or
# mount -n -o remount,rw /dev/sda3
  if no errors then try:
# apt-get update
# dpkg --configure -a
# apt-get -f install

check the file properties:
# ls -l / |more
# exit
resume

I ran dselect and could scroll
> through packages seing status.  The only thing I saw out of place was:
> 
> libdevmapper  removed      required

Well, that could certainly be a problem:
http://packages.ubuntu.com/hardy/libdevmapper1.02.1

Hopefully the previous (dpkg etc) will have corrected that.

> volumeid         not installed important

same.

> 
>> - fstab is doing as instructed because there is an error.
> 
> Ah.  OK.  Now I understand why we're doing this.
> 
>> Check to make
>> sure that the UUID didn't get messed up in the process:
>> $ sudo blkid
>>  or
>> # blkid
>> and compare that to see if it matches that of your fstab.
> 
> Yes, they match.

As Derek pointed out, they would have to be otherwise the drive wouldn't
be getting mounted at all. My mistake. But you also have sda1 and sda2 -
are those UUID's correct and also being mounted ro, or only sda3?

> 
> 
>> Check /var/log/dpkg.log to see what the upgrades were.
>> /var/log/syslog.0 should give some indication of errors, as should
>> /var/log/dmesg.0.
> 
> 
> Before I posted the first message, I did a grep of everything in
> /var/log for "error" and couldn't find anything.  I see the lines
> below in dmesg, but I don't understand any of it
> 
> 
> ------ start lines from dmesg -------
> [   25.817922] scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA
> MK1032GS AS02 PQ: 0 ANSI: 5
> [   25.821799] scsi 1:0:0:0: CD-ROM            HL-DT-ST DVDRAM
> GMA-4082N HA01 PQ: 0 ANSI: 5
> [   25.831918] Driver 'sd' needs updating - please use bus_type methods
> [   25.832026] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> [   25.832047] sd 0:0:0:0: [sda] Write Protect is off
> [   25.832052] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   25.832082] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [   25.832155] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> [   25.832173] sd 0:0:0:0: [sda] Write Protect is off
> [   25.832178] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   25.832208] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [   25.832214]  sda:<4>Driver 'sr' needs updating - please use bus_type methods
> [   25.857827]  sda1 sda2 sda3
> [   25.857971] sd 0:0:0:0: [sda] Attached SCSI disk
> ------ end   lines from dmesg -------

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/186167
[dmesg: Driver 'sd' needs updating - please use bus_type methods]
Isn't an issue.

Again, you'll need to go back and look at the full logs I mentioned. Use
the '|more' pipe so that you can read by screen (spacebar will scroll to
next screen). Hopefully you'll be able to spot the problem in the logs.

Also please provide the output of:
# tail /var/log/dpkg.log