[Bug 52605] smb manual mounts (not in fstab) hang system
Public bug reported: Please see http://www.ubuntuforums.org/showthread.php?t=212964. When smb share is mounted via command line: $ sudo mount -t smbfs -o username=/ /// /mnt/ remote share is accessable for a short period of time (minutes) then "dissappears". That is, copies from remote share to target Linux stall, and $ls command yields "Input/Output error". In some cases, system hard- locks requiring a power cycle. /var/log/messages and dmesg show nothing. If there is someplace else I can look, let me know. Source machine is a Windows 2003 R2 system. Target system was also Windows 2003 until yesterday when Kubuntu was installed. Systems had been up and running (and communicating over the network) for several months with no issues, so source system (Windows 2003) and network are known to be reliable. When problem occurs, source system is still up and running with no messages or errors in any event logs. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- smb manual mounts (not in fstab) hang system https://launchpad.net/bugs/52605 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52605] Re: smb manual mounts (not in fstab) hang system
More information -- again please also reference http://www.ubuntuforums.org/showthread.php?t=212964. Because I have an AMD X2 64 3800+ (dual core) I've upgraded the kernel and related packages to 2.6.15-26-k7 #1 SMP PREEMPT. I tried the copy again (without much hope) and it appears to actually be working. At this point, I'm 29% through an 11GB transfer. Before I'm pretty sure it would have stalled by now. Keeping in mind that the copy is still alive and well, I also have the following entries in my /var/log/messages file: 07/11/2006 01:28:26 PM beast kernel [17182486.028000] smb_get_length: Invalid NBT packet, code=6e 07/11/2006 01:28:56 PM beast kernel [17182516.024000] smb_add_request: request [edc5ba80, mid=25199] timed out! 07/11/2006 01:28:56 PM beast kernel [17182516.024000] smb_proc_readdir_long: error=-5, breaking 07/11/2006 01:33:06 PM beast kernel [17182765.532000] smb_add_request: request [edda0bc0, mid=2932] timed out! 07/11/2006 01:37:19 PM beast kernel [17183018.16] smb_add_request: request [edc5b180, mid=51811] timed out! 07/11/2006 01:43:28 PM beast kernel [17183388.076000] smb_add_request: request [edda05c0, mid=2137] timed out! 07/11/2006 01:51:05 PM beast kernel [17183844.216000] smb_add_request: request [edda09c0, mid=23306] timed out! 07/11/2006 01:54:00 PM beast kernel [17184019.224000] smb_add_request: request [edda08c0, mid=59691] timed out! 07/11/2006 01:54:30 PM beast kernel [17184049.912000] smb_get_length: Invalid NBT packet, code=41 07/11/2006 01:55:00 PM beast kernel [17184079.912000] smb_add_request: request [edda06c0, mid=14485] timed out! 07/11/2006 02:00:25 PM beast kernel [17184404.172000] smb_get_length: Invalid NBT packet, code=20 07/11/2006 02:00:25 PM beast kernel [17184404.172000] smbiod_handle_request: smbiod got a request ... and we don't implement oplocks! 07/11/2006 02:00:54 PM beast kernel [17184433.968000] smb_add_request: request [edda0ec0, mid=21311] timed out! 07/11/2006 02:20:13 PM beast none-- MARK -- 07/11/2006 02:20:15 PM beast kernel [17185594.768000] smb_add_request: request [f551a980, mid=23417] timed out! 07/11/2006 02:25:54 PM beast kernel [17185933.532000] smb_add_request: request [f551a980, mid=8199] timed out! 07/11/2006 02:30:26 PM beast kernel [17186205.088000] smb_add_request: request [db84b1c0, mid=59391] timed out! 07/11/2006 02:39:37 PM beast kernel [17186756.076000] smb_add_request: request [d4de6bc0, mid=39232] timed out! 07/11/2006 02:53:32 PM beast kernel [17187591.204000] smb_add_request: request [d4de6dc0, mid=48595] timed out! So it *looks* like the problem may be related to the i386 kernel build. Or not -- I don't know. -- smb manual mounts (not in fstab) hang system https://launchpad.net/bugs/52605 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52605] Re: smb manual mounts (not in fstab) hang system
BAH! Sorry for the chaff -- it stalled again after all at 35% after 4.1GB. Last /var/log/message entries were: 07/11/2006 01:28:26 PM beast kernel [17182486.028000] smb_get_length: Invalid NBT packet, code=6e 07/11/2006 01:28:56 PM beast kernel [17182516.024000] smb_add_request: request [edc5ba80, mid=25199] timed out! 07/11/2006 01:28:56 PM beast kernel [17182516.024000] smb_proc_readdir_long: error=-5, breaking 07/11/2006 01:33:06 PM beast kernel [17182765.532000] smb_add_request: request [edda0bc0, mid=2932] timed out! 07/11/2006 01:37:19 PM beast kernel [17183018.16] smb_add_request: request [edc5b180, mid=51811] timed out! 07/11/2006 01:43:28 PM beast kernel [17183388.076000] smb_add_request: request [edda05c0, mid=2137] timed out! 07/11/2006 01:51:05 PM beast kernel [17183844.216000] smb_add_request: request [edda09c0, mid=23306] timed out! 07/11/2006 01:54:00 PM beast kernel [17184019.224000] smb_add_request: request [edda08c0, mid=59691] timed out! 07/11/2006 01:54:30 PM beast kernel [17184049.912000] smb_get_length: Invalid NBT packet, code=41 07/11/2006 01:55:00 PM beast kernel [17184079.912000] smb_add_request: request [edda06c0, mid=14485] timed out! 07/11/2006 02:00:25 PM beast kernel [17184404.172000] smb_get_length: Invalid NBT packet, code=20 07/11/2006 02:00:25 PM beast kernel [17184404.172000] smbiod_handle_request: smbiod got a request ... and we don't implement oplocks! 07/11/2006 02:00:54 PM beast kernel [17184433.968000] smb_add_request: request [edda0ec0, mid=21311] timed out! 07/11/2006 02:20:13 PM beast none-- MARK -- 07/11/2006 02:20:15 PM beast kernel [17185594.768000] smb_add_request: request [f551a980, mid=23417] timed out! 07/11/2006 02:25:54 PM beast kernel [17185933.532000] smb_add_request: request [f551a980, mid=8199] timed out! 07/11/2006 02:30:26 PM beast kernel [17186205.088000] smb_add_request: request [db84b1c0, mid=59391] timed out! 07/11/2006 02:39:37 PM beast kernel [17186756.076000] smb_add_request: request [d4de6bc0, mid=39232] timed out! 07/11/2006 02:53:32 PM beast kernel [17187591.204000] smb_add_request: request [d4de6dc0, mid=48595] timed out! 07/11/2006 03:15:17 PM beast kernel [17188896.604000] smb_add_request: request [ca21d2c0, mid=52996] timed out! 07/11/2006 03:25:36 PM beast kernel [17189515.176000] smb_add_request: request [ca21d4c0, mid=24704] timed out! 07/11/2006 03:36:40 PM beast kernel [17190179.484000] smb_get_length: Invalid NBT packet, code=6f 07/11/2006 03:36:40 PM beast kernel [17190179.484000] smbiod_handle_request: smbiod got a request ... and we don't implement oplocks! -- smb manual mounts (not in fstab) hang system https://launchpad.net/bugs/52605 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70551] Cannot boot to RAID1 /boot after successful Edgy install
Public bug reported: After successfully installing Edgy AMD64 (from scratch) and creating the following: /boot - RAID1 / - RAID0 /home - RAID0 Grub errors out with "Error 15: File not found" This is with software RAID using two SATA II disks. Booting with recovery disk shows no /dev/mdx devices, even though menu.lst references /dev/md1. Installing Dapper (i386) from scratch on the same system works fine. Please let me know what other information I can provide to assist in troubleshooting. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Cannot boot to RAID1 /boot after successful Edgy install https://launchpad.net/bugs/70551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70551] Re: Cannot boot to RAID1 /boot after successful Edgy install
I'm not so sure this is a grub issue (but it may be). Grub is referencing a /dev/md1 device (which would normally be correct), but when I boot the system with the rescue disk, there are no /dev/mdx devices at all. There *should* be md1 for the RAID1 /boot partition, and two others for the RAID0 / and /home partitions. It seems to me that grub is doing the right thing when it runs at the end of the installation, but the devices are not present when the system reboots. The md devices are there immediately after they are created, otherwise the partitions couldn't be written to and the installation would fail. I can re-install the system and check various things out if you'd like. As long as I don't have to format my /home partition. -- Cannot boot to RAID1 /boot after successful Edgy install https://launchpad.net/bugs/70551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53633] Re: Kubuntu Dapper Installer does not support MD devices
I don't know if this is still relevant, but I encountered the same issue with the Dapper installer (with Ubuntu as well as Kubuntu, of course). I wasn't looking at the LVM entry, but in order to get the RAID configuration entry to appear during the partitioning stage of installation, you have to create at least one partition and set it's usage (or file system, I forget) to RAID (again, I forget the exact text, but it's obvious once you see the menu - it's all that way at the bottom under all the various file system types you can choose). Once you set a given partition to be part of a RAID array, you'll get the "Configure RAID" menu item. -- Kubuntu Dapper Installer does not support MD devices https://launchpad.net/bugs/53633 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70551] Re: Cannot boot to RAID1 /boot after successful Edgy install
Another note: When I install Dapper into the RAID1 configuration from scratch, it works (as noted above). If I then upgrade from Dapper to Edgy via the Upgrade Manager, the system continues to work -- that is, grub boots the system fine with /boot on RAID1 device and menu.lst references /dev/md1 and finds it. It's just when installing Edgy from scratch that grub can't seem to find what it's looking for after the reboot. -- Cannot boot to RAID1 /boot after successful Edgy install https://launchpad.net/bugs/70551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70551] Re: Cannot boot to RAID1 /boot after successful Edgy install
I'm mystified. . . I installed Ubuntu 6.10 amd64 from the alternate DVD into a VM. I setup multiple disks with the RAID configuration I outlined earlier and -- it WORKED. The installation in to the VM had no trouble. The identical installation with my physical hardware won't boot as outlined above. Am I correct in inferring that this is a hardware problem then? Hardware is as follows: Motherboard: Asus A8N-SLI Premium Both on-board "hardware" raid controllers (but not "real" ones) have been disabled since I'm using software RAID. CPU: AMD Athlon 64 X2 3800+ Disks: 2 x Hitachi Deskstar T7K250 250GB Serial ATA II 7200RPM Keep in mind that this hardware will install Dapper i386 without issues to the RAID configuration I've outlined. From this Dapper installation, it will upgrade to Edgy without issue as well. The trouble only comes when I try to install Edgy amd64 from scratch (I haven't tried to install Edgy i386 from scratch, but I would assume it would have the same problem). -- Cannot boot to RAID1 /boot after successful Edgy install https://launchpad.net/bugs/70551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37675] Re: Setup video mode not supported by Dell LCD display
With the same system I was using when I posted above, I tried to run the Edgy install DVD for both K/Ubuntu. With Edgy, it reaches the point where X should start, then bombs back out to a curses screen stating that there was a problem with X and would I like a detailed error message. If I then edit xorg.conf to use vesa instead of ati, X will start and everything is fine (more or less -- vesa is not pretty). -- Setup video mode not supported by Dell LCD display https://launchpad.net/bugs/37675 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70551] Re: Cannot boot to RAID1 /boot after successful Edgy install
Good find - I'd never considered that the arrays might not be completed when the reboot comes up. However, I don't "buy" that this is the solution. Here's why: 1) If the array build wasn't complete, why does the file system not report some sort of error when the Ubuntu installation copies all the files three seconds after the array is configured? 2) Why does Dapper not exhibit any issues? In a Dapper installation, everything "just works". Don't get me wrong - this is worth pursuing, and I appreciate you sending me this solution. I'm just not sure that this is actually going to work (yet). -- Cannot boot to RAID1 /boot after successful Edgy install https://launchpad.net/bugs/70551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 72229] Re: Switching users resets resolution to unsupported mode
I'll dl the CD and check it out. I expect to do this over the weekend. Thanks for following up - you guys (and girls) are awesome. On 8/20/07, Pedro Villavicencio <[EMAIL PROTECTED]> wrote: > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering is this still an issue > for you? The issue that you reported is one that should be reproducable > with the live environment of the Desktop CD of the development release - > Gutsy Gibbon. It would help us greatly if you could test with it so we > can work on getting it fixed in the next release of Ubuntu. You can find > out more about the development release at > http://www.ubuntu.com/testing/ . Thanks again and we appreciate your > help. > > ** Changed in: fast-user-switch-applet (Ubuntu) > Assignee: (unassigned) => Ubuntu Desktop Bugs >Status: New => Incomplete > > -- > Switching users resets resolution to unsupported mode > https://bugs.launchpad.net/bugs/72229 > You received this bug notification because you are a direct subscriber > of the bug. > -- -- Scott Reimert [EMAIL PROTECTED] -- Switching users resets resolution to unsupported mode https://bugs.launchpad.net/bugs/72229 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37675] Re: Setup video mode not supported by Dell LCD display
Haven't tried it yet. I was going to wait for Feisty to be released. On 3/9/07, Erik Andrén <[EMAIL PROTECTED]> wrote: > > What are the results using a feisty fawn herd 5 live cd? > > -- > Setup video mode not supported by Dell LCD display > https://launchpad.net/bugs/37675 > -- -- Scott Reimert [EMAIL PROTECTED] -- Setup video mode not supported by Dell LCD display https://launchpad.net/bugs/37675 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72229] Switching users resets resolution to unsupported mode
Public bug reported: Binary package hint: fast-user-switch-applet When running Ubuntu Edgy (released), switching users causes Dell 2005FPW display to change to unsupported resolution. Result is black screen with "Cannot display this mode" message. No keyboard sequences have any effect (Alt +/-, Alt-BS, Ctl-Alt-F1, etc.) and machine must be power-cycled. Note that this may be related to existing bugs 44562 and/or 68855 (at least). I wouldn't expect switching users to change resolution. ** Affects: fast-user-switch-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- Switching users resets resolution to unsupported mode https://launchpad.net/bugs/72229 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80835] Re: Beryl Crash when Logon
Beryl crashed when I started it from Gnome. I would have reported it to http://bugs.beryl-project but the Gnome bug reporter opened the Launchpad page via Firefox and requested I report it here. This worked in previous builds. Please find attached crash file. ** Attachment added: "Crash file for beryl." http://librarian.launchpad.net/6110089/_usr_bin_beryl-xgl.1000.crash -- Beryl Crash when Logon https://launchpad.net/bugs/80835 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68855] Re: Switching users freezes the machine
This issue did not affect me with 9.10 (karmic), but after wipe/new install of 10.04 beta 2, it affects me. Under karmic, I was using proprietary ATI drivers for Radeon Mobility X300 (Dell Latitude D610), but these drivers do not appear to be available with 10.04 beta 2. CTRL-ALT-BS does not restart gdm, but you can open a virtual console and restart it there. So far, issue only occurs when switching users. -- Switching users freezes the machine https://bugs.launchpad.net/bugs/68855 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
