Root filesystem corrupted, only var left

Hi fellow Arch users!
I was wondering if anybody would have an idea if it would be possible to restore packages and rebuild the system having only var partition.
In short - I have had an encrypted system with var and home stored on separate hard drives. Unfortunately hard drive that was storing root of the system got broken and I lost everything apart var and home.
I would be grateful for your thoughts,
Greg
Last edited by Gregosky (2014-10-14 19:18:14)

I came back from holiday and started working on restoring my Arch from var. Here is what I have done: I have formatted my new SSD hard drive, mounted it as /mnt, created /mnt/var and /mnt/boot, then I have mounted my var and boot partitions. Once mounted I have executed following:
pacman -r /mnt -Syu
. All packages were rebuilt and filesystem structure was restored however at the moment I'm unable to chroot to /mnt.

Similar Messages

Remounting Root Filesystem Read-only, what for?

Hi.
I have question. What really for while rebooting/halting system root filesystem is remounted? One second before all filesystems are unmounted. Why it has to be mounted when shutting off the computer.
Thanks in advance.

alexpnx wrote:I have a question on a similar topic... How unsafe is it if the system is rebooted or shutdown without unmounting samba shares? Can the shares be corrupted?
I think the file(s) you're writing to during shutdown can be corrupted (not all corrupted, but simply unfinished saved), if you write there at all, but not anything else as the partition is still up on the host and the host takes care of metadata and stuff - it's worse with local partitions where metadata and stuff can be saved uncompletely, which can lead to files disappearing all over the filesystem, some old files showing up again etc.
Can someone else confirm this?

[Solved]Root filesystem read-only at boot

Hi,
I can't boot arch. Root filesystem is mounted ro, so nothing works properly. Last boot I make a pacman -Syu without incidences. A few weeks ago I make manual intervention (filesystem upgrade - manual intervention required from latest news). I think that last new (Users of unofficial kernels must enable devtmpfs support) is not the problem since I don't complile the kernel.
dmesg show 2 mount operations to /dev/sda3 (my root partition, EXT4 fs).
mtab have 2 entrys with /sda3. The last shown "ro" flag, and some strange parameters for me .
Maybe is a disk problem? How can I remove this flag, or remount in rw mode?
umount -f don't work.
I use a dual boot with GRUB, and second system is W7.
Thanks in advanced.
Last edited by HermesT (2012-01-14 19:05:56)

