NAS520: Restore access to lost volume/disk 1 [SOLVED]

Options
ariek
ariek Posts: 30  Freshman Member
First Anniversary 10 Comments
edited November 2019 in Personal Cloud Storage
I have lost access to volume 1/disk 1/sysvol. I can logon to the NAS520 and when I choose "Storage Manager" it tells me that there is "No Storage" on the internal volume (external drives are not connected). Obviously, I can create a new volume but this will erase all data on the HDD will be lost.

However, when I click on other icons in the webgui, everything that is on the HDD is visible/present.


#NAS_Nov_2019


«1

Comments

  • lodiabai
    lodiabai Posts: 120  Ally Member
    Options
    What kind of RAID Type you used? Is there any screenshots?

    When you used File Browser of NAS520 or CIFS or FTP or ..., do you able to access your data?
    If yes, I suggest you to backup your data first.
  • ariek
    ariek Posts: 30  Freshman Member
    First Anniversary 10 Comments
    edited November 2019
    Options
    It is only 1 HDD. JBOD structure and that is to my knowledge just a plain ext4 drive.
    The status is LOST, internal HDD, and can't access the data because the volume doesn't exist (not recognized). I have to create a new volume but that will format the drive and all data will be lost.

    With MiniTools Partition Manager the HDD (note: I have changed some partitions from primary to logical)
    When I hook up the drive as an external drive I can access the drive content. The 'main partition' [with all my files, etc.] and the 'system partition' (which contains a system.img).
    The file structure:
    I'm able to access the drive content when the HDD is mounted as an external drive (USB1) but I can't when the drive is an internal drive, as the drive is not mounted or not recognized as a valid volume.
    If only I could fix the mounting of the internal HDD. Theoretically, the NAS should be functioning just fine.

    I can connect to the NAS over telnet/SSH but only have access to the ram drive.



  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    (note: I have changed some partitions from primary to logical)

    Why? In that case the disk is no longer recognized as internal disk. At boot this script is run to check if it's a valid internal disk:

    <p>#action: check is legal disk partition format<br># 1. check in internal disk<br># 2. check disk partition number<br># 3. check FW size<br># 4. check swap size<br>CheckInternalDiskFormat()<br>{<br>&nbsp;&nbsp;&nbsp; sdx=$1<br>&nbsp;&nbsp;&nbsp; IsInternDisk="`${INTERN_DISK_CHKER} -c ${sdx}`"<br>&nbsp;&nbsp;&nbsp; if [ "${IsInternDisk}" != "yes" ]; then<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return ${FAIL}<br>&nbsp;&nbsp;&nbsp; fi<br><br>&nbsp;&nbsp;&nbsp; numOfDiskPart=`${LS} -d /sys/block/${sdx}/${sdx}? | ${WC} -l`<br>&nbsp;&nbsp;&nbsp; if [ ${numOfDiskPart} != ${LEGAL_DISK_PARTITION_NUM} ]; then<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return ${FAIL}<br>&nbsp;&nbsp;&nbsp; fi<br><br>&nbsp;&nbsp;&nbsp; sdx1Siz=`${CAT} /sys/block/${sdx}/${sdx}1/size`<br>&nbsp;&nbsp;&nbsp; if [ ${sdx1Siz} != ${LEGAL_FW_SIZ} ]; then<br><br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return ${FAIL}<br>&nbsp;&nbsp;&nbsp; fi<br><br>&nbsp;&nbsp;&nbsp; sdx2Siz=`${CAT} /sys/block/${sdx}/${sdx}2/size`<br>&nbsp;&nbsp;&nbsp; if [ ${sdx2Siz} != ${LEGAL_SWAP_SIZ} ]; then<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return ${FAIL}<br>&nbsp;&nbsp;&nbsp; fi<br><br>&nbsp;&nbsp;&nbsp; return ${SUCCESS}<br>}<br></p>
    It checks partitions 1 and 2 for their sizes. A problem is that the primary partitions are numbered 1..4, while the logical partitions are numbered 5... . So this disk is no longer valid. Can you change that back?
  • ariek
    ariek Posts: 30  Freshman Member
    First Anniversary 10 Comments
    edited November 2019
    Options
    I can change the partitions back from logical to primary with MiniTool Partition manager.
    After changing it, the HDD is still not recognized as an internal HDD/Volume.
    # cat /proc/mdstat<br>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]<br>unused devices: <none>
    # fdisk -l<br><br>Disk /dev/loop0: 144 MiB, 150994944 bytes, 294912 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock0: 256 KiB, 262144 bytes, 512 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock2: 256 KiB, 262144 bytes, 512 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock3: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock5: 110 MiB, 115343360 bytes, 225280 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock6: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock7: 110 MiB, 115343360 bytes, 225280 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock8: 6 MiB, 6291456 bytes, 12288 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 4096 bytes<br>I/O size (minimum/optimal): 4096 bytes / 4096 bytes<br>Disklabel type: dos<br>Disk identifier: 0x1394754f<br><br>Device&nbsp;&nbsp;&nbsp;&nbsp; Boot&nbsp;&nbsp; Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; End&nbsp;&nbsp;&nbsp; Sectors&nbsp; Size Id Type<br>/dev/sda1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995520&nbsp; 1.9G 83 Linux<br>/dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8261632 3907028607 3898766976&nbsp; 1.8T 83 Linux
    I'm not sure if the partition IDs (83) are correct.
    <div><br></div><div>43 Linux Native (sharing disk with DRDOS)<br></div><div>82 Linux swap<br></div><div>83 Linux native</div><div><br></div><div>85 Extended Linux</div><div><br></div><div>88 Linux plain text partition table</div><div><br></div><div>F0 Linux/PA-RISC Boot Loader<br></div><div>FD Linux Raid Auto</div><div><br></div>





  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Hm. That didn't work out as intended. Somehow the size of the partition 1 changed by converting to logical and back, and somehow your 2nd partition is lost.
    /dev/sda1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995520&nbsp; 1.9G 83 Linux
    The script wants another size:
    LEGAL_FW_SIZ=3997696&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; #2047MB using parted created<br>LEGAL_SWAP_SIZ=3999744&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; #2048MB using parted created<br>
    and indeed my 520 has this sizes:
    <div>Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; End&nbsp;&nbsp;&nbsp; Sectors&nbsp;&nbsp; Size Type<br>/dev/sda1&nbsp;&nbsp;&nbsp;&nbsp; 2048&nbsp;&nbsp;&nbsp; 3999743&nbsp;&nbsp;&nbsp; 3997696&nbsp;&nbsp; 1.9G Linux RAID<br>/dev/sda2&nbsp; 3999744&nbsp;&nbsp;&nbsp; 7999487&nbsp;&nbsp;&nbsp; 3999744&nbsp;&nbsp; 1.9G Linux RAID<br>/dev/sda3&nbsp; 7999488 1953523711 1945524224 927.7G Linux RAID<br></div>
    Have you run some partition seek tool on this disk? It is striking that my 1st partition starts on sector 2048, while yours start on 4096. But mine has a raid array header of 2048 sectors, and the datasize of the array is 3995520, which exactly matches your partition size.

    &nbsp;&nbsp; Device Role : Active device 0<br>&nbsp;&nbsp; Array State : A. ('A' == active, '.' == missing)<br>mdadm --examine /dev/sda1<br>/dev/sda1:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Magic : a92b4efc<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version : 1.2<br>&nbsp;&nbsp;&nbsp; Feature Map : 0x0<br>&nbsp;&nbsp;&nbsp;&nbsp; Array UUID : 87cde249:5bd2cad3:9d19e8e2:96d47bda<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Name : NAS520:0&nbsp; (local to host NAS520)<br>&nbsp; Creation Time : Fri Aug 28 19:06:56 2015<br>&nbsp;&nbsp;&nbsp;&nbsp; Raid Level : raid1<br>&nbsp;&nbsp; Raid Devices : 2<br><br>&nbsp;Avail Dev Size : 3995648 (1951.33 MiB 2045.77 MB)<br>&nbsp;&nbsp;&nbsp;&nbsp; Array Size : 1997760 (1951.27 MiB 2045.71 MB)<br>&nbsp; Used Dev Size : 3995520 (1951.27 MiB 2045.71 MB)<br>&nbsp;&nbsp;&nbsp; Data Offset : 2048 sectors<br>&nbsp;&nbsp; Super Offset : 8 sectors<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; State : clean<br>&nbsp;&nbsp;&nbsp; Device UUID : e1c1bd04:3bcd2c01:e7ee3d59:7c7152d6<br><br>&nbsp;&nbsp;&nbsp; Update Time : Sat Nov 16 09:46:06 2019<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Checksum : d32e8be3 - correct<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Events : 2434<br>
    So a tool searching for filesystems could have done this.

    If that is the case, I think you can clone my partition table, except for the end of partition 3. That should be the highest available sector number.

  • ariek
    ariek Posts: 30  Freshman Member
    First Anniversary 10 Comments
    edited November 2019
    Options
    This was my 'sysvol'
    /i-data/e162cf92/

    <div>&nbsp;# mdadm --examine /dev/sda1<br>/dev/sda1:<br>&nbsp;&nbsp; MBR Magic : aa55<br>Partition[0] :&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3995520 sectors at&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 63 (type 85)<br>~ # mdadm --examine /dev/sda2<br>mdadm: No md superblock detected on /dev/sda2.<br><br></div><br>
    Above is the current state. As is the ouput of my previous post.
    Below the output is posted of the previous state before I converted partitions back from logical to primary.
    # cat /proc/mdstat<br>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]<br>unused devices: <none><br><br>fdisk -l<br><br>Disk /dev/loop0: 144 MiB, 150994944 bytes, 294912 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock0: 256 KiB, 262144 bytes, 512 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock2: 256 KiB, 262144 bytes, 512 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock3: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock5: 110 MiB, 115343360 bytes, 225280 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock6: 10 MiB, 10485760 bytes, 20480 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock7: 110 MiB, 115343360 bytes, 225280 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/mtdblock8: 6 MiB, 6291456 bytes, 12288 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 4096 bytes<br>I/O size (minimum/optimal): 4096 bytes / 4096 bytes<br>Disklabel type: dos<br>Disk identifier: 0x1394754f<br><br>Device&nbsp;&nbsp;&nbsp;&nbsp; Boot&nbsp;&nbsp; Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; End&nbsp;&nbsp;&nbsp; Sectors&nbsp; Size Id Type<br>/dev/sda1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4033&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995583&nbsp; 1.9G&nbsp; f W95 Ext'd (LBA)<br>/dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8261632 3907028607 3898766976&nbsp; 1.8T 83 Linux<br>/dev/sda5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995520&nbsp; 1.9G 83 Linux<br><br>Partition 2 does not start on physical sector boundary.<br>Partition table entries are not in disk order.<br><br><br>&nbsp;mdadm --examine /dev/sda1<br>/dev/sda1:<br>&nbsp;&nbsp; MBR Magic : aa55<br>Partition[0] :&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3995520 sectors at&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 63 (type 83)<br><br># mdadm --examine /dev/sda2<br>mdadm: No md superblock detected on /dev/sda2.<br>mdadm: No md superblock detected on /dev/sda5.<br><br><br># mdadm --assemble --scan<br>mdadm main: failed to get exclusive lock on mapfile<br>mdadm: No arrays found in config file or automatically
    Are Zyxel NASes formatted as ext2 or ext4?
    I don't know how to clone partition table, be I would give it a try.



  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    edited November 2019
    Options
    Device&nbsp;&nbsp;&nbsp;&nbsp; Boot&nbsp;&nbsp; Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; End&nbsp;&nbsp;&nbsp; Sectors&nbsp; Size Id Type<br>/dev/sda1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4033&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995583&nbsp; 1.9G&nbsp; f W95 Ext'd (LBA)<br>/dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8261632 3907028607 3898766976&nbsp; 1.8T 83 Linux<br>/dev/sda5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096&nbsp;&nbsp;&nbsp; 3999615&nbsp;&nbsp;&nbsp; 3995520&nbsp; 1.9G 83 Linux
    You have only 2 partitions here. Sda1 is an extended partition, which contains one logical partition sda5. You can see that on their start- and end sectors. And sda2 is a primary partition, containing your data. (Somehow, I hope).

    Let's have a look if a raid header can be found at sectors 2048 and 7999488, which is where they should be, according to my partition table.
    Create a loopdevice at the given offset of sda, and let mdadm have a look at it:
    <div>losetup -o 2097152 /dev/loop1 /dev/sda</div><div><br></div><div>mdadm --examine /dev/loop1</div><div><br></div><div>losetup -d /dev/loop1</div><div><br></div><div><br></div><div><div>losetup -o 4095737856 /dev/loop1 /dev/sda</div><div><br></div><div>mdadm --examine /dev/loop1</div><div><br></div><div>losetup -d /dev/loop1</div><div></div></div>
    Are Zyxel NASes formatted as ext2 or ext4?
    The 520 ext4. Older ones used ext3, xfs or reiserfs.
    I don't know how to clone partition table, be I would give it a try.
    That is the next step.

  • ariek
    ariek Posts: 30  Freshman Member
    First Anniversary 10 Comments
    edited November 2019
    Options
    # losetup -o 2097152 /dev/loop1 /dev/sdamdadm --examine /dev/loop1losetup -d /<br>dev/loop1<br>losetup: unrecognized option '--examine'<br>BusyBox v1.19.4 (2018-11-08 14:45:19 CST) multi-call binary.<br><br>Usage: losetup [-o OFS] LOOPDEV FILE - associate loop devices<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; losetup -d LOOPDEV - disassociate<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; losetup [-f] - show<br><br>~ # losetup -o 4095737856 /dev/loop1 /dev/sdamdadm --examine /dev/loop1losetup -<br>d /dev/loop1<br>losetup: unrecognized option '--examine'<br>BusyBox v1.19.4 (2018-11-08 14:45:19 CST) multi-call binary.<br><br>Usage: losetup [-o OFS] LOOPDEV FILE - associate loop devices<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; losetup -d LOOPDEV - disassociate<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; losetup [-f] - show<br><br>~ #
    I've got an error.

    losetup<br>/dev/loop0: 0 /firmware/mnt/sysdisk/sysdisk.img


  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Sorry. Stupid forumsoftware bôrked up my commands. I've edited my post.
  • ariek
    ariek Posts: 30  Freshman Member
    First Anniversary 10 Comments
    Options
    # losetup -o 2097152 /dev/loop1 /dev/sda<br>~ # mdadm --examine /dev/loop1<br>mdadm: No md superblock detected on /dev/loop1.<br>~ # losetup -d /dev/loop1<br>~ #<br>~ # losetup -o 4095737856 /dev/loop1 /dev/sda<br>~ # mdadm --examine /dev/loop1<br>/dev/loop1:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Magic : a92b4efc<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version : 1.2<br>&nbsp;&nbsp;&nbsp; Feature Map : 0x0<br>&nbsp;&nbsp;&nbsp;&nbsp; Array UUID : e162cf92:8d8b0390:a6f1e2ac:d411daa8<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Name : NAS520:2&nbsp; (local to host NAS520)<br>&nbsp; Creation Time : Thu Dec&nbsp; 3 10:29:20 2015<br>&nbsp;&nbsp;&nbsp;&nbsp; Raid Level : raid1<br>&nbsp;&nbsp; Raid Devices : 1<br><br>&nbsp;Avail Dev Size : 3898767360 (1859.08 GiB 1996.17 GB)<br>&nbsp;&nbsp;&nbsp;&nbsp; Array Size : 1949383488 (1859.08 GiB 1996.17 GB)<br>&nbsp; Used Dev Size : 3898766976 (1859.08 GiB 1996.17 GB)<br>&nbsp;&nbsp;&nbsp; Data Offset : 262144 sectors<br>&nbsp;&nbsp; Super Offset : 8 sectors<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; State : clean<br>&nbsp;&nbsp;&nbsp; Device UUID : 96ebf461:9976417b:13438673:58d3f678<br><br>&nbsp;&nbsp;&nbsp; Update Time : Thu Nov 14 18:16:56 2019<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Checksum : d7b1b221 - correct<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Events : 215<br><br><br>&nbsp;&nbsp; Device Role : Active device 0<br>&nbsp;&nbsp; Array State : A ('A' == active, '.' == missing)<br>~ # losetup -d /dev/loop1<br><br><br>



Consumer Product Help Center