Jump to content

Alpha.Ars

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by Alpha.Ars

  1. uhm wait. I tried it like tat and looks like it's working docker exec -u root nextcloud chown -R 33:33 * But I can't access the website
  2. hmmm well: Di I have to edit my data dir too ?
  3. right now it is nobody users Should I: chown -R user:33 ?
  4. I'm having a permission problem. In the logs of nextcloud-cronjob I get this feedback Cannot write into "config" directory! This can usually be fixed by giving the web server write access to the config directory. But, if you prefer to keep config.php file read only, set the option "config_is_read_only" to true in it. See https://docs.nextcloud.com/server/25/go.php?to=admin-config Can someone guide me here ?
  5. I ran the xfs_repair with -L and got verry little files back.
  6. I will try following the video since this message is similar to the message shown in the video at: 6:56. I'll update when I have something.
  7. I runned it again without anything: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
  8. I forgot about it, there you go: arialis-mserver-diagnostics-20221211-1429.zip
  9. One of my drives died and I replaced it. The drive rebuilded completely and once it was done I got this error: (Unmountable: Wrong or no file system). I started following the spaceinvader's video and saw I had a strage report in the xfs_repair status: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. I'm not sure what I'm supposed to do at this point. Could someone guide me a little ?
×
×
  • Create New...