[Bug 1688213] Re: Filesystem could not be read/written anymore

2018-05-08 Thread Emiliano Vavassori
Cannot run the indicated command; logs are long gone and I'm not using
anymore this kernel (using linux-image-generic-hwe-16.04, which is
working fine).

Frankly I do think we may close the bug as WONTFIX, since the kernel
version is not anymore in the repositories, plus if you are running
xenial you should have migrated long ago to linux-hwe. Please advise.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688213

Title:
  Filesystem could not be read/written anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688213/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688213] Re: Filesystem could not be read/written anymore

2017-05-04 Thread Emiliano Vavassori
@volt: I have a different DE (based on GNOME) so I cannot assure the
behavior between the two DEs are similar. What happens (for example) is
that the Telegram Desktop application stop to work, kills itself and
cannot be reopened, for example. Icons to shutdown the session or the PC
are missing. It is a little slower than normal and any other operation
usually silently fails.

No dual booting here, just Zorin, installed on UEFI.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688213

Title:
  Filesystem could not be read/written anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1688213/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1687025] Re: Background disappears when running, file system inaccessible

2017-05-04 Thread Emiliano Vavassori
Opened other bug report as I am not sure the issue here is identical.
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1688213

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687025

Title:
  Background disappears when running, file system inaccessible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1687025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1688213] [NEW] Filesystem could not be read/written anymore

2017-05-04 Thread Emiliano Vavassori
Public bug reported:

Description:Zorin OS 12.1
Release:12
Environment:Ubuntu 16.04 LTS - amd64
Severity: Critical
Affected versions:
linux-image-4.8.0-49-generic:
  Installed: (None)
  Candidate:  4.8.0-49.52~16.04.1
  Version table:
 4.8.0-49.52~16.04.1 500
500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
linux-image-4.8.0-51-generic:
  Installed: 4.8.0-51.54~16.04.1
  Candidate:  4.8.0-51.54~16.04.1
  Version table:
 *** 4.8.0-51.54~16.04.1 500
500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
Hardware information: Dell XPS 15 (9550), lshw attached as hardware.info.txt.

Description:
At a random time when normally using the PC, the disk is rendered unavailable 
and any commands run or file accessed has a read error. Poweroff and reboot 
hang because of unavailable disk. System is completely unusable and needs a 
forceful restart (pushing the power on button).
Misbehaviour happens 100% of the sessions, but with random time to appear (10 
minutes to 2 hours after the boot). NOTE: Log harvesting is quite impossible 
because the disk is rendered unavailable also to system process.

Steps to reproduce:
1) Boot with affected kernel and work normally
1) Wait between 10 minutes and 2 hours for the disk to be rendered unavailable
2) Power cycle the PC using the power button

Workaround:
There are no strict workaround known for the kernel versions affected; once 
misbehaviour has happened, the only thing that makes the PC usable again is to 
boot with previous kernel version (e.g. linux-image-4.8.0-46-generic included 
and lower works as expected).

Expected result:
Kernel does not render disk unavailable and continuously works.

** Affects: linux-hwe (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Hardware info (lshw)"
   
https://bugs.launchpad.net/bugs/1688213/+attachment/4871824/+files/hardware.info.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688213

Title:
  Filesystem could not be read/written anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1688213/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1687025] Re: Background disappears when running, file system inaccessible

2017-05-03 Thread Emiliano Vavassori
Confirming read-only access on disk with kernel versions 4.8.0-49
(linux-image-4.8.0-49-generic 4.8.0-49.52~16.04.1) and 4.8.0-51 (linux-
image-4.8.0-51-generic 4.8.0-51.54~16.04.1). Downgrading kernel to
4.8.0-46 (linux-image-4.8.0-46-generic 4.8.0-46.49~16.04.1) does not
show the issue.

My hardware is a Dell XPS 9550 with nve harddisk.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687025

Title:
  Background disappears when running, file system inaccessible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1687025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1580237] Re: pam_mount doesn't mount when using sgrp

2016-07-11 Thread Emiliano Vavassori
Hi,

Just try to see if this fixes:
* Upgrade to the latest version (on 14.04, 4.3.9);
* Add to /etc/samba/smb.conf file in the [global] section on the client:
winbind expand groups = 1 
* Restart smbd, nmbd and winbind

Fixed your same issue. sgrp seems to mount right after this procedure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580237

Title:
  pam_mount doesn't mount when using sgrp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1580237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs