I also have the BCM4328 (Rev 03) chipset. It is not detected by the
default Hardy 8.04 install, as advertised.
Likewise I have had some success with the ndiswrapper. I have a Dell
Inspiron 1721, and am using an XP driver that I found on their website.
I don't have a lot of experience with
I am upgrading from 7.10 to 8.04 LTS with 2.6.22-16-server.
Using the upgrade manager the upgrade has been completed without a
problem.
--
Gutsy-Hardy upgrade hangs in localedef
https://bugs.launchpad.net/bugs/249340
You received this bug notification because you are a member of Ubuntu
Bugs,
Here is an example of a bunch of failover events from a rebooted storage
controller. You can see that there are others similar to what you
mentioned above.
** Attachment added: "syslog containing failover"
This is the output of multipathd show config, which is the effective
multipath.conf file.
** Attachment added: "multipath.config"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+attachment/4680592/+files/multipath.config
--
You received this bug notification because
I have no multipath.conf, we just use the defaults that are built in for
our storage.
multipath -ll for that particular host is not going to look good right
now as I'm having an issue with an Emulex device. Until I get my
hardware issue resolved I don't want to send you an output that will be
Public bug reported:
For some reason, if I leave my Ubuntu VM up for a prolonged period of
time the machine will lose connection to the network. ip addr shows
that the nic port no longer has an address and an examination of the
syslog shows this:
May 27 14:19:38 matt-VirtualBox
I have finally been able to verify that this is reproducible with the
released 16.04 from the ISO.
What else can be provided here to move this bug along?
(This is being tracked internally in CQ 860251)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Maybe the problem is not in Avahi, but it is still a problem somewhere.
This bug continues to plague my vm. Today I noticed that if I try to
interact with the network port, I am told that it is unknown, does this
have something to do with it?
matt@matt-VirtualBox:~$ ip addr
1: lo:
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
Description: Ubuntu Xenial Xerus (development b ranch)
Release: 16.04
2) The version of the package you are using, via 'apt-cache policy
pkgname'
systemd:
Installed: 229-3ubuntu1
Candidate: 229-3ubuntu1
3)
This bug is being tracked in Netapp's internal bug tracking system:
LSIP200858428
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969
Title:
Udev rule causes automatic incorrect unmount of dm
Public bug reported:
I have 4 servers running the latest 16.04 updates from the development
branch (as of right now).
Each server is connected to NetApp storage using iscsi software
initiator. There are a total of 56 volumes spread across two NetApp
arrays. Each volume has 4 paths available to
Public bug reported:
I have 4 servers running the latest 16.04 updates from the development
branch (as of right now).
Each server is connected to NetApp storage using iscsi software
initiator. There are a total of 56 volumes spread across two NetApp
arrays. Each volume has 4 paths available to
Can you comment on when or if this fixed package might be pushed to the
Xenial repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969
Title:
Udev rule causes automatic incorrect unmount of dm
Contents of fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' 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).
#
#
# / was
This contains the configuration of my iscsi sessions. It is a tar of
the entire /etc/iscsi folder, it should show what we've got going on.
** Attachment added: "iscsi.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4648082/+files/iscsi.tar.gz
--
You
Here is the requested journal.txt file.
I had a bit of difficulty after performing the requested operations, my
server kept booting into the (initramfs) prompt.
The journal log may contain more than one reboot attempt.
** Attachment added: "journal.txt"
And just for good measure this is my /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet
I definitely have remote filesystems mounted (using _netdev if that
matters) when I experience this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with
I think I missed some questions. I'll try to aggregate:
1. Contents of "/proc/cmdline"
BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic
root=UUID=584a6a87-26b5-4262-b316-ca9d1c3a8a20 ro
2. Installed from an earlier ISO, probably one of the Beta images and
then dist-upgraded through till now.
3.
3. Grep was hanging up on some device files so...
root@ICTM1612S02H2:/# find / -xdev -type f -print0 |xargs -0 grep -H
"set-log-level"
Binary file /usr/bin/systemd-analyze matches
/usr/share/bash-completion/completions/systemd-analyze:
[LOG_LEVEL]='set-log-level'
I have installed a new system from the server CD. I chose Expert mode
and selected a few special options but nothing too drastic (like setting
up my NTP server and my internal mirror repository).
It does NOT seem to have these messages enabled. Maybe there was
something funky in the particular
I may have spoken too soon, I am seeing them again.
Is there any instance in which I would see these messages under normal
circumstances?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
Nothing for the system is on iscsi. They are just extra volumes that I
use for generating block or filesystem IO to our storage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
I have not touched /etc/systemd/system.conf. Looking at that file
everything is commented out so I assume defaults.
I don't see anything that says /etc/systemd/system.conf.d...I see
/etc/systemd/system/ but I haven't touched anything in there.
I don't knowingly have a call to systemd-analyze
I am not sure exactly when they start to appear.
The configuration of NTP and the internal mirror and stuff is done
inside of the installer from the "expert" option on the CD.
Then when it is installed and up I add a few more packages from the
repos.
I am not certain exactly when these start to
I have run for a bit now and have not seen anymore erroneous unmounts.
I'll call this one fixed and verified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969
Title:
Udev rule causes automatic
Ok, then how can I turn it off?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
Continuous messages from systemd: dm disk appears twice
To manage notifications about this bug go to:
Public bug reported:
During a path loss event, the syslog is showing these messages where
prior to the recent upgrade to multipath-tools I didn't see anything
like this. To me this seems like either a problem or it seems like a
print message that should go into a different log file.
Apr 13
In the above, the two NICs used for iSCSI traffic are the enp130s0 and
the enp4s0f0.
In case you were wondering I have another server running ipv4 and it
also hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the requested syslog.
Reboot happens after:
Apr 14 09:49:42 ICTM1612S02H1 root: MDS: Rebooting Now
** Attachment added: "requested syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4636878/+files/syslog
--
You received this bug notification because
I'm not suggesting that you remove it, but I don't know how it got set
and I am not intentionally setting debug level logging. Is it possible
that the bug is not that this output exists but instead that the
debugging is turned on?
--
You received this bug notification because you are a member
root@ICTM1612S02H1:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The
I can confirm that the messages seem to be cleaned up with your fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093
Title:
multipath-tools update introduced syslog messages about partx
To
FYI, this behavior persists with the released version of 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
debug messages are enabled
To manage notifications about this bug go
rc_micha: Your volumes aren't mounted, but the iscsi sessions are logged
in? If you log out of your iscsi sessions does it shutdown clean?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Do I have to rebuild the package with this debdiff before it can be
accepted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093
Title:
multipath-tools update introduced syslog messages about
We're still hoping for a resolution on this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694
Title:
[860730] Host experiencing constant session termination and recreation
while using
Still looking for a resolution to this one.
** Changed in: ubuntu
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
debug messages are enabled
To manage
Any movement here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636862
Title:
Shutdown hangs with active iscsi sessions
To manage notifications about this bug go to:
Any idea on this one folks?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage notifications about this bug go to:
Installed the most recent build of Zesty (zesty-server-amd64.iso
2017-02-22 06:54676M).
I was able to:
1. Confirm the issue still exists.
2. Confirm that the issue is not caused by multipath (i.e. it still occurs
during reboot when multipathing is disabled).
--
You received this bug
Didn't take as long as I thought. Installed the most recent build of
Zesty (zesty-server-amd64.iso 2017-02-22 06:54676M).
I was able to:
1. Confirm the issue still exists.
2. Confirm that the issue is not caused by multipath (i.e. it still occurs
during reboot when multipathing is
It is possible to test without multipath, this will take some time as I
no longer have anything with 16.04 installed. For fun I may go ahead
and try with 17.04 so we can figure out if it still exists then we'll
kind of kill two birds with one stone.
--
You received this bug notification because
iSCSI disks are not the root/boot disks.
Multipath IS in use. Hence the /dev/mapper at the beginning of the disk
names.
Yes I have tried 16.10, it is still present and I have another bug for
that release. https://bugs.launchpad.net/bugs/1636862
--
You received this bug notification because
There is clearly something wrong here.
FWIW This issue did not exist in 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage
** Changed in: systemd (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage notifications
For completeness, I upgraded to 16.04.1, the issue is still present.
I upgraded to the latest xenial-updates packages as of 10/24/16 and the
issue is still present.
I then re-installed with 16.10 and the issue is still present. I guess
I'll open a new bug for 16.10 and refer back to this one.
If this is still a problem, what do we do now? Do I just keep testing
with new releases and file new bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with
New bug for 16.10:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636862
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage
Public bug reported:
This is a duplicate of the bug listed here:
https://bugs.launchpad.net/bugs/1569925 for 16.04.
That bug was automatically closed though the problem still persists. I
am opening this bug for 16.10 in hopes that it will catch somebody's
attention.
I have 4 servers running
Sure, we can give Debian a shot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694
Title:
[860730] Host experiencing constant session termination and recreation
while using jumbo frames
To
Wait I'm confused, build what in a PPA? Didn't you just want us to run
Debian and test what the version of open-iscsi it comes with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694
Title:
I can confirm that the daily 17.10 build does not exhibit the problem.
Interestingly, the first time we tried we forgot to stop running IO to
our iSCSI volumes and it _looked_ like we reproduced the problem, then
the IOs timed out and our application stopped and we were able to
complete the
I have node.session.timeo.replacement_timeout = 20, which seems
completely reasonable in my book.
We have already established that this occurs without multipath even
enabled, thus it is not a multipath settings problem.
Also I have no containers.
--
You received this bug notification because
My test configuration has long since been re-tasked. I will eventually
be able to come back and test as you ask, but it may take a few weeks.
If anyone else on the bug has their systems up and available, please
test and reply.
--
You received this bug notification because you are a member of
As I said I don't have one up right now, but Comment 3 above has my
interfaces for one of the recreates.
Nothing bothered me in any way. I wanted to make sure that you knew
that I wasn't one guy who was looking to fix his one system, that's all.
You said "Usually those type of "partnership"
Please let me explain who I am and what we do to possibly shed some
light on this.
I am an Interoperability engineer at NetApp. We test our storage
products with many popular operating systems, adapters, protocols and
switches, in varying combinations.
We test software initiator iscsi
Excellent, thank you for the details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage notifications about this bug go to:
That's awesome sir, thank you for your diligence.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage notifications about this bug go
I apologize for my ignorance, but now that tall these check ins have
occurred, how do I know when an installable package has been built and
is available in the various repos?
And thank you @inaddy for the diligence getting this one resolved.
--
You received this bug notification because you are
Thanks, and will notifications appear here in the bug during these
stages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
To manage
Ok, I am officially giving up on this one, some one go ahead and close
this out please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
debug messages are enabled
To manage
Public bug reported:
I work at NetApp and we have a storage array that has dual SAS
controllers that present multiple paths to a single volume. We usually
are able to boot from SAN using SAS and utilize multipath on the root
volume. I have tried everything I can think of and don't get this
This has all been testing with Ubuntu 20.04. When I did have it install
to a single path, I updated everything to the latest (even tried the
proposed stuff) up to 3/30/2020.
When I switched tactics and tried to reinstall I was using an ISO from a
couple weeks ago.
--
You received this bug
At this point I have to assume that booting form SAN using a SAS
multipath device is not compatible with Ubuntu 20.04 and will advise
against its attempted use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Anybody have anything to add here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870146
Title:
Unable to successfully boot from SAN with multipath SAS volume
To manage notifications about this
Rafael, would it be wrong to simply take any existing files and save
them with an .bak extension? That way if the user really wanted their
old ID they could go get it back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, makes sense. I would say to try to follow the iscsi iqn behavior,
good idea!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867366
Title:
hostnqn fails to automatically generate after
** Changed in: nvme-cli (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874270
Title:
NVMe/FC connections fail to reestablish after controller is reset
69 matches
Mail list logo
