What a pain in the $%^&*( ass.
Lenovo has no concept of using a md5 checksum on a file to confirm its integrity before you flash it and end up with a corrupted NAS like me.
AND to top it off, Lenovo support only offers a destructive way to reflash the NAS, double %^&*()^& in the ass.
So, initially I thought the drives were set up as a zfs disk set – installed the zfs needed debs on my debian jessie system only to find out all the lenovo disk set is is a linux md raid set, so (pulling this from my bash history)
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 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: gpt Disk identifier: 276C4C51-BFA8-4E33-AB51-FC7033AA6D56 Device Start End Sectors Size Type /dev/sdd1 65536 42008575 41943040 20G Microsoft basic data /dev/sdd2 42008576 3907028991 3865020416 1.8T Microsoft basic data Once I figured out it was just a md linux raid set, it was easy peasy to import : root@dell:~# mdadm --assemble --run /dev/md1 /dev/sdd2 mdadm: /dev/md1 has been started with 1 drive (out of 2). # DOH! no lvm2 installed on the system root@dell:~# mount /dev/md1 /mnt mount: unknown filesystem type 'LVM2_member' root@dell:~# pvscan -su: pvscan: command not found root@dell:~# apt-get install lvm2 pvscan, vgscan, and lvscan bought it LV into devicemapper root@dell:~# pvscan PV /dev/md1 VG bad2c48_vg lvm2 [1.80 TiB / 0 free] Total: 1 [1.80 TiB] / in use: 1 [1.80 TiB] / in no VG: 0 [0 ] root@dell:~# vgscan Reading all physical volumes. This may take a while... Found volume group "bad2c48_vg" using metadata type lvm2 root@dell:~# lvscan ACTIVE '/dev/bad2c48_vg/lv3140cc7e' [1.80 TiB] inherit Mounted it up, root@dell:~# sudo mount /dev/bad2c48_vg/lv3140cc7e /mnt bingo - now I can find 1.8TB worth of space elsewhere to rsync all that %^&*( data off so I can follow Lenovo's destructive NAS rebuild.