We need more testers to the new incoming repo (how-to)

[Spec-chum]

Update pack 2 all installed with nothing to report (or if you've read my thread about being bored lol )

And just for giggles I did a backup and reinstalled lmde from scratch and went straight to Update Pack 2, again no issues ( )

Nice work!

[zerozero]

boring

[AlbertP]

My NTFS drives just dismount - I am running the 2.6.38-10 kernel. It also worked with 2.6.38-8 and 2.6.37. Seems this is a bug in the 2.6.39 kernel of LMDE.

[SimonTS]

@Wyrdoak

Error 1 is caused by you replacing your / partition information with the correct swap UUID but with a leading " that shouldn't be there
Error 2 is caused by you leaving the original, incorrect, UUID in place for swap.
Copying my /etc/fstab file and editing it for your system, it should look like this...

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
proc /proc proc nodev,noexec,nosuid 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# /dev/sda1 / ext4 rw,errors=remount-ro 0 0
UUID=1140b737-c1d0-4491-a560-cce25fe10ee3 / ext4 rw,errors=remount-ro 0 0
# swap was on /dev/sda6 during installation
UUID=eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e none swap sw 0 0
# /dev/sda3 / ext4 rw,errors=remount-ro 0 0
UUID=496d31b8-39f3-42c8-9265-742373c0d2e6 / ext4 rw,errors=remount-ro 0 0

[wyrdoak]

SimonTS,
I think that did it, the UUID numbers started running together, a problem for the dyslectic.

no problems with swapon now. I now have a 7.7gb swapfile. need to turn off the other program.

Here the fstab I used:


# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
proc /proc proc nodev,noexec,nosuid 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
#/dev/sda1 / ext4 rw,errors=remount-ro 0 0
UUID=1140b737-c1d0-4491-a560-cce25fe10ee3 / ext4 rw,errors=remount-ro 0 0
#swap was on /dev/sda2 during installation
UUID=eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e none swap sw 0 0
#/dev/sda3 / ext4 rw,errors=remount-ro 0 0
UUID=496d31b8-39f3-42c8-9265-742373c0d2e6 / ext4 rw,errors=remount-ro 0 0

Thank you much for your help, I now have a better idea of what I'm looking at now.

[SimonTS]

Wyrdoak, you're welcome. I've had to go through that about 20 times in recent weeks due to my addiction to re-installing distros

Just keep an eye on it - if you upgrade your kernel it wouldn't surprise me if something went screwy again.

[wyrdoak]

SimonTS,

Thank you again, I saved a copy to my notes just in case.

And have the swap the same as in Mint 10 now.

I wasn't kidding about the dyslexia, I wouldn't be able to do that too many times.

[bluheron1]

Just installed update pack 2 on my desktop. Haven't found any problems so far. 203 updates and six new libs.
That's a hefty update lol The new updater worked flawlessly.

Good job mint team !!!

[kmb42vt]

Okay, I have update pack 2 installed and so far no problems. I'm booted into the updated 2.6.39-2 kernel (as listed in Grub boot list) which is defined in Synaptic as the 2.6.39-3 kernel in the "Installed kernel" column btw--go figure. Using "Safely remove drive" for my "Fantom" 500 GB external USB hard drive (single NTFS partition) worked with this time around--no kernel panic.

BTW, the download speed was excellent (for me in the US), running at just above 1.0 MB/sec on an 8 MB download broad band connection (which often test at download speeds up to 14 MB). The new update servers are working fine so far.

More later....

[kmb42vt]

:lol: boring

I hate to add to your over excitement here, but yeah--boring.

[wayne128]

:lol: boring

I hate to add to your over excitement here, but yeah--boring.

sooner or later would play with Sid

[rocuronium]

Installed Update Pack 2 today with no problems. Can't remember the download speed, but it was normal enough for me not to notice.

Great work!

[kmb42vt]

Wyrdoak, you're welcome. I've had to go through that about 20 times in recent weeks due to my addiction to re-installing distros

Just keep an eye on it - if you upgrade your kernel it wouldn't surprise me if something went screwy again.

Ah, a fellow addict although I've managed to cut my distro hopping to 10 every few weeks down from 20 (and my wife is talking to me again too! ). As I posted before, the same thing happens to me but that's the price we pay to hop. One thing though, upgrading kernels, at least in my experience, is not going to mess with your fstab file at all. Updating? Now that's a different matter entirely.

Actually for the current release of LMDE, for a fresh install the fstab file was automatically built using the old way of identifying partitions by alpha-numeric designation (sda1, sda2, sda3, etc for example). Sometime during the update process over the last 8 months, Debian switched over to using the UUID number to identify each partition as it pertained to the LMDE install (but keeping old alpha-numeric labeling so you knew which partition was which). It was that switchover and rebuild of the fstab file that seemed to cause most of the problems that Wyrdoak experienced. That plus running multiple Linux distros on the same hard drive can cause the same type of problems as you probably well know.

[bigdee]

Installed Update Pack 2 and absolutely no problems what so ever.
It's more great work by the devs, but it is pretty boring.
Can't they squeeze in just one little deliberate mistake/bug?

[Dar-es-Salaam]

Hi All

I switched to incoming repro the other day and all went fine. However today I did an update and during the instalation this message appeared

Installation finished. No error reported.
/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea..

/usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..

Installation finished. No error reported.


It also downloaded a whole lot of openoffice

I have not done anything different than I would normally do. By the way I use aptitude to do all my updates. I hope I have posted this in the right place, I am not sure

[xircon]

I noticed the strange grub message as well, but that is all it was, machine reboots to grub OK.

Other than that, everything OK, approx 500mb of updates installed, one minor hitch with one library (I use the PPA for AWN ), but I sorted it quickly. ATI graphics/Sound/Compiz running fine.

Cheers

Steve

:Edit: Though I have to admit, as I set the laptop to reboot, I did shuffle through my CDs looking for my Super Grub recovery disk - Oh Ye of little faith

[kaizer]

wyrdoal, SimonTS,
I have been reading your conversation and it explained me a lot of things but i got few (stupid) questions left:

1. Do we need the double entry for /proc in the fstab? Is there an easy way to interpret these entries? (I mean compare to the lines which are partition mapping)
2. Comparing the output of blkid and fdisk -l it seems to me that sda2 is not recognized (it is also not mention in fstab. Why this?
3. In the fstab I can see 2 partitions being mounted as /. How is this possible?)

Thank you for your help

[AlbertP]

The lines with a # are ignored. That way, there's only 1 / and only 1 proc.

[kaizer]

Hi Alber P

The lines with a # are ignored. That way, there's only 1 / and only 1 proc.

for what I can see:

Here the fstab I used:


# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
proc /proc proc nodev,noexec,nosuid 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
#/dev/sda1 / ext4 rw,errors=remount-ro 0 0
UUID=1140b737-c1d0-4491-a560-cce25fe10ee3 / ext4 rw,errors=remount-ro 0 0
#swap was on /dev/sda2 during installation
UUID=eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e none swap sw 0 0
#/dev/sda3 / ext4 rw,errors=remount-ro 0 0
UUID=496d31b8-39f3-42c8-9265-742373c0d2e6 / ext4 rw,errors=remount-ro 0 0

the mentioned lines are not commented so I can see 2 references to "proc" and 2 mounting point "/"
do you agree?

[zerozero]

@Dar-es-Salaam, i assume your LMDE's grub's is on the partition (sdax) and you have another OS controlling the mbr, this way that message makes sense, GRUB can be embedded in the partition but for some reason doesn't like it too much.