write(2, "main.main", 9main.main)                = 9                            write(2, "(", 1()                        = 1                                    write(2, ")\n", 2)                                                              )                      = 2                                                      write(2, "\t", 1        )                       = 1                             write(2, "./main.go", 9./main.go)                = 9                            write(2, ":", 1:)                        = 1                                    write(2, "64", 264)                       = 2                                   write(2, " +", 2 +)                       = 2                                   write(2, "0x47d", 50x47d)                    = 5                                write(2, "\n", 1                                                                )                       = 1                                                     exit_group(2)                           = ?                                     +++ exited with 2 +++                                                           admin@i-035d976ba3c56dd73:~$                                                    

rm: cannot remove 'datafile': Permission denied                                 admin@i-0726590fe1fcdef99:/mnt/new_partition$ sudo srm datafile                 sudo: srm: command not found                                                    admin@i-0726590fe1fcdef99:/mnt/new_partition$ sudo rm datafile                  admin@i-0726590fe1fcdef99:/mnt/new_partition$ ls                                lost+found                                                                      admin@i-0726590fe1fcdef99:/mnt/new_partition$ cd /                              admin@i-0726590fe1fcdef99:/$ ls                                                 bin   dev  home  lib32  libx32      media  opt   root  sbin  sys  usr           boot  etc  lib   lib64  lost+found  mnt    proc  run   srv   tmp  var           admin@i-0726590fe1fcdef99:/$ cd home/admin/                                     admin@i-0726590fe1fcdef99:~$ ls                                                 agent  data  datafile  kihei                                                    admin@i-0726590fe1fcdef99:~$ ln -s /mnt/new_partition/ test                     admin@i-0726590fe1fcdef99:~$ ls                                                 

otary_Club, Delta SkyMiles, the local library, and the Museum of Bash History. Teable and have no name, for some reason.                                        CLUE: Questioned the barista at the local coffee shop. He said a woman left rights. The name on her latte was Annabel, she had blond spiky hair and a New Zealanadmin@i-0a2012c5b0c99948f:~/clmystery/mystery$ ls                               crimescene  interviews  memberships  people  streets  vehicles                  admin@i-0a2012c5b0c99948f:~/clmystery/mystery$ cd ..                            admin@i-0a2012c5b0c99948f:~/clmystery$ ls                                       LICENSE.md  cheatsheet.md   hint1  hint3  hint5  hint7  instructions            README.md   cheatsheet.pdf  hint2  hint4  hint6  hint8  mystery                 admin@i-0a2012c5b0c99948f:~/clmystery$ cat hint3                                In order to track down our potential witness, we need to figure out where she li                                                                                Try using 'head' on some of the files like 'people' and 'vehicles' and see whereadmin@i-0a2012c5b0c99948f:~/clmystery$ cat hi                                   

fsck from util-linux 2.36.1                                                     e2fsck 1.46.2 (28-Feb-2021)                                                     ext2fs_open2: Bad magic number in super-block                                   fsck.ext2: Superblock invalid, trying backup blocks...                          fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme2n1p1                                                                                  The superblock could not be read or does not describe a valid ext2/ext3/ext4    filesystem.  If the device is valid and it really contains an ext2/ext3/ext4    filesystem (and not swap or ufs or something else), then the superblock         is corrupt, and you might try running e2fsck with an alternate superblock:          e2fsck -b 8193 <device>                                                      or                                                                                 e2fsck -b 32768 <device>                                                                                                                                    admin@i-0eacfe699faffbd49:~$