search for: linux_raid_member

...gt; rd.md.uuid=ea5fede7:dc339c3b:81817fc4:aba0bd89 > rd.md.uuid=7a90faed:4e5a2b50:9baa8249:21a6c3da rhgb quiet > /dev/sda1: UUID="6f900f10-d951-2ae7-712c-a5710d8d7316" > UUID_SUB="541c8849-58bd-8309-96fd-b45faf0d40bb" LABEL="localhost:home" > TYPE="linux_raid_member" > /dev/sda2: UUID="ea5fede7-dc33-9c3b-8181-7fc4aba0bd89" > UUID_SUB="f127cce4-82f6-fa86-6bc5-2c6b8e3f8e7a" LABEL="localhost:root" > TYPE="linux_raid_member" > /dev/sda3: UUID="39f40c01-b62c-8434-741d-38ee40c227f9" > UUID_SUB=...

...al_e-lv_internal_srv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" vg_internal_e /dev/md3: UUID="1Fi2Ex-..." TYPE="LVM2_member" /dev/sda4: UUID="00029bd4-..." UUID_SUB="d0024074-..." LABEL="e.ld:3" TYPE="linux_raid_member" /dev/sdb4: UUID="00029bd4-..." UUID_SUB="bf98fc79-..." LABEL="e.ld:3" TYPE="linux_raid_member" beside blkid any other tool available? -- Thanks, LF

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

...rv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" > vg_internal_e > /dev/md3: UUID="1Fi2Ex-..." TYPE="LVM2_member" > /dev/sda4: UUID="00029bd4-..." UUID_SUB="d0024074-..." LABEL="e.ld:3" TYPE="linux_raid_member" > /dev/sdb4: UUID="00029bd4-..." UUID_SUB="bf98fc79-..." LABEL="e.ld:3" TYPE="linux_raid_member" > > beside blkid any other tool available? > > -- > Thanks, > LF > > ____________________________________________...

...nual and quite simple. Everything is RAID 1, I have a /boot array on /dev/sda1 + /dev/sdb1, swap on /dev/sda2 + /dev/sdb2 and / on /dev/sda3 + /dev/sdb3. I tried to mount /dev/sda3 directly from the rescue disk: # mount /dev/sda3 /mnt But I only get this: mount: unknown filesystem type 'linux_raid_member' I'd be very grateful for suggestions. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32

Hi all, Does anyone know how to determine which file system a disk was formatted with, if fdisk -l doesn't show it? usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 sd 7:0:0:0: Attached scsi disk sda sd 7:0:0:0: Attached scsi generic

...t; array on /dev/sda1 + /dev/sdb1, swap on /dev/sda2 + /dev/sdb2 and / on > /dev/sda3 + /dev/sdb3. > > > I tried to mount /dev/sda3 directly from the rescue disk: > > > # mount /dev/sda3 /mnt > > > But I only get this: > > > mount: unknown filesystem type 'linux_raid_member' > > > I'd be very grateful for suggestions. > Condolences. I think how I'd go about it would be to boot off a rescue disk, then either try to mount the raid, or just edit the /etc/mdadm.conf, and tell it only sda, and maybe sdb marked as failed. Then see if you can mount t...

...t; > The latest version (F-14) also supports RAIDs and LVM. > > Karel > > > > $ wipefs /home/images/filesystems/mdraid.img > > offset type > ---------------------------------------------------------------- > 0x9f0000 linux_raid_member [raid] > UUID: 37c76b91-011a-05c5-d30c-1fd4c5c3dbbc > > > $ wipefs /home/images/filesystems/lvm2.img > offset type > ---------------------------------------------------------------- > 0x218 LVM2_member [raid] >...