Some extra info:
from dmesg
[ 1.237581] sda: sda1 sda2 sda3 sda4 < sda5 >
[ 1.829594] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 5.722599] EXT4-fs (sda3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered.
mtab
rootfs / rootfs rw 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
/sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=215507,mode=755 0 0
/run /run tmpfs rw,nosuid,nodev,relatime,size=10240k,mode=755 0 0
/dev/sda3 / ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
/dev/sda1 /media/SYSTEM fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sda2 /media/COMPAQ fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sda5 /media/Almacen fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
* please, note that rootfs (?) is the same partition as /dev/sda3, like can be seen in df output.
df
S.ficheros 1K-bloques Usado Disponible Uso% Montado en
rootfs 21096088 12132788 7891664 61% /
udev 10240 0 10240 0% /dev
/run 10240 252 9988 3% /run
/dev/sda3 21096088 12132788 7891664 61% /
shm 1550516 0 1550516 0% /dev/shm
/dev/sda1 102396 25744 76652 26% /media/SYSTEM
/dev/sda2 54772576 36097780 18674796 66% /media/COMPAQ
/dev/sda5 548819964 142760132 406059832 27% /media/Almacen

XFS Root Filesystem on LVM Stripe - Corruption

I want to create a LVM Stripe across two SATA drives. The problem I keep running into is, on boot, arch reports that a fsck needs to be run on the root filesystem, so it mounts it read only and allows me to type in the root password to get shell access. This all happens after I do the initial arch install, reboot, log in normally, do a pacman -Syu, reboot.
Here's what I have and what I did...
I have two 320G SATA Drives plugged into my system board (an ABIT AN-M2HD). My Bios is set to "AHCI Linux" for the SATA mode.
Boot the latest Arch CD install at command prompt:
cfdisk /dev/sda
create 125M Partition (for /boot) /dev/sda1
create 319G Partition /dev/sda2
cfdisk /dev/sdb
create 320G Partition /dev/sdb1
lvm pvcreate /dev/sda2 /dev/sdb1
lvm vgcreate lvmgrp0 /dev/sda2 /dev/sdb1
lvm lvcreate -i2 -I4 -L1G -nswap lvmgrp0
lvm lvcreate -i2 -I4 -L594G -nroot lvmgrp0
/arch/setup (I'm going to abbreviate this)
Hard Drive Setup (chose option 3)
Set swap to swap LV
Set root to root LV (xfs)
Set /dev/sda1 to /boot (ext3)
/etc/rc.conf USE LVM="YES"
Kerel Params = Boot from LVM Support? I answer Yes
Grub Looks Good.
Everything seemingly installs fine, I can reboot and arch comes right up. But after I do pacman -Syu everything goes to pot.
I suspect I have something wrong in alignment between the LVM stripe and XFS, but dont know..
alternately, should I set my LVM Stripe Size to a value larger than 4? I thought since on i686 max XFS block size is 4096 (4K) then they should match. Any thoughts on this?
help! ;-)
Ether..

I just wanted to add an update. It wasn't a LVM issue, it was a XFS issue.
I went to Arch 64 bit for a while and everything (above) worked just fine.. The usability and Lib32 issues with 64 bit lost it's luster and last weekend I went back to 32 bit Arch.
In going back to 32 bit I followed my procedure above for partitioning just as I had with the 64 bit version and after rebooting from the install and updating packman, the same thing occurred, the file system would start to corrupt, pacman would complain that libraries were truncated and so forth. After reboot, the /root partition would not mount read/write because it was not clean...
I reinstalled Arch 32 bit 6 times on Saturday trying various things in a scientific way and came to this conclusion:
__and I have no idea why__, but when I use the XFS file system on an install with Arch 32 bit, it hoses up. "Your Crazy" you might say, but trust me I've tried it different ways more than a dozen times. (I'm no n00b either, I've been an RHCE since 2003 and a daily Linux user since 1999.) Seems crazy, but XFS was a constant in all of my testing. The only thing I can figure is that it's my hardware and that's just a guess. 64 bit worked without a hitch with XFS. I even got desperate and installed / on a lone 60 gig partition (/dev/sda1) completely deleting all LVMs and it still corrupted with XFS and 32 bit
The Solution?
I used JFS. I have created the LVM Stripe as I have described above and it works great. No issues.
Weird..
For the sake of knowledge I have a:
AMD 5000+ Black Edition CPU
Abit AN-M2HD Motherboard
2 Gig Dual Channel RAM (2x1Gb)
2 320 Gig SATA Drive
1 SATA DVD Writer
-Ether..
Last edited by EtherNut (2008-01-29 14:54:01)

Kinit mounts root filesystem as read only [HELP][solved]

hello
I've being messing around with my mkinitcpio trying to optimize my boot speed, i removed some of the hooks at the beginning i couldn't boot, but then now i can boot but the root filesystem mounts as read only, i tried everything my fstab looks fine, / exists with defaults i tried to mount it referencing by it's uuid or by it's name and i get the same results, it mounts the filesystem as root only all the time no mather what i do.
There is not logs since i started playing with mkinitcpio, or anything i searched everywhere in this forum and around the internet, and i can't find any solution that would work, i restored all the hooks and modules on mkinitcpio and the result it's still the same. i also changed the menu.lst in grub to vga=773 but that's about it.
Can anyone help with this please i can't seem to boot properly.
Regards
Last edited by ricardoduarte (2008-09-14 16:16:25)

Hello
Basically what happens it's that it loads all the uDev events then the loopback, it mounts the root read only, then when it checks filesystems it says
/dev/sda4: clean, 205184/481440 files, 1139604/1920356 blocks [fail]
************FILESYSTEM CHECK FAILED****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write: mount -n -o remount,rw / *
* When you exit the maintenance shell the will *
* reboot automatically. *
Now what bugs me its that i can do that mount -n -o remount,rw / with no problems and when i do
e2fsck -f /dev/sda4
it doesn't return any errors just says that 0.9 non continuous.
none of this makes sense to me!! thats why i though that the problem could be coming from mkinitcpio or something
any ideas
Thanks for your help, btw thanks for the quick reply
Regards
Last edited by ricardoduarte (2008-09-14 15:48:49)

[SOLVED] df -h does not reflect true root filesystem size

Why does df -h show root filesystem as being only 20G?
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/cryptroot 20G 15G 4.6G 76% /
dev 7.7G 0 7.7G 0% /dev
run 7.7G 668K 7.7G 1% /run
tmpfs 7.7G 70M 7.7G 1% /dev/shm
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
tmpfs 7.7G 224K 7.7G 1% /tmp
/dev/sda1 239M 40M 183M 18% /boot
tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000
That is what my df -h output looks like. My setup is full disk encryption using dm-crypt with LUKS, per the guide on arch wiki. I basically created one /boot partition and left the rest of the disk to be an encrypted partition for the root filesystem. So why is my system complaining about (and acting as if it's running out of space)? Have I forgotten something?
Thank you for reading this. Let me know if you need any more logs or info on my setup - I realise I haven't provided very much info here, but I can't think of what to provide.
Last edited by domentoi (2014-12-24 19:02:32)

This is lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 250M 0 part /boot
└─sda2 8:2 0 465.5G 0 part
└─cryptroot 254:0 0 465.5G 0 crypt /
sdb 8:16 0 14.9G 0 disk
└─sdb1 8:17 0 14.9G 0 part
and fdisk -l
Disk /dev/sdb: 14.9 GiB, 16013942784 bytes, 31277232 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
Disklabel type: dos
Disk identifier: 0x5da5572f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 31275007 31272960 14.9G 73 unknown
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa5018820
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 514047 512000 250M 83 Linux
/dev/sda2 514048 976773167 976259120 465.5G 83 Linux
Disk /dev/mapper/cryptroot: 465.5 GiB, 499842572288 bytes, 976255024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 1.4 TiB, 1500301908480 bytes, 2930277165 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
Disklabel type: dos
Disk identifier: 0x445e51a8
And graysky: I thought I made the partition for /boot 250 MB and the encrypted partition 465.5 GB but I'm now quite sure I did something wrong...
Thank you all

CentOS based linux VM running on Hyper-v : Checking root filesystem fails when kernel switches having old PV(para virtualised driver based on 2.6.32 linux kernel) to new PV(which is equivalent to linux integration component 3.4)

hi all,
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support
Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i
am hitting following filesystem check error messages :
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
The superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2
filesystem(and not swap or ufs or something else),then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda2
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** When you leave the shell.
Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :
(Repair filesytem) 1 # mount
/dev/hda2 on / type ext3 (rw)
proc on /proc type proc (rw)
(Repair filesystem) 1# cat /etc/mtab
/dev/hda2 /ext3 rw 0 0
proc /proc proc rw 0 0
(Repair filesystem) 1# df
Filesystem 1K-blocks used Available Use% Mountedon
/dev/hda2 4%
I think for all above command there should be /dev/sda2 instead of /dev/hda2.
Also my fstab , and fdisk -l looks like ok for me.
(Repair filesystem) 1# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=swap-xvda3 swap swap defults 0 0
(Repair filesystem) 1# fdisk -l
Device Boot Start End Block Id System
/dev/sda1 * 1 49 98535 83 Linux
Partition 1 does not end with cylinder boundary.
/dev/sda2 49 19197 39062500 83 Linux
Partition 2 does not end with cylinder boundary.
/dev/sda3 ......
Partition 3 does not ......
/dev/sda4 ......
Partition 4 does not end ....
(Repair filesystem) 1# e2label /dev/sda1
/boot
(Repair filesystem) 1# e2label /dev/sda2
(Repair fielsystem) 1# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
(Repair filesyatem) 1# ls /dev/hd*
ls: /dev/hd*: No such file or directory
Kindly suggest any configuration of windows server or kernel configs missing or how to resolve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal

i am not able to understand duplicate UUID and from where it is picking /dev/hda* ?
~
VVM:>>
VVM:>> Output of dmesg | grep ata contain substring "Hyper-V" ?
VVM:>>
it doesn't contain "Hyper-V" or ata related message and the output doesn't change with boot parameter reserve=0x1f0, 0x8
~~
~~~~
==
output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8)
==
see later ( in "good situation" example )
~~
===
Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst:
reserve=0x1f0, 0x8
. (This option reserves this I/O region and prevents ata_piix from loading).
==
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8) :
~~
[ 0.176027]
libata version 3.00 loaded.
[ 0.713319]
ata_piix 0000:00:07.1: version 2.13
[ 0.713397]
ata_piix 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713404]
ata_piix: probe of 0000:00:07.1 failed with error -22
[ 0.713474]
pata_acpi 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713479]
pata_acpi: probe of 0000:00:07.1 failed with error -22
~~
As result: 1) IDE disk handled by hv_storvsc , but 2) no CD-ROM device
==
~ # blkid
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
==
~~
VVM>>
VVM>>Q1: Output of blkid contain duplicate UUID ?
VVM>>
-> blkid contains duplicate UUID, below are the output.
~~
This situation is classic problem "
use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the DVD-ROM / CD-ROM device handling)
~~
For compare, see example "good situation":
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( without boot parameter reserve=0x1f0, 0x8) :
~~~~
~ # dmesg |grep ata
[ 0.167224] libata version 3.00 loaded.
[ 0.703109] ata_piix 0000:00:07.1: version 2.13
[ 0.703267] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
[ 0.703339] ata_piix 0000:00:07.1: setting latency timer to 64
[ 0.704968] scsi0 : ata_piix
[ 0.705713] scsi1 : ata_piix
[ 0.706191] atal: PATA max UDMA/33 cmd 0xlf0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.706194] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.868844] atal.00: host indicates ignore ATA devices, ignored
[ 0.869142] ata2.00: ATAPI: Virtual CD, , max MWDMA2
[ 0.871736] ata2.00: configured for MWDMA2
~~~~
===
~ # uname -a
Linux ubuntu 3.7.0-7-generic #15-Ubuntu SUP Sat Dec 15 14:13:08 UTC 2012 x86_64 GNU/Linux
~ # lsmod
hv_netvsc 22769 0
hv_storvsc 17496 3
hv_utils 13569 0
hv_vmbus 34432 3 hv_netvsc,hv_storvsc,hv_utils
~ # blkid
/dev/sr0: LABEL=”CDROM" TYPE="iso9660”
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
===
( only CD-ROM and 1( one) IDE disk connected to ATA)
~~
regarding ata_piix.c patch . . .
As far as i understand this patch , it ignore ATA devices on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~~
Yes:
ignore ATA-HDD ( but not ignore ATA CD-ROM ) on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~
this patches need be backported:
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
~
~~
P.S.
Are You do this:
==
As temporary solution, increase on 1-2 Gb size all .vhd connected to IDE bus
( but not increase size of partitions inside disks)
==
? fsck write message a-la: "no error in file system" ?
2013-01-24 Answer by Ujjwal Kumar: As a temporary solution looks ok for me, but [ VVM: need true solution ]
P.P.S.
To Ujjwal Kumar :
My e-mail:
ZZZZZZZZZZZZZZZ
please send e-mail to me, in reply I send to You patches to ata_piix ( and *.c before and after patches) , etc.
} on 2013-01-14 -- DoNe

