"IOError: [Errno 30] Read-only file system" when installing SME Server 8 from USB
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"IOError: [Errno 30] Read-only file system" when installing SME Server 8 from USB
Hello,
I managed to make my 8.0GB USB flash drive boot the current SME Server 8 beta ISO image. The installation program starts when I boot from USB, and configuration of install options worked fine.
After pressing "Install now", the installation starts, then ends with a python exception error: IOError: [Errno 30] Read-only file system
I tried it twice and got the same error, what does this mean and how should I alleviate this problem?
If a Linux server detects an error on a drive, it will change the file system to read only, so that you have an opportunity to back-up data without risking further damage to the file system.
Normally rebooting will fix the error, but if you're getting the error during the install, you might be best to delete and recreate or ....
I was getting this error when my drive was bad. Replace the drive with new one and everything was fine. Don't know give it a try.
Thanks for the tip! I will try it. However, if using a different USB stick still doesn't work, would that imply the ISO image I used might be bad? Thanks 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.