10-09-2008
Ouch!
Have you done ANYTHING to md0 or the underlying devices since then??
I believe that md0 uses an on-disk block for tracking meta information, but that essentially, the underlying partitions are simply kept in sync as normal filesystems are. Translation: you can directly mount the underlying file system. If they're not too out-of-sync, you can just fsck and mount. If the fsck fails at first because the md0 blasted it (unlikely), you can just use a backup superblock and specify that to fsck.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey peeps,
Here is somethin u might find interestin....
Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :)
I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies
2. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
3. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
4. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
5. Filesystems, Disks and Memory
Hi
I am new on your forum, because I need some help.
I have a server with debian and proxmox 2.
The HardDisk is broken.
I am in rescue mode, and I can't mount LVM partition to recover my backups.
What I've already done :
# fdisk -l
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255... (0 Replies)
Discussion started by: pppplu
0 Replies
6. UNIX for Advanced & Expert Users
Hi guys,
I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss.
I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates).
Basic system spec:
AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies
7. Linux
Hi all,
I been trying to recover a volume group of single PV.
vgcfgrestore output
# vgcfgrestore vgoraData
Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
Cannot restore Volume Group vgoraData with 1 PVs marked as missing.
Restore failed.
fdisk output
... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies
LEARN ABOUT MOJAVE
systemd-fsck
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)
NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but
only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root
file system in the initramfs.
These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
rotating disk.
systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
mounts, unclean unmount, etc.
If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
fsck.repair=
One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.
SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)
systemd 237 SYSTEMD-FSCK@.SERVICE(8)