Filesystem Corruption?

Hi, Folks,
While this is indeed conjecture, it appears that the 2.0 series of firmware has a filesystem corruption problem as the amount of content on the device increases - in particular, once many applications have been installed. The behavior that I've witnessed in this circumstance is somewhat progressive. Initially, application install or updates begin to slow down dramatically. User behavior starts to contribute to the problem: when an update might takes more than five minute, folks may try aborting the update or sync, which often leads to a corrupted filesystem. This is easy to identify; powering down then back up again will lead to an "Apple logo" hang. Only a DFU restore will recover from this failure.
Much more significant is that even in the absence of inappropriate user behavior, the filesystem issue continues to worsen over time. For techies, the symptoms appear quite similar to serious fragmentation (or analogously for in-memory issues, garbage collection). I'm beginning to think that the core Flash filesystem code has a bug which starts to yield incorrect FS handling once many files are present. A key symptom is that attempts to restore from a backup will often report that the backup file is corrupted. My best guess is that the backup itself was probably performed properly, but the reported corruption actually may have been caused by the iPhone's filesystem itself becoming corrupted prior to the backup.
After having run into this issue often enough that I've needed to perform ~10 DFU restores on three iPhones (one original 8GB, and two 3G 16GB devices), this indeed appears to be a serious problem. Though my guess is that the iPhone's filesystem code is the root cause, I'm interested in hearing feedback from other folks who may have encountered this issue. Are the problems which you've seen consistent with this hypothesis?
Cheers!
Mark

