iilied

Members
  • Posts

    70
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

iilied's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. been getting these errors since the last update. not exactly sure what is causing.
  2. in short, one of the array disks (disk6) is about to fail, and got a new replacement (4tb) ready for it. also, i‘ve another new 4tb that i‘d use to replace the current parity (2tb), allowing the newly replaced disk6 to operate at full capacity. but, how would i go about using the current parity drive to replace disk6? is adding a second parity first (4tb) then taking the current parity out and use it to replace disk6 considered safe? this is for the sake of adding the extra (4tb) as a newly drive to the array.
  3. server has been running for 88 days w/o issues (version 6.8.3), but all of a sudden now it lists “not available” in the docker containers tap. tried forcing update on multiple containers, and stoping and starting the array, to no avail. first time facing this issue and not quite sure a restart would fix this, or where to start. tower-diagnostics-20210514-0713.zip
  4. tried this, unfortunately didn’t work. don’t know where to start to solve this.
  5. I am not getting a handshake from WireGuard client on macOS. Used to be able to connect no problem, is there a common issue occurring atm after the latest client update? Edit: Regenerated keys and tried to reconnect, still same issue. Able to connect, no data, no handshake. No idea what to do next. Used to work smoothly, unfortunately, not anymore.
  6. that was very stupid of me, did not notice that the same diags were uploaded. my bad. attached are the one that was supposed to be uploaded in the previous post, and another latest one.
  7. the server was shut down and the connections were checked again, they are good. powered back the server again, but the disk is still disabled and did not start the array yet. should i start the array and see what happens or what exactly to do here?
  8. all connections look good, the udma crc errors are old and the cables have been changed since then.
  9. Hello, Server was scheduled today for parity check, and from what is shown the check did not finish as disk 2 had read errors then was disabled. First time having a disabled disk, not sure what is the next step. Thank you and appreciate the help
  10. it’s an external drive connected through the back-port usb directly. used as time machine backup, using spaceoneinvader method. i rarely disconnect it, so usually is it connected all the time.
  11. it happened again. disconnected and reconnected, and another letter assigned is assigned, that’s very strange. Jul 28 03:20:46 Tower unassigned.devices: Adding disk '/dev/sdm1'... Jul 28 03:20:46 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdm1' '/mnt/disks/ST9500325AS_6VE5Z84R' Jul 28 03:20:46 Tower kernel: XFS (sdm1): Filesystem has duplicate UUID c0baa833-15ad-41c1-b008-93d89164b138 - can't mount Jul 28 03:20:46 Tower unassigned.devices: Mount of '/dev/sdm1' failed. Error message: mount: /mnt/disks/ST9500325AS_6VE5Z84R: wrong fs type, bad option, bad superblock on /dev/sdm1, missing codepage or helper program, or other error. and it doesn’t unmount. Jul 28 03:36:53 Tower unassigned.devices: Issue spin down timer for device '/dev/sdm'. Jul 28 03:36:53 Tower unassigned.devices: Unmounting '/dev/sdm1'... Jul 28 03:36:53 Tower unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdm1' 2>&1 Jul 28 03:36:53 Tower unassigned.devices: Unmount of '/dev/sdm1' failed. Error message: umount: /mnt/disks/ST9500325AS_6VE5Z84R: target is busy. now this too. Jul 28 10:54:58 Tower unassigned.devices: Adding disk '/dev/sdn1'... Jul 28 10:54:58 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdn1' '/mnt/disks/ST9500325AS_6VE5Z84R' Jul 28 10:54:58 Tower kernel: XFS (sdn1): Filesystem has duplicate UUID 82f7e126-d6cb-4146-a545-0c51fbe8f1fa - can't mount Jul 28 10:54:58 Tower unassigned.devices: Mount of '/dev/sdn1' failed. Error message: mount: /mnt/disks/ST9500325AS_6VE5Z84R: wrong fs type, bad option, bad superblock on /dev/sdn1, missing codepage or helper program, or other error.
  12. I’m having the same issue, Jul 27 09:46:19 Tower unassigned.devices: Adding disk '/dev/sdl1'... Jul 27 09:46:19 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdl1' '/mnt/disks/ST9500325AS_6VE5Z84R' Jul 27 09:46:19 Tower kernel: XFS (sdl1): Filesystem has duplicate UUID 20345907-1be5-47e5-9722-00ca8c644885 - can't mount Jul 27 09:46:20 Tower unassigned.devices: Mount of '/dev/sdl1' failed. Error message: mount: /mnt/disks/ST9500325AS_6VE5Z84R: wrong fs type, bad option, bad superblock on /dev/sdl1, missing codepage or helper program, or other error. Jul 27 09:46:20 Tower unassigned.devices: Partition 'ST9500325AS_6VE5Z84R' could not be mounted. Jul 27 09:47:36 Tower unassigned.devices: Changing disk '/dev/sdl1' UUID. Result: 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_admin. If you are unable to mount the filesystem, then use the xfs_repair -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. drive was working perfectly before. no idea what to do next. could anyone offer their help, please? edit: ran xfs_repair -L then xfs_admin -U generate and all is good.