0

I'm new to this page and im not sure where to get help. I hope this would be an appropriate place.

TLDR: Docker overflowed server OS storage, after doing docker prune, i realised that my mounted drives are not there anymore? and everything seems to be off.

More context after TLDR: What started the discovery My immich server was not able to load, from there i tried to login via web GUI but i was not able to. Afraid that there was a case of a security breach?? i tried to force restart the server. (I am not sure if this will affect the drives). I then realised that it was a case of OS storage full.

Drives I have 2 drives, one 2tb one 512gb running in raid0, thus they should have alot of space but when i looked at my network drive, all i can see is 56.2GB which i assume is the onboard storage. Not mounted. But i can see under disk temperatures that both are doing well.

Trouble shooting I looked under File systems and it was just one file system, displaying - i looked at the shared files thru windows file explorer, i only can find my minecraft server which i remembered i stored in my raid0 drives? why is it doing here in the OS drive?? confused I looked at Multiple device, i can see that

/dev/md0 clean Stripe 2.27 TiB /dev/nvme1n1 /dev/nvme3n1

PICS!! : https://imgur.com/a/ftP3PIq

Im lost and im afraid to take more steps to troubleshoot.

Please keep my little hobby alive. Thank you for reading! Have a nice day ahead

$ lsblk

NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
mmcblk2      179:0    0  57.6G  0 disk
├─mmcblk2p1  179:1    0     4M  0 part
├─mmcblk2p2  179:2    0     4M  0 part
├─mmcblk2p3  179:3    0     4M  0 part
├─mmcblk2p4  179:4    0    16M  0 part
|─mmcblk2p5  179:5    0    40M  0 part
├─mmcblk2p6  179:6    0    32M  0 part
├─mmcblk2p7  179:7    0    32M  0 part
└─mmcblk2p8  179:8    0  57.5G  0 part  /
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
nvme1n1      259:0    0   1.8T  0 disk
└─md0          9:0    0   2.3T  0 raid0
nvme3n1      259:1    0 465.8G  0 disk
└─md0          9:0    0   2.3T  0 raid0

mount -a

mount: /srv/dev-disk-by-uuid-4b49873f-53f0-4490-a12d-4151af9b9723: must be superuser to use mount.
       dmesg(1) may have more information after failed mount system call.

sudo mdadm --examine /dev/nvme1n1

/dev/nvme1n1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1000
     Array UUID : 02e639b2:4d4a6007:d45663a3:1333c799
           Name : openmediavault:0  (local to host openmediavault)
  Creation Time : Fri Jul  5 23:05:07 2024
     Raid Level : raid0
   Raid Devices : 2

Avail Dev Size : 3906764976 sectors (1862.89 GiB 2000.26 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=264112 sectors, after=0 sectors State : clean Device UUID : c3bccf6f:3a250f78:471eb858:08fad37f

Update Time : Fri Jul  5 23:05:07 2024

Bad Block Log : 512 entries available at offset 8 sectors Checksum : 93ba78b8 - correct Events : 0

     Layout : original
 Chunk Size : 512K

Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

sudo mdadm --examine /dev/nvme3n1

/dev/nvme3n1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1000
     Array UUID : 02e639b2:4d4a6007:d45663a3:1333c799
           Name : openmediavault:0  (local to host openmediavault)
  Creation Time : Fri Jul  5 23:05:07 2024
     Raid Level : raid0
   Raid Devices : 2

Avail Dev Size : 976508976 sectors (465.64 GiB 499.97 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=264112 sectors, after=0 sectors State : clean Device UUID : 3fc24bba:dd4cda98:c24392a7:419f56af

Update Time : Fri Jul  5 23:05:07 2024

Bad Block Log : 512 entries available at offset 8 sectors Checksum : ceb6480c - correct Events : 0

     Layout : original
 Chunk Size : 512K

Device Role : Active device 1 Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

UPDATES: OMG I THINK I MESSED UP, i did

sudo mdadm --stop /dev/md0 mdadm --assemble --run /dev/md0 /dev/nvme1n1 /dev/nvme3n1

then

sudo mkfs.ext4 /dev/md0

mke2fs 1.47.0 (5-Feb-2023)
/dev/md0 contains a btrfs file system
Proceed anyway? (y,N) y
Discarding device blocks: done
Creating filesystem with 610409216 4k blocks and 152608768 inodes
Filesystem UUID: 84f31daf-3006-4a12-869e-1d4ba931c239
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776

Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done

And when i mounted it all i saw was "lost+found" Am i cooked :(

Checking lsblk I still can see that my 900gb is still there?

reeve@openmediavault:/$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
mmcblk2      179:0    0  57.6G  0 disk
├─mmcblk2p1  179:1    0     4M  0 part
├─mmcblk2p2  179:2    0     4M  0 part
├─mmcblk2p3  179:3    0     4M  0 part
├─mmcblk2p4  179:4    0    16M  0 part
├─mmcblk2p5  179:5    0    40M  0 part
├─mmcblk2p6  179:6    0    32M  0 part
├─mmcblk2p7  179:7    0    32M  0 part
└─mmcblk2p8  179:8    0  57.5G  0 part  /
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
nvme1n1      259:0    0   1.8T  0 disk
└─md0          9:0    0   2.3T  0 raid0
nvme3n1      259:1    0 465.8G  0 disk
└─md0          9:0    0   2.3T  0 raid0

1 Answers1

0

Depends on your definition of cooked. Your MD volume is now an empty ext4 filesystem; running mkfs.ext4 and confirming that you wanted the existing btrfs filesystem overwritten pretty much assured that. You do have your 2.3TB data volume still, just there is now nothing recoverable on it. Your 57.5G OS volume has not been touched through all of this, which is why you can still boot. And I'd guess that your OS drive is also the one that you're seeing on the Windows file share.

tsc_chazz
  • 2,941