Hello!
I'll add one more interesting data point. I've since found that I have had two different backup files that take well over an hour to restore onto a newly DFU-restored phone. On both of these files, the backup would proceed fairly quickly to a specific point (~50% on one file, and about 75% on the other file), and then would stop (the progress bar kept spinning, but with no forward progress) for about 1 hour, and then would continue and ultimately succeed. It's intriguing that repeating this process with each of these files yielded exactly the same "pause point".
While the thought of a timeout occurring is still quite appropriate, this further suggests that if the core filesystem code is at fault, the error might be induced by a NAND/iNAND error condition (NAND Flash always has errors, by design; Flash filesystems are supposed to handle those errors gracefully). This deterministic very-long-delay condition suggests that (normal) Flash errors just might be confusing the filesystem driver.
FYI!
Mark

My Macintosh HD is full 979GB only 300MB left.

My Macintosh HD is full 979GB with only 300MB left but there is only 100GB of files stored on the Mac, can't find anything that is filling the disc.

Your boot volume is full. First, reboot. That will free up some space. Typically you need at least about 10 GB free for proper operation. More than that to allow for growth of your data.
Use a tool such as OmniDiskSweeper to explore your volume and find out what's taking up the space.
Proceed further only if the problem hasn't been solved.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To really see everything, you have to run it as root.
First, back up all data if you haven't already done so. No matter what happens, you should be able to restore your system to the state it was in at the time of that backup.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Terminal in the page that opens.
After installing ODS in the Applications folder, drag or copy — do not type — the following line into the Terminal window, then press return:
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
I don't recommend that you make a habit of this. Don't delete anything while running ODS as root. When you're done with it, quit it and also quit Terminal.

