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

[AlbertP]

You may need apt dist-upgrade to upgrade those packages; probably they pull an extra dependency which is only installed using dist-upgrade.

[wayne128]

In my opinion, this thread is for testing incoming repos with MInt Update manager (MU).

So I click the shield and let it do the job and check the detail inside MU.

[grizzler]

Reboot, test USB drive again. no more kernel panic, great to see it resolved.

Hate to disappoint you, but it isn't. Not for me anyway. When I safely remove my external hd, the kernel panics just as before.

I started at the other end of the list this time (i.e. I clicked and selected safely remove on an icon of one of the ext4 partitions). It seemed to go well at first, but then an error was reported about not being able to remove/dismount the (only) NTFS partition because it was busy (which it wasn't). I tried safely remove on that partition's icon (the only one still showing up on the desktop) and poof!

So it seems an external hd with more than one partition and at least one NTFS partition can still not be safely removed normally.

[wayne128]

Reboot, test USB drive again. no more kernel panic, great to see it resolved.

Hate to disappoint you, but it isn't. Not for me anyway. When I safely remove my external hd, the kernel panics just as before.

I started at the other end of the list this time (i.e. I clicked and selected safely remove on an icon of one of the ext4 partitions). It seemed to go well at first, but then an error was reported about not being able to remove/dismount the (only) NTFS partition because it was busy (which it wasn't). I tried safely remove on that partition's icon (the only one still showing up on the desktop) and poof!

So it seems an external hd with more than one partition and at least one NTFS partition can still not be safely removed normally.

Interesting..

anyway my USB partitions have combination of ext, ntfs

Device Boot Start End Blocks Id System
/dev/sdd1 1 3825 30724281 83 Linux
/dev/sdd2 3826 4080 2048287+ 82 Linux swap / Solaris
/dev/sdd3 4081 7904 30716280 83 Linux
/dev/sdd4 7905 77826 561642609+ 5 Extended
/dev/sdd5 7905 10454 20482843+ 83 Linux
/dev/sdd6 10455 13004 20482843+ 83 Linux
/dev/sdd7 13005 15554 20482843+ 83 Linux
/dev/sdd8 15555 18104 20482843+ 83 Linux
/dev/sdd9 18105 20654 20482843+ 83 Linux
/dev/sdd10 20655 23204 20482843+ 83 Linux
/dev/sdd11 23205 64061 328182526+ 7 HPFS/NTFS
/dev/sdd12 64062 65460 11229184 83 Linux
/dev/sdd13 65461 66333 7012341 83 Linux
/dev/sdd14 66334 67588 10075136 83 Linux
/dev/sdd15 67588 68168 4659200 83 Linux
/dev/sdd16 68168 68951 6285312 83 Linux
/dev/sdd17 68951 73122 33505280 7 HPFS/NTFS

[grizzler]

This is mine:

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13055 104857600+ 7 HPFS/NTFS
/dev/sdb2 13055 15726 21461462+ 83 Linux
/dev/sdb3 15727 21070 42925680 83 Linux
/dev/sdb4 21071 77825 455884537+ 5 Extended
/dev/sdb5 21071 26414 42925648+ 83 Linux
/dev/sdb6 26415 31758 42925648+ 83 Linux
/dev/sdb7 31759 37102 42925648+ 83 Linux
/dev/sdb8 37103 42446 42925648+ 83 Linux
/dev/sdb9 42447 47790 42925648+ 83 Linux
/dev/sdb10 47791 77564 239159623+ 83 Linux
/dev/sdb11 77565 77825 2096451 82 Linux swap / Solaris

Maybe it's the position of the NTFS partition. Or the boot flag. Or a combination of the two. Or something else entirely.
I don't know. All I know is it's still causing a panic.

[wyrdoak]

This is why I had to use "dphys-swapfile" to create a swap file for LMDE

@ ~ $ sudo swapon -a
[sudo] password for :
swapon: cannot find the device for UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a

But Mint 10 uses/finds it.

And I still get a kernel panic if I try "safely remove device" for my usb harddrives, but I can just put the plug and replug all day long with not problems.(I wouldn't suggest it often) I originally formatted them when I was using Win7 so the file type is "fusebik" if that makes a difference.

Well back to playing.

[SimonTS]

@Wyrdoak

If this comes across as condescending then it is not intended as such - you seem to be fairly switched on, but I wanted to check something.

Is the UUID returned by the 'swapon' error message the correct UUID for your swap partition? Have you checked your /etc/fstab file? There are bugs in the Debian-based installer that can cause weird things to happen, especially if you don't let LMDE install GRUB automatically. I had double entries for /proc, incorrect entries for both / and swap (as well as the correct mount points)... I first learnt about the bugs due to testing LiquidLemur which has borrowed the same installer.

[kmb42vt]

This is why I had to use "dphys-swapfile" to create a swap file for LMDE

@ ~ $ sudo swapon -a
[sudo] password for :
swapon: cannot find the device for UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a

But Mint 10 uses/finds it.

And I still get a kernel panic if I try "safely remove device" for my usb harddrives, but I can just put the plug and replug all day long with not problems.(I would suggest it often) I originally formatted them when I was using Win7 so the file type is "fusebik" if that makes a difference.

Well back to playing.

Yes, there's a problem with the Dec 2010 LMDE release having problems finding an already existing swap file. In fact it has a problem with setting up a proper fstab file at all. In my experience it's always adding the wrong uuid for the swap drive, adding double entries for the swap partition--located on two different partitions no less (my shared swap partition is sda5 in my case) as well as adding entries for partitions with the wrong file systems like ext3 for example (all my partitions are ext4 with the exception of my swap partition which is ext2 of course). It always manages to get my root partition right though on my test partitions (no separate Home partition for my test installations). I always have to rebuild my fstab file manually after a fresh install of LMDE Dec, 2010 and I can safely say the cause of this messed up fstab file is due to updating an 8 month old release. So much fun though.

I'm headed out at the moment but I'll run the "Incoming" updates as soon as I get back. I'm particularly interested in the external USB HDD kernel panic. The new "incoming" kernel is 2.6.39-3 and I'm currently running the Liquorix version of the same kernel which doesn't exhibit that particular problem. My external HDD has only one NTFS partition on it though so we'll see.

[wyrdoak]

SimonTS
I learned a long time ago on the Internet to assume I'm misunderstood or I'm miss understanding. So I didn't think an of that.

I don't know yet what it's supposed to look like yet, but here's my "fstab"

Looks like my swap partition was in use on boot but then......

# /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
# / was on /dev/sda1 during installation
UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f / ext3 errors=remount-ro 0 1
# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
proc /proc proc nodev,noexec,nosuid 0 0
# /dev/sda3 / ext4 rw,errors=remount-ro 0 0
UUID=496d31b8-39f3-42c8-9265-742373c0d2e6 / ext4 rw,errors=remount-ro 0 0

[SimonTS]

OK, can you also give us the outputs from;-

Code: Select all

sudo fdisk -l
sudo blkid

[zerozero]

Ok here's the results:


sudo blkid
/dev/sda3: UUID="496d31b8-39f3-42c8-9265-742373c0d2e6" TYPE="ext4"
/dev/sda5: UUID="eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e" TYPE="swap"
/dev/sda1: UUID="1140b737-c1d0-4491-a560-cce25fe10ee3" TYPE="ext4"
/dev/sdb1: LABEL="FreeAgent Drive" UUID="F08ED84B8ED80C4A" TYPE="ntfs"
/dev/sdc1: LABEL="Books" UUID="4E48E75448E738FB" TYPE="ntfs"

Code: Select all

 ~ $ sudo fdisk -l
[sudo] password for :

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b6f7e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       12275    98592768   83  Linux
/dev/sda2           18712       19458     5993473    5  Extended
/dev/sda3           12276       18711    51697170   83  Linux
/dev/sda5           18712       19458     5993472   82  Linux swap / Solaris

Partition table entries are not in disk order

Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa4b57300

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       38913   312568641    7  HPFS/NTFS

Disk /dev/sdc: 500.1 GB, 500107860992 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x746c4ee2

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       60801   488384001    7  HPFS/NTFS

[wyrdoak]

I think sda5 is the soft-swap made by "dphys-swapfile"

[zerozero]

1st update pack installed (though MU-debian), and nothing special to report:
- the MESA breakage was solved with ease by MU-debian, nvidia updated, compiz working, all's well
- as for the others updates (39-3 kernel, new firmware, pulseaudio, grub, vlc, i can't find a regression: the system works as this morning (this with half hour play after the update)

[wyrdoak]

Looks like I got the headers for kernel 2.6.39-3 but not the image. Not seeing it in the package manager ether, only the headers.

[zerozero]

linux-headers-2.6.39-2-common:amd64 (2.6.39-2, 2.6.39-3), gcc-4.6-base:amd64 (4.6.1-1, 4.6.1-4), libpwl5:amd64 (0.11.2-3, 0.11.2-4), libklibc:amd64 (1.5.22-1, 1.5.23-2), libgl1-mesa-glx:amd64 (7.10.2-3, 7.10.3-3), mplayer:amd64 (1.0~rc4+svn20110505-0.1, 1.0~rc4+svn20110505-0.2), libpcap0.8:amd64 (1.1.1-6, 1.1.1-8), libx86-1:amd64 (1.1+ds1-6, 1.1+ds1-7), at:amd64 (3.1.12-1, 3.1.13-1), firmware-qlogic:amd64 (0.30, 0.32), pulseaudio-module-x11:amd64 (0.9.21-4, 0.9.21-4.1), perl-base:amd64 (5.12.3-7+b1, 5.12.4-1), libgomp1:amd64 (4.6.1-1, 4.6.1-4), gdebi-core:amd64 (0.7.1, 0.8.0), pulseaudio-module-gconf:amd64 (0.9.21-4, 0.9.21-4.1), firmware-iwlwifi:amd64 (0.30, 0.32), libgs9-common:amd64 (9.02~dfsg-2, 9.02~dfsg-3), libgnutls26:amd64 (2.10.5-1+b1, 2.10.5-2), perl-modules:amd64 (5.12.3-7, 5.12.4-1), libavahi-glib1:amd64 (0.6.30-3, 0.6.30-5), klibc-utils:amd64 (1.5.22-1, 1.5.23-2), linux-image-2.6.39-2-amd64:amd64 (2.6.39-2, 2.6.39-3),

[wyrdoak]

Zerozero,
OK I have all them and I now see Linux-patch-debian-2.6.39 install version 2.6.39-3.

I just don't see an image, unsure how debian does things but was expecting a kernel image and another entry in Grub.

[SimonTS]

@Wyrdoak;-

There's your problem then. The error message refers to

swapon: cannot find the device for UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a

which is the same UUID as specified in your /etc/fstab file

# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none swap sw 0 0

The soft-swap isn't sda5. sda5 is used for the first logical partition, no matter whether you have 1, 2 or 3 primary partitions. Modify your /etc/fstab file to read

# swap was on /dev/sda2 during installation
UUID="eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e none swap sw 0 0

instead. You also have an error in your / partition information in fstab. Your file reads;-

# / was on /dev/sda1 during installation
UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f / ext3 errors=remount-ro 0 1

When the actual UUID for your / partition is 1140b737-c1d0-4491-a560-cce25fe10ee3, but I am not sure how much harm this can do as your system is obviously booting correctly from the information in your grub.cfg file. Can someone else advise on this.
And you have the 'double /proc' entry, although that doesn't seem to cause problems.

[zerozero]

wyrdoak, at first i too questioned why there wasn't another entry in grub, but if you look in synaptic the pkgs are still linux-headers-2.6.39-2 and linux-image-2.6.39-2, only in the description the v. number changed to 39-3, so it's a minor kernel update

[wyrdoak]

SimonTS here's my fstab now:

# /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
# / was on /dev/sda2 during installation
UUID="eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e none swap sw 0 0
# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
proc /proc proc nodev,noexec,nosuid 0 0
# /dev/sda3 / ext4 rw,errors=remount-ro 0 0
UUID=496d31b8-39f3-42c8-9265-742373c0d2e6 / ext4 rw,errors=remount-ro 0 0


But I'm getting this now for swapon:

swapon: cannot find the device for UUID="eb5fb1ea-b4c3-4f9c-9a9c-a01c7a3d9a5e
swapon: cannot find the device for UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a

But I'm still showing a working swapfile in system monitor. using dphys-swapfile.

[wyrdoak]

ZeroZero,

Thank you for the info, now I have an idea of what happen.

Looks like the kernel panic in safely remove hardware is a problem dismounting a NTFS drive. Mine are just data drives so they are not used all the time, just pulling (if necessary)the plug causes no problems to the system.