Wheezy - Removable media becomes unreadable after time passes
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Wheezy - Removable media becomes unreadable after time passes
Good evening everyone.
As the subject says I'm running wheezy and I'm having trouble with removable devices 'removing' themselves from the system after a period of time. The amount of time when the disconnect occurs is undetermined. It just happens.
So here's a rundown. I have wheezy installed to a jump drive which I boot to from a desktop or laptop. I typically run VMs through virtualbox and I have an external drive that hosts the VM images. I can connect either through esata or USB 2/3 but it doesn't change the situation. After I get up and running the removable drive will suddenly become inaccessible where virtualbox will report it's read only. Attempting to run fdisk on it to view partitions through the terminal results in 'bad superblock'. Oddly, disconnecting and re-connecting the drive brings it back to life.
Whenever I mount the external volume (either through terminal or gui), it's always mounted with root permissions. I'm curious if the permissions to the drive are lost similar to how root permissions for some actions 'time out' and you need to put in your password again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.