johnnie.black

Members
  • Content count

    9697
  • Joined

  • Last visited

  • Days Won

    93

johnnie.black last won the day on January 16

johnnie.black had the most liked content!

Community Reputation

733 Guru

About johnnie.black

  • Rank
    and still...

Converted

  • Gender
    Male

Recent Profile Visitors

1645 profile views
  1. newly added 4TB drive shows 4GB used, but it's empty

    Also let me add that the 2TB was probably formated with an earlier xfs version, and that's the likely reason it was emptier, xfs started using more space on newer kernels, IIRC a couple of years ago or so.
  2. newly added 4TB drive shows 4GB used, but it's empty

    Don't know, ask an xfs maintainer, it's likely some metadata reserve for filesystem housekeeping, can only tell that it's normal.
  3. newly added 4TB drive shows 4GB used, but it's empty

    If you reformat it you'll get ~2GB used
  4. newly added 4TB drive shows 4GB used, but it's empty

    It's normal for the xfs filesytem, about 1GB per TB.
  5. 6.4 - Array Starting - Starting Services (Stuck?)

    If you're willing you could try redoing your flash to make sure it's not related to your config or any customization, which IMO it's highly likely. Backup the current flash drive, create a new install on it and copy just super.dat (disk assignments) and your key from the current flash, both on the config folder, if the array starts normally you can then start reconfiguring the rest one thing at a time.
  6. Call Traces

    You currently have a BD-Drive, the new 8TB disk and an SSD, it might be OK for the BD but don't use it for any disks or SSDs.
  7. Call Traces

    Sorry, my bad for not looking at the diags more carefully before, you are using the new disk on the Marvell controller on your Asrock board, don't as they are a known problem on those boards and will keep dropping disks, never use the first 4 white SATA ports. The BD-Drive might be OK there, but best move it also just in case.
  8. 3rd time having cache drive hose up!

    SSD dropped offline, a reboot will bring it online, until the next time it drops again.
  9. Can't enable SMART on my HDD

    Likely a problem with the disk then.
  10. Call Traces

    Start the array with disk4 unassigned, stop the array, re-assign new disk to disk4 slot, start the array to begin rebuilding.
  11. 3rd time having cache drive hose up!

    These are hardware errors, SSD was disabled and the filesystem shutdown in the end, possibly a bad cable, but there's no SMART since it dropped offline: Jan 19 00:59:24 THECONSTRUCT kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 19 00:59:24 THECONSTRUCT kernel: ata1.00: failed command: FLUSH CACHE EXT Jan 19 00:59:24 THECONSTRUCT kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Jan 19 00:59:24 THECONSTRUCT kernel: res 40/00:01:00:00:00/04:00:00:00:00/e0 Emask 0x4 (timeout) Jan 19 00:59:24 THECONSTRUCT kernel: ata1.00: status: { DRDY } Jan 19 00:59:24 THECONSTRUCT kernel: ata1: hard resetting link Jan 19 00:59:29 THECONSTRUCT kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 19 00:59:34 THECONSTRUCT kernel: ata1: SRST failed (errno=-16) Jan 19 00:59:34 THECONSTRUCT kernel: ata1: hard resetting link Jan 19 00:59:39 THECONSTRUCT kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 19 00:59:44 THECONSTRUCT kernel: ata1: SRST failed (errno=-16) Jan 19 00:59:44 THECONSTRUCT kernel: ata1: hard resetting link Jan 19 00:59:49 THECONSTRUCT kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 19 01:00:19 THECONSTRUCT kernel: ata1: SRST failed (errno=-16) Jan 19 01:00:19 THECONSTRUCT kernel: ata1: limiting SATA link speed to 1.5 Gbps Jan 19 01:00:19 THECONSTRUCT kernel: ata1: hard resetting link Jan 19 01:00:24 THECONSTRUCT kernel: ata1: SRST failed (errno=-16) Jan 19 01:00:24 THECONSTRUCT kernel: ata1: reset failed, giving up Jan 19 01:00:24 THECONSTRUCT kernel: ata1.00: disabled Jan 19 01:00:24 THECONSTRUCT kernel: ata1: EH complete Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 175860562 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 175860576 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 175860584 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 175860619 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 175860622 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 05 dd d6 80 00 00 20 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 98424448 Jan 19 01:00:24 THECONSTRUCT kernel: XFS (sdb1): metadata I/O error: block 0xa7b6b12 ("xlog_iodone") error 5 numblks 64 Jan 19 01:00:24 THECONSTRUCT shfs/user: err: shfs_ftruncate: ftruncate: (5) Input/output error Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 10 44 64 98 00 00 08 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 272917656 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 10 77 e5 a8 00 00 88 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 276293032 Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536621, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536622, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536623, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536624, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 12 3c 9c c0 00 00 40 00 Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536625, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 305962176 Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536626, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 38245264, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536627, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536628, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: Buffer I/O error on dev sdb1, logical block 34536629, lost async page write Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 10 44 64 98 00 00 08 00 Jan 19 01:00:24 THECONSTRUCT kernel: blk_update_request: I/O error, dev sdb, sector 272917656 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 05 ff 92 d0 00 00 08 00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 05 ff 92 f0 00 00 08 00 Jan 19 01:00:24 THECONSTRUCT kernel: XFS (sdb1): xfs_do_force_shutdown(0x2) called from line 1200 of file fs/xfs/xfs_log.c. Return address = 0xffffffff812b4a91 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 19 01:00:24 THECONSTRUCT kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 06 0f 5a 58 00 00 08 00 Jan 19 01:00:24 THECONSTRUCT kernel: XFS (sdb1): Log I/O Error Detected. Shutting down filesystem
  12. Call Traces

    SMART for the new disk looks fine, try rebuilding again, it it fails again recommend replacing the cables to rule them out.
  13. Can't enable SMART on my HDD

    And this is someway related to unRAID? You could at least use the lounge forum. Anyway to enable SMART you just type: smartctl -s on /dev/sdX Or whatever the device is, if that isn't working you have other problems, likely with the disk.
  14. Call Traces

    The new disk dropped offline so there's no SMART, power down, check/replace cables, power back on and post new diags.
  15. Yeah, but doubt anyone will be working on that Linux driver soon, and even if you downgrade you'll likely run into issues again if you need to replace a disk with a new one.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.