Filesystem read only after kernel compilation

Hello,
I builded my own kernel so I shouldn't need an initrd. After a lot trial and error I finally have a booting kernel. Funny thing is, that my root filesystem is read only.
When I boot from the standard arch kernel, everything is fine.
I thought it was because I have data=writeback in my fstab, but it isn't.
Does somebody have an idea? My filesystem is ext4.
the only error message that is usefull, I think is something about /etc/sysinitrc line 301 /etc/mtab: mount read only.
regards,
Roel

it's odd, but i think it needs the initrd to mount the root properly. in my case, without an initrd, the root being ext4, is mounted ext3.

Filesystem read only at boot "SOLVED"

Hi archers
I have a frustrating problem.... for some unknown reason... I rebooted today, and havn't been able
to get back into arch....
it complains that my filesystem is read only etc. heres the error
******************* FILESYSTEM CHECK FAILED *************
* Please repair manually and reboot. Note that the root *
* filesystem is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the mantenance shel the system will *
* reboot automatically.
i've tried what it suggests "mount -n -o remount,rw /
i reboot, and still get the same problem over and over again.
I don't know what could of caused this.... i havn't been messing with anything unusual....
I better output my fstab and partitions:
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0007f78b
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 46 265072+ 82 Linux swap / Solaris
/dev/sda3 47 1003 7687102+ 83 Linux
/dev/sda4 1004 19457 148231755 83 Linux
Fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 0 1
/dev/sda4 /home ext4 defaults 0 1
Pleaasseeee Help
I'm using a live cd to access the internet right now
thanx in advance
any ideas?
thankyou
Last edited by kaddy (2009-10-18 13:38:16)

