JorgeB

Moderators
  • Posts

    42701
  • Joined

  • Last visited

  • Days Won

    508

JorgeB last won the day on December 8

JorgeB had the most liked content!

Retained

  • Member Title
    On vacation, back in a week or so

Converted

  • Gender
    Male

Recent Profile Visitors

25692 profile views

JorgeB's Achievements

Grand Master

Grand Master (14/14)

5.3k

Reputation

804

Community Answers

  1. There's no GUI option for that, you could gave a script doing a remount.
  2. Don't follow, if the 2TB drive is disabled you can't read or write to it with another missing drive and single parity.
  3. In that case recommend using a different bay to rule that out.
  4. It doesn't usually crash because that, but looks like it did here, still first thing to do is to fix the hardware problem.
  5. Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 Sense Key : 0x5 [current] Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 ASC=0x21 ASCQ=0x0 Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 CDB: opcode=0x28 28 00 7a 11 ff ff 00 00 01 00 Dec 8 15:29:48 Tower kernel: blk_update_request: critical target error, dev sdg, sector 16383999992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Dec 8 15:29:48 Tower root: Warning! Read error 5; strange behavior now likely! Dec 8 15:29:48 Tower root: #007Caution: invalid backup GPT header, but valid main header; regenerating Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 Sense Key : 0x5 [current] Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 ASC=0x21 ASCQ=0x0 Dec 8 15:29:48 Tower kernel: sd 10:0:0:0: [sdg] tag#0 CDB: opcode=0x28 28 00 7a 11 ff ff 00 00 01 00 Dec 8 15:29:48 Tower kernel: blk_update_request: critical target error, dev sdg, sector 16383999992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Dec 8 15:29:48 Tower kernel: Buffer I/O error on dev sdg, logical block 2047999999, async page read This is hardware problem, but since there's no SMART report because of the USB bridge can't tell you if it's the disk or the USB bridge, note that we don't recommended USB for array/pool devices.
  6. Look for an LSI 9201-16i, 9305-16i, 9305-24i, though not sure you'll be able to find them for under £100, a 2 port HBA with a SAS expander can also be an option.
  7. Performance has been similar for all v6.11.x releases, they all use Samba 4.7.x
  8. Unfortunately that doesn't really matter, parity is not valid without it, because assuming there was data there at some point in the past the drive will never be 100% cleared (all zeros).
  9. Check filesystem on disk2, as for the missing cache device check/replace cables, it's not being detected, this is a hardware issue.
  10. Sorry, don't know, but there would be a much bigger chance of data recovery, at a price of course.
  11. If the errors started after the 8TB mark it's an old bug, though it's a pesky one because it only happens sometimes, nothing to worry about, just let it correct.
  12. Sorry for the typo, if that doesn't work the filesystem is likely beyond repair, that transid verify failed error is fatal, it means some writes were lost, it can happen if a storage device lies about flushing it's write cache, most often caused by bad drive (or controller) firmware. Second option in the rescue options, btrfs restore, is usually the best for this, but if you've already tried that and it didn't work not much more you can do other then reformatting the pool and restoring from backups.
  13. That's what I see in that log, then btrfs crashed.