[SOLVED] read only filesystem prevents login

Hi everyone.
I have this problem after changing from initscript to systemd and adding an external ntfs-3g drive to /etc/fstab. when i log in i get this message and xfce4 doesnt start :
-bash: /home/bb/.xlog : read-only file system
ls -la /
gives output rwxr-xr-x for /home
i also tried
#mount -o remount,rw /dev/sda4 /
with no results.
when i try to change /etc/fstab entries i get an error message saying that system is read-only...
chmod and chown dont work either with the same error message
how am i supposed to change something in a read-only system?
Last edited by memax (2012-11-15 17:39:45)

i ve not removed 'ro' from booting cmd and / is mounted with rw,relatime,data=ordered 0 1 in /etc/fstab as options

Similar Messages

[SOLVED] Read-only filesystem error

Hi there,
i'm trying to install Arch Linux (2012.10.06) about a week.
I have problem, that i can't connect to wired internet, because I have access only to wireless....
Let's begin, i read all of this:
https://wiki.archlinux.org/index.php/Ne … stallation
https://wiki.archlinux.org/index.php/Co … ng_network
https://wiki.archlinux.org/index.php/Wireless_Setup
My problems (can't access internet while installing arch):
Img 1
Img 2
Img 3
Img 4
Img 5
Img 6
I just don't know what to do...
Last edited by CauseLT (2012-10-30 22:13:16)

ewaller wrote:
I am not sure exactly what you are asking. I think you are asking as to whether you can install Arch alongside Ubuntu using the spare space on your drive. The answer is, yes. But, things can go wrong if there is pilot error.
From Ubuntu, please post the output of sudo fdisk -l /dev/sda and of mount.
As to your English -- it is far better than my Lithuanian. I regret that I have never mastered a second language; No need to apologize.
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009b88f
Device Boot Start End Blocks Id System
/dev/sda1 * 2046 849594367 424796161 5 Extended
/dev/sda4 849594368 1250260991 200333312 7 HPFS/NTFS/exFAT
/dev/sda5 2048 7999487 3998720 82 Linux swap / Solaris
/dev/sda6 8001536 203311103 97654784 83 Linux
/dev/sda7 203313152 849594367 323140608 83 Linux
mount:
/dev/sda6 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
/dev/sda7 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfsd-fuse on /run/user/cause/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=cause)
/dev/sda4 i will delete durning Arch installation, because I don't use that partition (old Windows D disk)..
Last edited by CauseLT (2012-10-29 00:17:43)

[SOLVED] Strange Hard Drive Errors - Read Only Filesystem?

Solution: Discard old laptop, buy new laptop
I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
Last edited by aphirst (2013-03-27 14:51:38)

Smartctl gives me the impression it's my Hard Drive:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
Not that this tells me how to fix it...
Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
Cheers.
Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...

[SOLVED] Root mounted as "Read-only filesystem". mkinitcpio issue?

I am currently in the middle of setting up system encryption with LUKS. I have been making good progress so far, but I do have one remaining issue.
After typing my LUKS password, the Linux kernel starts to complain that root is a read-only filesystem. "Starting NetworkManager... cannot touch file XYZ: Read-only filesystem". When it has finally finished booting, I am dropped into a TTY. I can log in and cat my files, but I cannot write to any files our use any programs that do (like pacman).
I wonder if this is an mkinitcpio issue, but I am not sure. For whatever it's worth, here's my basic setup:
* /dev/sda1: Boot
* /dev/sda2: Swap
* /dev/sda3: Root (LUKS/ext4)
* menu.lst looks like this
* /etc/fstab contains this line:
/dev/mapper/root / ext4 defaults 0 1
* /etc/mkinitcpio.conf contains these lines:
MODULES="ext4"
HOOKS="base udev pata scsi sata encrypt filesystems"
edit: I should note that I did reinstall the kernel after making those edits to mkinitcpio.conf.
Any idea what I'm doing wrong? As always, I really do appreciate the help. Thanks in advance!
Last edited by jalu (2011-04-16 22:14:20)

So it looks like this major problem was caused by a minor mistake. The file /etc/rc.sysinit was not executable. This made it impossible for the kernel to run the script, which in turn made it impossible for the kernel to mount /dev/sda2 (the swap partition) at /dev/mapper/swap. For some unknown reason, this in turn caused /dev/sda2 to be mounted at /, messing everything up.
Anyway, a simple sudo chmod +x /etc/rc.sysinit fixed the problem. Thanks for the help, MadTux!

[SOLVED] Appending Quiet forces Read-Only filesystem

After the update to initscripts I tried to append quiet to the kernel command line of GRUB and it simply causes my system to start-up as a read-only filesystem.
Last edited by horrormaster (2011-08-01 15:36:21)