Few days, or maybe a week ago, when i was trying to get X to work, i always had to use the computer's reset button because the keyboard would be irresponsive. Normally Arch would fix itself and re-reboot, but eventually it broke because of whatever reason. I thought of wiping the partition and reinstalling Arch from scratch as i didn't have many things on it anyway, but guess what, GParted could fix the filesystem.
(By the way, in case you're curious, the reason X wasn't working properly was that i had no keyboard or mouse drivers installed.)
If you have another Linux on your PC, or a Live CD, or even an installation CD, see if it has a disk-partitioning tool that has an option to fix filesystems. If it doesn't, but if the Linux you use is installed on your PC, just install GParted. But if you're using an installation- or Live CD, you can't do that, and in that case i think you'll have to get another Linux; i would say download Puppy Linux and make a Live CD of that; it has GParted and is friendly for newcomers in every other way too. And you can be sure that having a Live CD lying around is always something good. You never know when something like this will happen again.
(Oh, i just realized that you already ARE using a Live CD... Keep installation CDs, and Puppy Linux, in mind though.)
Last edited by TaylanUB (2009-10-18 13:36:48)

Increase root filesystem size with VxVM

Hi All,
Can i increase the root fileystem size in solaris 10 after encapsulating the root disk into VxVM.
Thanks
---MGP---

I wouldn't try it.
If you have a mirror, I'd drop the mirror, copy everything over to the mirror disk (in normal, contiguous slices), then redo the VxVM encapsulation.
Root filesystem cannot be discontiguous, no concats, stripes, raid5s, only mirror. So growing is difficult unless the space is already past the end.
Easier to copy to another disk, reset the bits (/etc/system, /etc/vfstab), then boot from it.
Darren

[SOLVED]root partition read only after update systemd

After update systemd today, the systemd-remount-fs.service fail to start. Root filesystem is read only I tried add rw to fstab mount option, but the root parition is still read only. I noticed that util-linux package are installed and udev package is dropped , Does it related to my problem?
Please advice me.
Sorry for my bad English.
Update
After downgard util-linux package, the system work again
Update 2
UUID in grub.conf and fstab are inconsistent, Thanks to tomegun for point out this problem.
Last edited by aduser (2012-06-08 04:05:59)

