Difference between revisions of "Talk:Installing Arch Linux on a USB key"

From ArchWiki
Jump to: navigation, search
m (Concerns about installations on usb keys: rm closed discussion)
(I/O error on resume, arch on usb stick.)
Line 1: Line 1:
 +
I am experiencing serius I/O errors after suspending / resuming with arch on a usb key. These issues have been described in several bugreports:
 +
https://bugzilla.kernel.org/show_bug.cgi?id=30912
  
 +
I tried following the steps in
 +
https://www.kernel.org/doc/Documentation/usb/persist.txt
 +
 +
but to no avail. The usb persist feature was already activated on my USB deve but I/O errors kept coming on resume
 +
 +
I also found this post in ubuntuforums
 +
 +
http://askubuntu.com/questions/505779/suspending-with-root-on-usb
 +
 +
which explains the issue as follows
 +
 +
"...during resume there will be a race between the USB system on one hand trying to detect media and syslog on the other hand trying to write log messages from suspend and resume to disk.
 +
 +
If syslog happens to attempt a write before the USB device has been detected ext4 gets an error, which for some reason isn't handled cleanly and eventually the file system will need fsck to be run manually."
 +
 +
The author suggest patching the kernel to give kernel threads a head start on resume. Intuitively, I feel there must be an easier way!

Revision as of 20:37, 30 November 2015

I am experiencing serius I/O errors after suspending / resuming with arch on a usb key. These issues have been described in several bugreports: https://bugzilla.kernel.org/show_bug.cgi?id=30912

I tried following the steps in https://www.kernel.org/doc/Documentation/usb/persist.txt

but to no avail. The usb persist feature was already activated on my USB deve but I/O errors kept coming on resume

I also found this post in ubuntuforums

http://askubuntu.com/questions/505779/suspending-with-root-on-usb

which explains the issue as follows

"...during resume there will be a race between the USB system on one hand trying to detect media and syslog on the other hand trying to write log messages from suspend and resume to disk.

If syslog happens to attempt a write before the USB device has been detected ext4 gets an error, which for some reason isn't handled cleanly and eventually the file system will need fsck to be run manually."

The author suggest patching the kernel to give kernel threads a head start on resume. Intuitively, I feel there must be an easier way!