On Thu, Apr 4, 2019 at 8:51 PM <no_spam@xxxxxxxxxxxx> wrote: > # btrfs insp dump-s -fa /dev/>> > > > ERROR: bad magic on superblock on /dev/md3 at 65536 Wrong device. Your btrfs file system is not on /dev/md3, it's on /dev/mapper/vgsomething-lvsomething > <<# btrfs --version>> > btrfs-progs v4.0 That's April 2015. It's really old, but I don't see many restore fixes or enhancements explicitly listed; but it's always possible a fix could help. I dunno if you can easily compile things on the NAS, if not then compile from source elsewhere, tar up the directory, and untar it on the NAS user folder you're using (maybe that's root, no idea), and just use absolute paths to the newer btrfs binary, should work. Anyway, until further notice all commands will be read only anyway so even if it blows up it won't write. > I'll also note that your message prompted our colleagues and myself to > investigate this further, and upon further investigation we noticed > that the configuration from the rescued LVM metadata doesn't fully > match the backup metadata on the original system partition. I'm > escalating back to our developers and asking them double check and > make sure that we correctly recreated the volume group and LV, and > I'll let you know as soon as I hear back. OK good. -- Chris Murphy