output of systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sun, 03 Jun 2012 01:17:42 +0800; 5min ago
Process: 132 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
fstab
UUID=55326b3a-eec9-498e-8e20-0a7ddd8daf9a / btrfs rw,compress=lzo,space_cache,autodefrag 0 1
UUID=54c17991-716b-496e-a89b-4e978f2d92a4 /boot ext2 defaults 0 1
systemctl
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devi...d-card1.device loaded active plugged RV630 audio device [Radeon HD 2600 Series]
sys-devi...d-card0.device loaded active plugged 82801I (ICH9 Family) HD Audio Controller
sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
sys-devi...dd-sdd1.device loaded active plugged ST3120213A
sys-devi...dd-sdd2.device loaded active plugged ST3120213A
sys-devi...ock-sdd.device loaded active plugged ST3120213A
sys-devi...da-sda1.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda2.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda3.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda5.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...ock-sda.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...db-sdb1.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb2.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb3.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb4.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb5.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...ock-sdb.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...dc-sdc1.device loaded active plugged ST980811AS
sys-devi...dc-sdc2.device loaded active plugged ST980811AS
sys-devi...ock-sdc.device loaded active plugged ST980811AS
sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-devi...y-ttyS0.device loaded active plugged /sys/devices/pnp0/00:07/tty/ttyS0
-.mount loaded active mounted /
boot.mount loaded active mounted /boot
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted /tmp
xs-big.mount loaded active mounted /xs/big
xs-dev-\...pace\x5d.mount loaded active mounted /xs/dev/[workspace]
xs-dev.mount loaded active mounted /xs/dev
xs-dl.mount loaded active mounted /xs/dl
xs-file.mount loaded active mounted /xs/file
systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
console-...daemon.service loaded active running Console Manager
console-...-start.service loaded failed failed Console System Startup Logging
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running dhcpcd on eth0
gdm.service loaded active running Gnome Display Manager
[email protected] loaded active running Getty on tty1
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-...unt-fs.service loaded failed failed Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...rigger.service loaded active exited udev Coldplug all Devices
systemd-udev.service loaded active running udev Kernel Device Manager
systemd-...nlevel.service loaded failed failed Update UTMP about System Runlevel Changes
systemd-...ssions.service loaded active exited Permit User Sessions
systemd-...-setup.service loaded active exited Setup Virtual Console
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...control.socket loaded active listening udev Control Socket
systemd-...-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
74 units listed. Pass --all to see inactive units, too.
grub2 conf
menuentry 'Broken' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-ck kernel-true-852c733e-be0d-4375-8668-d7ae049295a9' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 54c17991-716b-496e-a89b-4e978f2d92a4
else
search --no-floppy --fs-uuid --set=root 54c17991-716b-496e-a89b-4e978f2d92a4
fi
echo 'Loading Linux ck kernel ...'
linux /vmlinuz-linux-ck root=UUID=852c733e-be0d-4375-8668-d7ae049295a9 ro rootflags=subvol=broken quiet add_efi_memmap elevator=bfq
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-ck.img
The update packages
core/btrfs-progs 0.19.20120328-2 2 -> 3
core/device-mapper 2.02.95-4 4 -> 6
core/cryptsetup 1.4.2-1 1 -> 2
core/gpm 1.20.6-7 7 -> 8
core/lvm2 2.02.95-4 4 -> 6
extra/libglapi 8.0.3-1 1 -> 2
extra/libgl 8.0.3-1 1 -> 2
extra/ati-dri 8.0.3-1 1 -> 2
extra/bluez 4.99-2 2 -> 6
extra/consolekit 0.4.6-3 3 -> 4
extra/gvfs 1.12.3-1 1 -> 2
extra/gvfs-obexftp 1.12.3-1 1 -> 2
extra/libatasmart 0.18-1 1 -> 2
extra/libcanberra 0.28-4 4 -> 5
extra/libpulse 2.0-1 1 -> 2
extra/libcanberra-pulse 0.28-4 4 -> 5
extra/mesa 8.0.3-1 1 -> 2
extra/pulseaudio 2.0-1 1 -> 2
extra/xf86-video-ati 6.14.99-0.20120517 0.20120517 -> 1.20120517
community/libvirt 0.9.12-7 7 -> 8
community/ttf-ubuntu-font-family 0.80-2 2 -> 3
multilib/lib32-libglapi 8.0.3-3 3 -> 3.1
multilib/lib32-libgl 8.0.3-3 3 -> 3.1
==> Software upgrade (new version) :
core/util-linux 2.21.1-2 -> 2.21.2-1
core/e2fsprogs 1.42.2-2 -> 1.42.3-1
core/libpipeline 1.2.0-2 -> 1.2.1-1
core/libsystemd 44-7 -> 184-2
core/procps-ng 3.3.2-2 -> 3.3.3-1
core/systemd 44-7 -> 184-2
core/systemd-sysvcompat 3-1 -> 184-2
extra/pixman 0.24.4-1 -> 0.26.0-1
extra/xorg-server-common 1.12.1.902-1 -> 1.12.2-1
extra/xorg-server 1.12.1.902-1 -> 1.12.2-1
community/libuser 0.57.1-2 -> 0.57.6-1
community/os-prober 1.49-3 -> 1.53-1
community/systemd-arch-units 20120412-6 -> 20120528-3
repo-ck/linux-ck-corex 3.3.7-1 -> 3.4-1
repo-ck/linux-ck-corex-headers 3.3.7-1 -> 3.4-1
==> New package :
core/systemd-tools 184-2 (required by systemd)
Does the systemd not support btrfs subvolume as root partition??
Last edited by aduser (2012-06-02 17:45:39)

ZFS root filesystem & slice 7 for metadb (SUNWjet)

Hi,
I'm planning to use ZFS root filesystem in Sun Cluster 3.3 environment, as written in documentation when we will use UFS share diskset then we need to create small slice for metadb on slice 7. In standar installation we can't create slice 7 when we install solaris with zfs root, then we can create it with jumpstart profile below :
# example Jumpstart profile -- ZFS with
# space on s7 left out of the zpool for SVM metadb
install_type initial_install
cluster SUNWCXall
filesys c0t0d0s7 32
pool rpool auto 2G 2G c0t0d0s0
so, my question is : "when we use SUNWjet (JumpStart(tm) Enterprise Toolkit) how we can write the profile similar to above jumpstart profile"?
Thanks very much, for your best answer.

This can be done with JET
You create the template as normal.
Then create a profile file with the slice 7 line.
Then edit the template to use it.
see
---8<
# It is also possible to append additional profile information to the JET
# derived one. Do this using the base_config_profile_append variable, but
# don't forget to fill out the remaining base_config_profile variables.
base_config_profile=""
base_config_profile_append="
---8<
It is how OpsCentre (which uses JET) does it.
JET questions are best asked on the external JET alias at yahoogorups (until the forum is setup on OTN)

