=== Guest31934 is now known as ogry === ogry is now known as ogra [01:22] good evening! [01:24] I've a problem with an external USB harddisk, a WD Elements 2GB. The only partition has its last sector beyond the last sector reported by the kernel for the disk. [01:25] Any ideas how I find the missing bits to get disk size and partition size matching? [02:02] Hi, I'm running into a small issue with Kernel 2.6.32-27.49 and dmcrypt [02:04] when using Truecrypt 7.0a to create an encrypted partition the length of the device, I'm receiving an error, "device-mapper: reload ioctl failed: invalid argument command failed" [02:07] I haven't had issues with Truecrypt making use of dm-crypt/cryptsetup in the past even on the same distribution in the past (Ubuntu 10.04) [02:32] presume I caught channel sleeping [02:32] a little mor information, I was able to create volumes in truecrypt as late as last week before the recent kernel update pushed into Ubuntu 10.04 LTS [02:33] so this regression appears to be a result of the kernel update [02:35] Some more: My problem is _exactly_ the same as http://ubuntuforums.org/archive/index.php/t-1603349.html, see comments shayno90 October 28th, 2010, 07:58 PM and srs5694 October 28th, 2010, 11:39 PM [02:36] fdisk -l output for the 2TB-drive is identical [03:21] small update, kern log listed the following error after two attempts to encrypt partitioned device [03:23] http://pastebin.com/Am9YR9QC [08:29] problem solved, sorry for disturbing chan [08:31] prior disk was not removed correctly from OS prior to hotswap and insertion of new HDD. This appears to have caused the issue with cryptsetup === yofel_ is now known as yofel [14:38] Is anyone alive? [14:40] Anyone out there? [14:41] no. [14:51] LetoThe2nd: Seemingly [14:52] lag: its the same as always... have a look at the topic, especially the last sentence :-) [14:53] LetoThe2nd: Na, it's okay - I'll just grab them when they return === solarion_ is now known as Solarion === Quintasan_ is now known as Quintasan [15:06] Can someone take a look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/694825 ? It's driving me mad, my installation crashes almost right after booting [15:06] Launchpad bug 694825 in linux (Ubuntu) "ata_bmdma crashing at random(?) (affects: 1) (heat: 6)" [Undecided,New] === ogra_ac is now known as ogra [17:02] grmbl [20:14] godamned ! [20:14] * ogra starts to hate the ubuntu kernels with passion [20:41] hello [20:42] can anybody help me with kernel crashes? [20:42] afunix_: have you read https://wiki.ubuntu.com/Kernel/Debugging ? [20:43] yes. i have strange symptoms [20:44] mainline kernel (2.6.37) is crashing (kernel panic: bounce buffer is not DMA'ble from swiotlb) [20:44] ubuntu maverick last kernel has random hangs [20:45] crashes have appeared after I've upgraded my laptop memory up to 4Gb (x86_64 arch) [20:46] I've run memtest. I've run BIOS built-in hardware tests. Those tools report no errors [20:47] afunix_: could I see your dmesg? I was wonder if you could have ran into the same issue as me [20:47] i've googled "kernel panic: bounce buffer is not DMA'ble" and found such errors were 2007-2008 in redhat kernels [20:48] http://dl.dropbox.com/u/6312269/dmesg.txt [20:48] afunix_: uh, that is from a mainline kernel? [20:49] that is current ubuntu [20:49] oh I see [20:49] i cannot boot mainline [20:49] afunix_: you get random hang with maverick ones? [20:49] yes [20:50] 2.6.35-24-generic x86_64 [20:51] afunix_: You'd better file a bug report, I was trying to grab attention here for at least two days but without success, bugs at launchpad may get adressed faster [20:51] sometimes there are just hags, sometimes I can see blinking caps+scroll lock. sometimes (when I'm in console) I can see a lot of "oops" messages [20:51] well, I'm not sure if it is a memory problem or some real kernel bug [20:52] did you try booting without the additional RAM? [20:53] yes. When I'm booting with 2Gb it works fine. But when there is 4Gb it hangs. [20:53] but two different memtesting tools says that everything is fine [20:54] I've got such line in dmesg: "Memory: 4041352k/4456448k available (5711k kernel code, 264216k absent, 150880k reserved, 5379k data, 908k init)" [20:54] well, I would open a bug in your case, they will just close it if it's your memory's fault in the end [20:54] BIOS reports 256Mb of RAM as absent. So, maybe there is some errors in the way kernel detects and occupies memory [20:56] hmmm. I'll try, but I think that bug report can stay unresolved forever... === ogra is now known as Guest180