Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Docker image is corrupt, apparently because it ran out of space, delete and re-create.
  2. If I understand correctly it's possible, but safer to add the new device(s) and remove the old one(s).
  3. Unraid driver is crashing, this can sometimes be helped by using a different kernel, update to v6.11.0-rc3 to see if it helps.
  4. Try this: https://forums.unraid.net/topic/122185-time-machine-error-19-operation-not-supported-by-device/?do=findComment&comment=1120439
  5. Still no valid SMART, looks like a disk problem, you can ry swapping places with another disk to make sure, but doubt it will help.
  6. Check the syslog during disk mounting: reflink=1 new format, reflink=0 old format. There's only one way, empty the disk, reformat, copy the data back.
  7. Still some issues with disk9, but it mounted this time, check filesystem on the emulated disk2.
  8. Try that device with a different controller if available.
  9. Start by booting in safe mode to rule out any plugins
  10. This is usually hardware related, a BIOS update might help, as well as using other PCIe/M.2 slots if available, different kernel might also help.
  11. Before or after these last diags? It's still dropping. Also the docker image is corrupt and needs to be re-created.
  12. Power down, check/replace cables on disk9, power back up and post new diags after array start.
  13. SSD is on a different port but it dropped again: Aug 11 12:27:15 WMLUnraid kernel: ata2: COMRESET failed (errno=-16) Aug 11 12:27:15 WMLUnraid kernel: ata2: limiting SATA link speed to 3.0 Gbps Aug 11 12:27:20 WMLUnraid kernel: ata2: COMRESET failed (errno=-16) Aug 11 12:27:20 WMLUnraid kernel: ata2: reset failed, giving up Aug 11 12:27:20 WMLUnraid kernel: ata2.00: disabled
  14. Jan 11 16:15:49 Media init: Switching to runlevel: 0 Syslog shows a shutdown was initiated, this could be a button press, or a malfunctioning power button, or some other plugin/app initiating it.
  15. Aug 11 11:09:48 WMLUnraid kernel: ata1: COMRESET failed (errno=-16) Aug 11 11:09:48 WMLUnraid kernel: ata1: reset failed, giving up Aug 11 11:09:48 WMLUnraid kernel: ata1.00: disabled SSD cache dropped offline, but that's not a reason for the server crashing, still you need to fix that, check/replace cables, then enable the syslog server, start the parity sync and post that if it crashes again.
  16. It's coming from disk3: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.46-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: Unknown error Try power cycling the server (not just rebooting).
  17. Should be all fine, it means it was likely caused by some flash drive corruption.
  18. Multiple errors but they just affect one file: Aug 11 06:09:09 Tower kernel: BTRFS warning (device nvme1n1p1): checksum error at logical 658747006976 on dev /dev/nvme1n1p1, physical 395688648704, root 5, inode 482653, offset 9145081856, length 4096, links 1 (path: data/media/movies/Doctor Strange in the Multiverse of Madness (2022)/Doctor.Strange.in.the.Multiverse.of.Madness.2022.4K.HDR.DV.2160p.BDRemux Ita Eng x265-NAHOM.mkv) Delete/restore that file from backups.
  19. Edit /config/disk.cfg in the flash drive and change this line: diskFsType.2="&xfs" to diskFsType.2="xfs" Then start array.
  20. Please post new diags after array start in normal mode.
×
×
  • Create New...