Frequent 'Filesystem Corrupt', Invalid File count

I have been getting this message every a couple of days in my MBP or iMac running 10.6.2. It happens/visible only when I runs Disk Utility and Verify Disk. Of course, this brings unsettling point to me when it comes now and then. Not to mention I have to boot from DVD to run disk utility to fix this
Error Message: Invalid file count (It should be xxxxx instead of xxx+1) AND
Error Message: Invalid volume directory count (It should be xxxxx instead of xxxx-1)
Any idea what causes this and what's the impact i.e. do I lose any files?
Thanks!!

Leonard Ong wrote:
Hi Tim,
By default, it is HFS+ Journaled (non-case sensitive). So I have also the same understanding that journalled filesystem should be robust as you wrote it. But the fact that this comes now and then, It created some doubts.
Is this a harmless error message or should I be worried about it. That basically my questions. I do repair when I see this.
It can't be because of disk is failing for a number of reason:
1) I have the same behavior both in my iMac and MBP
2) Both HDD has been replaced with new one recently
3) Both HDD has passed through surface scan from TechTool Deluxe 5.0.6, so no bad blocks
Still a puzzle...
Are you sure that the errors are showing up on both computers when performing either a "Verify Disk" or "Repair Disk" and NOT just a "Verify Disk Permissions" or "Repair Disk Permissions"? Permissions errors are mostly harmless. Filesystem errors (the sort you see when you ask for "Verify Disk" or "Repair Disk" in Disk Utility are not harmless and you should be worried about those.
If so, then either both drives are failing or your drives are being exposed to a strong enough magnetic field to damage their data (and that would have be pretty strong -- a common refrigerator magnet wouldn't do the trick.) In all of my years of working with journaled filesystems (or operating systems with "filesystem logging" which is the same thing) I have NEVER seen a journaled volume have filesystem errors unless it was physically failing.
Journaling will prevent filesystem errors if it's enabled for pretty much every cause except for a physically defective or damaged disk. Here's the short version of how journaling works...
Journaling (aka "filesystem logging") is intended to prevent filesystem corruption... and it's pretty rock-solid.
1) A "journal" (or "log") area is added.
2) A hard rule is established that, under no circumstances may the OS be performing writes to both the journal and the regular filesystem at the same time. One must be flushed before it can work on the other and vice versa.
3) When a write operation is about to happen, the OS writes information to the journal indicating which blocks on the filesystem are about to be changed and what it's about to change. This information is flushed to disk.
4) The OS can then perform the write on the actual filesystem areas it intended to change. These must then be flushed to disk.
5) The journal can now be cleared.
That's pretty much it (simplified). But think about what this does. Normally if something interrupts a write operation (something crashes, a kernel panic, a power loss, etc.) there is something that will still have integrity because the OS will not write to both the journal and the regular filesystem at the same time.
If a failure occurs while writing to the filesystem it's no big deal. When the system boots back up, it notices the journal wasn't cleared so it "replays" the journal. This re-writes any blocks that might only have been partially written thus clearing any chance of corruption on the volume.
If a failure occurs while writing to the journal it's still no big deal. When the system boots back up it notices a corrupt journal, but that means the regular filesystem itself wasn't being touched so the filesystem is guaranteed to not have errors on it (although it does mean the last file you were about to save probably didn't get saved -- and that file wouldn't have written successfully even if journaling were off. At least this way there is no filesystem corruption.)
While it sounds pretty solid (and it is) there's still a potential for corruption, but it's rare. If a drive swings the access arms to a specific track and starts writing data, the assumption is that the write head is above the correct track. If the head is "sloppy" due to wear, then the head may be slightly mis-aligned and bleeding writes into the adjacent track. This will cause filesystem corruption even with journaling enabled.
If these drives came with the computers then the only warranty would be via Apple. If you purchased these drives on your own then they probably came with a pretty good manufacturer warranty -- most drives I've purchased in recent years had at least a 3 year warranty.

Root filesystem corrupted, only var left

Similar Messages

Maybe you are looking for