title Arch Linux x64
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/gnu_linux ro rootflags=data=writeback,commit=90,orlov,barrier=0,async
initrd /boot/kernel26.img
If I add "quiet" before "rootflags" everything fails to load on boot (udev, mounting HDD rw, alsa, cupsd, etc.) and after all of those it simply states "Read-Only Filesystem". If I add "quiet" after "async" it fails to boot altogether due to an unrecognized option.
Last edited by horrormaster (2011-08-01 02:04:07)

Single User Mode : Read Only Filesystem

I can't edit files in single user mode as Root. When I try to edit them I get a msg saying "Read Only Filesystem".
I have tried chmod with no evial. I want to change my .profile as root so cls='clear'.
Any ideas?
Also when I try to login to my account in single user mode it says that account does not exist. However I'm in that accunt right now!
Thank You.

When you boot up into single user mode, there is a single recognized user -- root. That's why they call it single-user mode and not multi-user mode.
When you boot up into single user mode, the disk mounts as read-only. You have to make it writeable in order to do anything to it. I forget the actual command but it displays on the monitor nearby where it gives the "fsck" command syntax when you first boot into it. It's something like "mount -uw /" or something to that effect. It is saying to mount the root drive ("/") with user write privileges.
Then just "pico /Users/Mephux/.profile" (although I profess that I don't understand why you have to edit this file as root).
(if you find that this solves your problem, or is actually helpful towards arriving at a solution to your problem, please consider clicking on either the "helpful" or "solved" buttons above)

Pacstrap failed. Now I have a read-only filesystem that is unusable

Hello,
I have been using Linux for the past few years (primarily Ubuntu and Fedora), and have used the command line a lot.
I was just following the instructions on the Beginners guide. I set up wifi, and partitioned the disk using gdisk (all my computers since late 2009 have not used MBR). I then set up my mirrorlist (left the first one, and added my university as second).
When I ran pacstrap (without -i), it started downloading everything. I think it finished most of it. The kernel had been downloaded, and the filesystem supposedly set up. Then, I got an error. (I am not sure where it was, and I wasn't logging the output. There were many many lines of:
[timestamp] EXT4-fs (sda1): ext4_da_writepages: jpd2_start:8192 pages, ino xxxxxxx; err -30
Then:
[timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): Remounting filesystem read-only
error: command failed to execute correctly
error: could not create directory /mnt/var/lib/pacman/local/groff-1.21-2/: Read-only file system
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occured, no packages were upgraded.
warning: could not remove lock file /mnt/var/lib/pacman/db.lck
==> ERROR: Failed to install packages to new root
pacstrap /mnt base base-devel 35.27s user 6.19s system 3% cpu 17:34.81 total
Trying to rerun pacstrap gets me an error that the lockfile still exists. I cannot remove it because it is a "read-only filesystem". Its permissions are 000, and the folder it is in (pacman) has 755.
I also cannot make an fstab or continue with the installation.
I tried to run the setup again, and it kept failing. (MBR failed too, with the same error.)
What do you think caused it, and what could I do to resolve it. I couldn't find anything like that in the forums, or on google.
Last edited by masasin (2012-10-27 03:18:37)

Are the ext4 errors not a dead giveaway that the FS (or physical disk) are misbehaving? It's remounted itself read-only to prevent further damage.

Usb stick is "READ ONLY FILESYSTEM"

hello.
i have a problem with my USB-Stick. since i gave it to a friend it does no longer work. unix says it is a "READ-ONLY FILESYSTEM". anny sugestions how i could change that?
it was not possible to reformat it by disk utility. i also tried to format it on a windows machine - didn´t work... any ideas?
best reagards
sepoe

Monkeymeetsrobot's suggestion is the first thing I would have suggested myself -- your original post made no mention of no write-lock switch -- many flash drives have them -- one of mine does and when locked would exhibit that behavior and the other one that doesn't, it still works properly.
That said, now that we know that yours doesn't have a write-lock switch, maybe you could try this:
It's a long shot, but what happens when you launch Terminal and type
ls -ld /Volumes/{usbStickName}?
If the permissions are not drwxrwxrwx, then, perhaps, from an admin-privileged account, you could
sudo chmod 777 /Volumes/{usbStickName}
and with any luck, you will have write privileges again.
Something to try....no guarantees....
Short of that, you may be giving your friend a slightly used usb flash drive as a Christmas present.
(if this solves your problem, or is actually helpful towards arriving at a solution to your problem, please consider marking this reply as "helpful" or "solved," in addition to, if applicable, marking this question as "answered")

Read-only filesystem after reinstallation,chmod failure

I decided to switch to a pure systemd init yesterday. Despite strictly followed wiki my system failed to init with switch to systemd emergency mode with no way to cure the problem. So I followed with reinstallation of my system (32bit on 64bit HW as recently). I went thoroughly according installation wiki, installed and configured the base system and correctly umount-ed chrooted environment. I have reformated primary root and boot partitions with ext4 and ext2 respectively and extended /var partition with reiserfs. My home ext4 partition has left unchanged. Grub has been configured OK when being compared with my two Thinkapd Arch installations. My fstab is correctly set using UUID and explicit rw option. After rebooting from Install CD all seemed going well to login prompt and successfull root login. Next proceedings failed on unchangeble read-only filesystem permissions.
How can I chmod the partitions to make them writable and add users and use pacman? One fail with systemd is followed with another one with unchangable read-only permissions... Courious and very frustrating... Any help, please? Thanks, Petr

You'll need to post files, logs etc. if you want help - according to you, everything is correct .
For example, grub.cfg, fdisk -l or gdisk -l /dev/sdX, fstab...

Reset lost root password and now have read only filesystem

Hello,
I have recently had to reset a locked root password by booting from cdrom, mounting the first boot disk, editing the shadow file to remove root's password and rebooting the system.
The system has booted OK but, I now have a read only filesystem - everything in / cannot be edited, passwd doesnt work etc.
df -k shows the root (/) filesystem has been mounted on the physical disk I edited:
Filesystem kbytes used avail capacity Mounted on
/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a 10085836 185862 9799116 2% /
but in the vfstab it still references the disksuite metadevice:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
So, can I simply boot from CDROM again, amend the vfstab to be /dev/dsk/c0t0d0s0 (instead of /dev/md/dsk/d03) and reboot?
Any help with this is appreciated!
Thanks,
Emma

df -k should have shown root mounted on md0
e.g. on my machine
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 8260691 4366317 3811768 54% /
what does /etc/system show for rootdev?
# grep rootdev /etc/system
* rootdev: Set the root device. This should be a fully
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk
Remember if this is a mirrored drive, when you boot from CD you may need to mount both sides of the mirror and make changes on both sides- otherwise the replication may not goes as expected.
Actually, I have run into problems with the modifying one side of a mirror this way. In the past Sun tech support would recommend that I break the mirror and then rebuild it once the system is up and running. So in your case you may want to boot from CD, mount the 1st disk slice, edit /etc/vfstab AND /etc/system, boot into the OS and use the various meta commands to delete and rebuild the mirror- or at least maybe to drop and reattach the 2nd 1/2 of the mirror.

Read only filesystem when editing files

I just installed installed arch linux and when i try to edit and save a config file it says something like, "can't save file: read only filesystem". How do I change that?

Ok, I think I know what the problem is now, / is not in /etc/fstab. The new question is, how do i get it there w/o reinstalling everything?

Trying to modify PDF w/ no security, says it's opened as "read only to prevent modification"

what am I missing here?
The PDF in question can be found here:
http://wndw.net/
The PDF has a Creative Commons license saying I can:
"Copy, distribute and display the book. Make derivative works, including books and articles. Make commercial use of the book"
When I download and open the PDF, it is listed as having no security, but there's a blue info bar along the top in Acrobat X saying "The file you have opened complies with the PDF/A standard and has been opened read-only to prevent modification."
I actually just trying to remove any hyperlinks and color information on some of the pages so we can reduce our printing costs.
any ideas on how to open this NOT in read-only mode?

You can temporarily disable PDF/A mode in Acrobat and/or remove the PDF/A information: http://blogs.adobe.com/acrolaw/2011/05/how-to-remove-pdfa-information-from-a-file/

[SOLVED]pacman -Sf zim makes arch read-only filesystem

Hi,
Last night I was trying to install zim, it looks like there were a couple packages which weren't properly installed before. I googled the error I received and found somewhere on the forum the tip to use
pacman -Sf package
I ran the command and it installed some sort of new kernel, fstab, something with python, and zim of course. While it was installing the packages I noticed it moved a couple files around and I'm not quite sure what it all did. anyway when I booted arch this morning it didn't quite make it to gdm, so I quickly booted into ubuntu, mounted my arch partition changed the inittab to boot to init 3. I then noticed that it mounted the arch / as read-only, I looked around a bit seems like my /etc/fstab was moved to /etc/fstab.pacorig. Now before I start playing around and maybe break things more than they are, anyone have a tip about how to figure out everything that was changed?
I also noticed that I could login as root without having to use a password which I don't like at all, which is a little scary.
Last edited by whitethorn (2010-06-26 13:50:11)

First things first; using the -f/--force flag with pacman is the absolute last resort, when everything else fails, and when you know exactly what you're doing. Using it just because you found a tip on the forum, and clearly without thinking about the potential consequences, is just asking for trouble - and you've got it.
To fix: your pacman log will tall you what packages were installed, and also has a record of any install-time messages. Comb through that, and work out how to revert the major issues.
[edit] overlap with loafer - he was faster because he used fewer words.

[SOLVED] More rsync problems after restore... Read only filesystem?

Yesterday I backed up all of my data with rsync to a USB thumb drive. Surprisingly it all fit, but my intentions were to wipe my disk and create a new partition scheme for a dualboot while still being able to continue where I left off with arch. So after backing up with the script from the arch wiki titled full system restore with rsync, I followed the rest of that page, and modified the fstab on the backup on the USB and reconfigured grub and restarted my computer and I was able to boot into the USB. Then, I decided that it would be easier to just use the live cd to repartition and pacstrap the base system and generated an fstab. Next, I chrooted from the livecd environment into the newly built base and installed rsync. I then mounted my USB to /mnt in the chrooted environment and used
rsync -aAXv /mnt/ARCH_BACKUP/* / --exclude={/mnt/ARCH_BACKUP/etc/fstab,/mnt/ARCH_BACKUP/boot/grub/}
I just did this since I figured that all of the directories excluded in the script wouldn't really have to be excluded here since they were already empty. Everything seemed to run smoothly except for one file(or maybe directory?) called /etc/resolv.conf.t.jbnW2 which kept giving an error. I figured the file was unique to the USB or something and continued to reinstall grub and then reboot. The weird thing is that everything was back on my system, but it didn't automatically boot into a display manager which it's set up to do. Then when trying to manually start x, that wouldn't work. Then I tried to connect to wifi, it recognized my network but wouldn't connect, so I tried sudo su, which worked but returned an error that the var file system was read only. I then tried to use rsync again thinking maybe that directory would transfer now that I wasn't in the chrooted environment. But instead, it was trying to restore every single file, but every one returned the error "filesystem is read only".
It seems like when I restored all of the files in my entire system were made read only.
Can anyone tell me what may have caused this and how to fix it?
I think it may either be that when I mounted the device in the chrooted environment I didn't specify 'rw' capabilities, or it may be that when I backed up I didn't specify 'rw' capabilities I just opened the file manager and clicked on it and it automagically mounted to /media/.
Last edited by eroge008 (2013-01-25 20:29:22)

Ok, well I fiixed it. I had edited the fstab on the usb to be able to boot into the usb, and, while I edited it again on the hdd each time I restored from the backup, I didn't realize that the top entry /dev/sda1 (which is my root partition) was on a line that was commented out. I guess I accidentally hit the backspace button or something while editing it to be able to boot into the usb.
Also, I think there was a second problem, that my usb controller is starting to fail. Because on the last time that I backed up, if I moved my computer or anything I would get a I/O error. This was caused by the failing usb controller. The computer would remount it as read-only because of the failure. The solution to this was to use
hdparm -r0 /dev/sdxy
Note: The device must be unmounted.
Where x is the device and y is the partition number, for me this was sdb1.
Then mount specifying read-write option.
mount -o rw /dev/sdxy /media/<BACKUP>
I also tried
mount -o remount,rw /dev/sdxy /media/<BACKUP>
as was recommended on all of the sites that I could find, but this command kept returning an error.
Note: For newer users, Arch does not automatically create the media folder as it doesn't provide automatic mounting of external drives. If such is the case, and you haven't installed a desktop environment with a file manager that will automatically do this for you when the device is recognized, you must make the media directory and the directory which you intend to mount to manually.
# mkdir /media
# mkdir /media/<BACKUP>
Where <BACKUP> can be whatever you want it to be.
Last edited by eroge008 (2013-01-25 20:27:52)

[Solved]please help with btrfs read only filesystem

Yesterday I deleted a snapshot using the command
sudo btrfs subvolume delete /snapshot-2014-**-**
in which the snapshot-... is a snapshot I created eariler. But a few hours later I suddenly found that the file system became read-only. I reboot and the message stuck at mounting /dev/sda1 and failed, into an emergency shell, saying something like "no subvolume is find". I tried to mount /dev/sda1 using a rescue usb stick but still failed...
I have been using the same command to create and delete snapshots for several months without problem, but this time... I don't know what was I doing wrong, maybe I mistyped something this time?
So... How could I recovery the filesystem? I've searched for a bit but cannot find any satisfied result.
EDIT: I re-installed the system.
Last edited by Frefreak (2014-09-27 10:39:45)

LoBo3268715 wrote:Just gonna take a stab at what you want to do here but I assume you want to switch to the ATI card correct? using open source drivers? Google around for vgaswitcharoo. It can be a royal PITA but I got it working with my intel integrated card and ATI mobility 5650. Also there is a package in the AUR for this. https://aur.archlinux.org/packages.php?ID=51704
Yes, that's exactly what I'm trying to achieve. Thanks for the advice, I will explore all the possibilities with vga_switcheroo

[SOLVED] read only filesystem prevents login

Similar Messages

Maybe you are looking for