Um, I forgot that with a fresh install, I have to remember what all
tools I had installed and re-install 'em.
bach:/home/bkorb # /home/bkorb/bin/lsdrv/lsdrv-master/lsdrv
PCI [ahci] 00:11.4 SATA controller: Intel Corporation C610/X99 series
chipset sSATA Controller [AHCI mode] (rev 05)
├scsi 0:0:0:0 ATA TOSHIBA HDWE160 {487OK01XFB8G}
│└sda 5.46t [8:0] Partitioned (gpt)
│ ├sda1 128.00g [8:1] btrfs 'OPT-USR' {649826e5-7406-49fb-ad4a-a35a0077a325}
│ │└Mounted as /dev/sda1 @ /opt
│ ├sda3 64.00g [8:3] Empty/Unknown
│ ├sda4 16.00g [8:4] Empty/Unknown
│ └sda5 5.25t [8:5] MD raid1 (0/2) (w/ sdb5) in_sync 'bach:0'
{0e2cb19c-b567-5fcc-2982-c38e81e42a71}
│ └md0 5.25t [9:0] MD v1.2 raid1 (2) clean
{0e2cb19c:-b567-5f:cc-2982-:c38e81e42a71}
│ │ ext4 'HOME' {a6551143-65ab-40ff-82b6-8cc809a1a856}
│ └Mounted as /dev/md0 @ /home
├scsi 1:0:0:0 ATA TOSHIBA HDWE160 {487OK01SFB8G}
│└sdb 5.46t [8:16] Partitioned (gpt)
│ ├sdb1 192.00g [8:17] btrfs 'VAR-TMP' {c1304823-0b3b-4655-bfbb-a7f064ec59f5}
│ │└Mounted as /dev/sdb1 @ /var
│ ├sdb2 16.00g [8:18] Empty/Unknown
│ └sdb5 5.25t [8:21] MD raid1 (1/2) (w/ sda5) in_sync 'bach:0'
{0e2cb19c-b567-5fcc-2982-c38e81e42a71}
│ └md0 5.25t [9:0] MD v1.2 raid1 (2) clean
{0e2cb19c:-b567-5f:cc-2982-:c38e81e42a71}
│ ext4 'HOME' {a6551143-65ab-40ff-82b6-8cc809a1a856}
├scsi 2:0:0:0 ATA HGST HMS5C4040AL {PL1331LAHEZZ5H}
│└sdc 3.64t [8:32] Partitioned (gpt)
│ ├sdc1 3.20t [8:33] MD raid0 (0/2) (w/ sde1) in_sync 'any:1'
{f624aab2-afc1-8758-5c20-d34955b9b36f}
│ │└md1 6.40t [9:1] MD v1.0 raid0 (2) clean, 64k Chunk, None (None)
None {f624aab2:-afc1-87:58-5c20-:d34955b9b36f}
│ │ xfs 'User' {fe716da2-b515-4fd6-8ea6-f44f48038b78}
│ ├sdc2 320.00g [8:34] ext4 'PHOTOS-B' {4ab1a2c2-dbee-4f4d-b491-8652ea7a24d7}
│ └sdc3 65.22g [8:35] ext4 'TEMP' {c18c28d3-dafd-4f1b-aa9f-b7a462139073}
└scsi 3:0:0:0 ATA WDC WDS250G2B0A- {181202806197}
└sdd 232.89g [8:48] Partitioned (gpt)
├sdd1 901.00m [8:49] vfat 'BOOT-EFI' {AF1B-15D7}
│└Mounted as /dev/sdd1 @ /boot/efi
├sdd2 116.00g [8:50] Partitioned (dos) 'ROOT1'
{63e24f52-2f8f-4ad1-a1e6-cb5537efcf6f}
│├Mounted as /dev/sdd2 @ /
│├Mounted as /dev/sdd2 @ /.snapshots
│├Mounted as /dev/sdd2 @ /boot/grub2/i386-pc
│├Mounted as /dev/sdd2 @ /boot/grub2/x86_64-efi
│├Mounted as /dev/sdd2 @ /srv
│├Mounted as /dev/sdd2 @ /usr/local
│├Mounted as /dev/sdd2 @ /tmp
│└Mounted as /dev/sdd2 @ /root
└sdd3 116.01g [8:51] xfs 'ROOT2' {69178c35-15ea-4f04-8f29-bf4f1f6f890a}
└Mounted as /dev/sdd3 @ /root2
PCI [ahci] 00:1f.2 SATA controller: Intel Corporation C610/X99 series
chipset 6-Port SATA Controller [AHCI mode] (rev 05)
├scsi 4:0:0:0 ATA HGST HMS5C4040AL {PL1331LAHGEP7H}
│└sde 3.64t [8:64] Partitioned (gpt)
│ ├sde1 3.20t [8:65] MD raid0 (1/2) (w/ sdc1) in_sync 'any:1'
{f624aab2-afc1-8758-5c20-d34955b9b36f}
│ │└md1 6.40t [9:1] MD v1.0 raid0 (2) clean, 64k Chunk, None (None)
None {f624aab2:-afc1-87:58-5c20-:d34955b9b36f}
│ │ xfs 'User' {fe716da2-b515-4fd6-8ea6-f44f48038b78}
│ ├sde2 64.00g [8:66] swap {dbd52b6f-fc65-42e9-948b-33d9c3834c3c}
│ └sde3 385.22g [8:67] ext4 'PHOTO-A' {c84250ab-6563-4832-a919-632a34486bf1}
└scsi 5:0:0:0 HL-DT-ST BD-RE WH14NS40 {SIK9TH8SE163}
└sr0 1.00g [11:0] Empty/Unknown
USB [usb-storage] Bus 002 Device 007: ID 05e3:0745 Genesys Logic, Inc.
Logilink CR0012 {000000000903}
└scsi 10:0:0:0 Generic STORAGE DEVICE {000000000503}
└sdf 0.00k [8:80] Empty/Unknown
USB [usb-storage] Bus 002 Device 008: ID 058f:6387 Alcor Micro Corp.
Flash Drive {A3A1458D}
└scsi 11:0:0:0 Generic Flash Disk {A}
└sdg 28.91g [8:96] Partitioned (dos)
└sdg1 28.91g [8:97] vfat '32GB' {1D6B-D5DB}
└Mounted as /dev/sdg1 @ /run/media/bkorb/32GB
Hmm. Interesting. Dunno what that /dev/sdf thingy is. I only have one
thumb drive plugged in and mounted as /dev/sdg1.
- Bruce
On Fri, Apr 1, 2022 at 10:59 AM Bruce Korb <bruce.korb@xxxxxxxxx> wrote:
>
> Hi,
> Thank you again. I've attached a typescript of the commands. Here are
> the line numbers where the commands get issued. The relevant
> partitions are on /dev/sdc1 and /dev/sde1:
>
> 1:>3> uname -a
> 3:>4> mdadm --version
> 5:>5> for d in /dev/sd[ce]
> 6:>7> smartctl --xall /dev/sdc
> 252:>8> mdadm --examine /dev/sdc
> 256:>9> mdadm --examine /dev/sdc1
> 281:>5> for d in /dev/sd[ce]
> 282:>7> smartctl --xall /dev/sde
> 556:>8> mdadm --examine /dev/sde
> 560:>9> mdadm --examine /dev/sde1
> 585:>11> mdadm --detail /dev/md1
> 614:>12> /home/bkorb/bin/lsdrv/lsdrv-master/lsdrv
>
> Right after line 256, you'll see the fateful info:
> 263 Creation Time : Tue Mar 29 11:02:09 2022
> 264 Raid Level : raid0
>
> The first block of /dev/sdc1 contains:
> bkorb@bach:~> sudo od -Ax -N 4096 -tx1 /dev/sdc1
> 000000 58 46 53 42 00 00 10 00 00 00 00 00 33 33 32 d0
> 000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 000020 fe 71 6d a2 b5 15 4f d6 8e a6 f4 4f 48 03 8b 78
> 000030 00 00 00 00 20 00 00 07 00 00 00 00 00 00 00 60
> 000040 00 00 00 00 00 00 00 61 00 00 00 00 00 00 00 62
> 000050 00 00 00 01 0c cc cc b4 00 00 00 04 00 00 00 00
> 000060 00 06 66 66 bc b5 10 00 02 00 00 08 55 73 65 72
> 000070 00 00 00 00 00 00 00 00 0c 0c 09 03 1c 00 00 05
> 000080 00 00 00 00 00 15 9c 80 00 00 00 00 00 00 2b 48
> 000090 00 00 00 00 27 92 36 06 00 00 00 00 00 00 00 00
> 0000a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0000b0 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
> 0000c0 00 0c 10 00 00 00 10 00 00 00 01 8a 00 00 01 8a
> 0000d0 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00
> 0000e0 6f 7c f9 cc 00 00 00 00 ff ff ff ff ff ff ff ff
> 0000f0 00 00 00 7a 00 31 11 20 00 00 00 00 00 00 00 00
> 000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> I wouldn't know how to find the file system start. :)
>
> - Bruce
>
> On Thu, Mar 31, 2022 at 2:34 PM Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote:
> >
> > On 31/03/2022 19:14, Bruce Korb wrote:
> > > On Thu, Mar 31, 2022 at 10:06 AM Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote:
> > >>
> > >> On 31/03/2022 17:44, Bruce Korb wrote:
> > >>> I moved the two disks from a cleanly shut down system that could not
> > >>> reboot and could not
> > >>> be upgraded to a new OS release. So, I put them in.a new box and did an install.
> > >>> The installation recognized them as a RAID and decided that the
> > >>> partitions needed a
> > >>> new superblock of type RAID-0.
> > >>
> > >> That's worrying, did it really write a superblock?
> > >
> > > Yep. That worried me, too. I did the command to show the RAID status of the two
> > > partitions and, sure enough, both partitions were now listed as RAID0.
> > >
> > >>> Since these data have never been
> > >>> remounted since the
> > >>> shutdown on the original machine, I am hoping I can change the RAID
> > >>> type and mount it
> > >>> so as to recover my. .ssh and .thunderbird (email) directories. The
> > >>> bulk of the data are
> > >>> backed up (assuming no issues with the full backup of my critical
> > >>> data), but rebuilding
> > >>> and redistributing the .ssh directory would be a particular nuisance.
> > >>>
> > >>> SO: what are my options? I can't find any advice on how to tell mdadm
> > >>> that the RAID-0 partitions
> > >>> really are RAID-1 partitions. Last gasp might be to "mdadm --create"
> > >>> the RAID-1 again, but there's
> > >>> a lot of advice out there saying that it really is the last gasp
> > >>> before giving up. :)
> > >>>
> > >>
> > >> https://raid.wiki.kernel.org/index.php/Asking_for_help
> > >
> > > Sorry about that. I have two systems: the one I'm typing on and the one
> > > I am trying to bring up. At the moment, I'm in single user mode building
> > > out a new /home file system. mdadm --create is 15% done after an hour :(.
> > > It'll be mid/late afternoon before /home is rebuilt, mounted and I'll be
> > > able to run display commands on the "old" RAID1 (or 0) partitions.
> > >
> > >> Especially lsdrv. That tells us a LOT about your system.
> > >
> > > Expect email in about 6 hours or so. :) But openSUSE doesn't know
> > > about any "lsdrv" command. "cat /proc/mdstat" shows /dev/md1 (the
> > > RAID device I'm fretting over) to be active, raid-0 using /dev/sdc1 and sde1.
> >
> > Well, the webpage does tell you where to download it from - it's not
> > part of the official tools, and it's a personal thing that's damn useful.
> > >
> > >> What was the filesystem on your raid? Hopefully it's as simple as moving
> > >> the "start of partition", breaking the raid completely, and you can just
> > >> mount the filesystem.
> > >
> > > I *think* it was EXT4, but. it might be the XFS one. I think I let it default
> > > and openSUSE appears to prefer the XFS file system for RAID devices.
> > > Definitely one of those two. I built it close to a decade ago, so I'll be moving
> > > the data to the new /home array.
> > >
> > >> What really worries me is how and why it both recognised it as a raid,
> > >> then thought it needed to be converted to raid-0. That just sounds wrong
> > >> on so many levels. Did you let it mess with your superblocks? I hope you
> > >> said "don't touch those drives"?
> > >
> > > In retrospect, I ought to have left the drives unplugged until the install was
> > > done. The installer saw that they were RAID so it RAID-ed them. Only it
> > > seems to have decided on type 0 over type 1. I wasn't attentive because
> > > I've upgraded Linux so many times and it was "just done correctly" without
> > > having to give it a lot of thought. "If only" I'd thought to back up
> > > email and ssh.
> > > (1.5TB of photos are likely okay.)
> > >
> > > Thank you so much for your reply and potentially help :)
> > >
> > If it says the drive is active ...
> >
> > When you get and run lsdrv, see if it finds a filesystem on the raid-0 -
> > I suspect it might!
> >
> > There's a bug, which should be well fixed, but it might have bitten you.
> > It breaks raid arrays. But if the drive is active, it might well mount,
> > and you will be running a degraded mirror. Mount it read-only, back it
> > up, and then see whether you can force-assemble the two bits back
> > together :-)
> >
> > But don't do anything if you have any trouble whatsoever mounting and
> > backing up.
> >
> > Cheers,
> > Wol
