Public bug reported:
Software: Ubuntu 12.10 amd64, Linux 3.5.0-25.39-generic
Hardware: Thinkpad X230, Ultrabase series 3, generic Samsung SATA hard drive in
Ultrabase HDD bay
To reproduce:
Boot system, use drive in dock bay. Suspend while docked, undock, "go to work",
resume (dock bay drive previously on /dev/sdb1 isn't there anymore), suspend
again, "return home", dock, resume.
Now the bay drive isn't shown anymore, there is no /dev/sdb or any hint of its
existence in udisks, fdisk, mtab, ...
Running 'udevadm info -ap /sys/devices/platform/dock.2' simply shows
'ATTR{docked}=="0"' among others.
Workaround:
Simply undocking and redocking while the system is awake repopulates /dev/sdb1.
As I haven't figured out a software way to do it, this amounts to pulling the
docks lever and dropping it again every time after docking.
More:
Undocking before suspend (before "going to work") is clunky (have to open lid
once more) but fixes this problem.
As does resuming before docking again (after "return home"), but I'd like to
avoid having to open the lid at all, and this is equivalent to the workaround
described above.
I don't know why allowing it to register the undock before suspending
the first time makes a difference when resuming in a docked-again state.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Description changed:
Software: Ubuntu 12.10 amd64, Linux 3.5.0-25.39-generic
- Hardware: Thinkpad X230, Ultrabase series 2, OCZ Vertex3 SSD in Ultrabase HDD
bay
+ Hardware: Thinkpad X230, Ultrabase series 3, OCZ Vertex3 SSD in Ultrabase HDD
bay
To reproduce:
Boot system, use drive in dock bay. Suspend while docked, undock, "go to
work", resume (dock bay drive previously on /dev/sdb1 isn't there anymore),
suspend again, "return home", dock, resume.
Now the bay drive isn't shown anymore, there is no /dev/sdb or any hint of
its existence in udisks, fdisk, mtab, ...
Running 'udevadm info -ap /sys/devices/platform/dock.2' simply shows
'ATTR{docked}=="0"' among others.
Workaround:
Simply undocking and redocking while the system is awake repopulates
/dev/sdb1. As I haven't figured out a software way to do it, this amounts to
pulling the docks lever and dropping it again every time after docking.
More:
Undocking before suspend (before "going to work") is clunky (have to open lid
once more) but fixes this problem.
As does resuming before docking again (after "return home"), but I'd like to
avoid having to open the lid at all, and this is equivalent to the workaround
described above.
I don't know why allowing it to register the undock before suspending
the first time makes a difference when resuming in a docked-again state.
** Description changed:
Software: Ubuntu 12.10 amd64, Linux 3.5.0-25.39-generic
- Hardware: Thinkpad X230, Ultrabase series 3, OCZ Vertex3 SSD in Ultrabase HDD
bay
+ Hardware: Thinkpad X230, Ultrabase series 3, generic Samsung SATA hard drive
in Ultrabase HDD bay
To reproduce:
Boot system, use drive in dock bay. Suspend while docked, undock, "go to
work", resume (dock bay drive previously on /dev/sdb1 isn't there anymore),
suspend again, "return home", dock, resume.
Now the bay drive isn't shown anymore, there is no /dev/sdb or any hint of
its existence in udisks, fdisk, mtab, ...
Running 'udevadm info -ap /sys/devices/platform/dock.2' simply shows
'ATTR{docked}=="0"' among others.
Workaround:
Simply undocking and redocking while the system is awake repopulates
/dev/sdb1. As I haven't figured out a software way to do it, this amounts to
pulling the docks lever and dropping it again every time after docking.
More:
Undocking before suspend (before "going to work") is clunky (have to open lid
once more) but fixes this problem.
As does resuming before docking again (after "return home"), but I'd like to
avoid having to open the lid at all, and this is equivalent to the workaround
described above.
I don't know why allowing it to register the undock before suspending
the first time makes a difference when resuming in a docked-again state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161973
Title:
Ultrabase suspend cycle loses bay HDD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1161973/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
