Reference10:Event/0x0018009b: Difference between revisions
Jump to navigation
Jump to search
(New page: The Alarm "Read-only partition" is generated on the Linux Application Platform if the partition is mounted read-only.<br> <br> Normally this happens, when the kernel recognizes issues with...) |
No edit summary |
||
Line 1: | Line 1: | ||
The Alarm "Read-only partition" is generated on the Linux Application Platform if the partition is mounted read-only.<br> | The Alarm "Read-only partition" is generated on the Linux Application Platform if the partition is mounted read-only.<br> | ||
<br> | <br> | ||
Normally this happens, when the kernel recognizes issues with the hard disk and | Normally this happens, when the kernel recognizes issues with the hard disk and therefore mounts the partition read-only.<br> | ||
You may recover from this situation, but there is always the possibility, that your hard drive/CF card is defect! | You may recover from this situation, but there is always the possibility, that your hard drive/CF card is defect! |
Latest revision as of 14:59, 4 September 2015
The Alarm "Read-only partition" is generated on the Linux Application Platform if the partition is mounted read-only.
Normally this happens, when the kernel recognizes issues with the hard disk and therefore mounts the partition read-only.
You may recover from this situation, but there is always the possibility, that your hard drive/CF card is defect!
LAP on a gateway
- configure root=/dev/sda2 as Kernel command line under Linux->General and restart the LAP.
- login with Putty
- perform a disk check: e2fsck /dev/sda4
- configure root=/dev/sda4 as Kernel command line under Linux->General and restart the LAP.
- see if the webserver starts and everything runs again
- make a backup of all your configurations and databases! If a database has been corrupted, the backup will fail!
LAP inside a VM
- reboot your VM and select the Rescue Debian GNU... entry from the boot loader
- login with Putty
- perform a disk check: e2fsck /dev/sda3
- reboot the VM
- see if the webserver starts and everything runs again
- make a backup of all your configurations and databases! If a database has been corrupted, the backup will fail!