Jump to content

fysmd

Members
  • Content Count

    70
  • Joined

  • Last visited

Community Reputation

0 Neutral

About fysmd

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    UK
  • AIM
    aqilarigg
  • YIM
    fysmd
  • MSN Messenger
    fysmd_uk@hotmail.com
  1. O-M-G!! I feel like a muppet. Off to get proper cables now. Thanks again!
  2. I want to say a big thank you, especially to johnnie.black for all the help with my recent issues (not only in this thread!) I worked out the source of my troubles I think and it was mainly -- >>ME<< I'm embarrassed to say that I had a compound issue: 1. Two of the five cables I bought seem incompatible, drives connected after one of these cables were not detected! 2. I'm a dick - I had knocked power off for a large number of by drives (2nd PSU!) - THINGS WORK BETTER WHEN PLUGGED IN! Now I'm over my brain fart I can start to fix properly, the cables I bought (same supplier) are: https://www.scan.co.uk/products/1m-broadcom-sff-8643-to-x4-sata-cable-mini-sas-hd-to-sata-data-port (works) and https://www.scan.co.uk/products/60cm-silverstone-12gb-minisas-hd-sff-8643-to-sata-7pinplussideband-cable (don't work) What should I be looking for vs avoid in these cables, I'm not seeing the difference
  3. I dont know what forward vs reverse breakout means.... Tried the HBA in two identical machines, same result and have now replaced the card, same result Same cables and drives though I've upgraded the firmware on the HBA, same results, no BIOS update available for MB. Could this be MB or Drive compatibility?
  4. Oh I hope not, servers been down for days already Would be just my luck though! Anybody know if there's any config I need to do to enable all ports for sata drives or anything similar?
  5. Hi all, I'm new to this card and just installed it. It seems to only detect drives connected to the first port. All four connected drives are detected but moving the same cable to other ports on the card leaves them undetected. If I run the setup tool at boot time (ctrl-c) I see the same thing, just four drives. Any tips?
  6. OK, well my new toy will be with me tomorrow so I'll take it from there. Can I just check the approach when I get the new controller, after reconnecting everything should I expect the one disabled drive to still be disabled? is there a way to force it back into life or is it safer (better) to just all it to allow the array to rebuild on the same disk again?
  7. This sounds odd to me. I do not have any stand-alone port multipliers, could they be a part of the card I'm using?? Also, I have been running this config for many years now and I have only ever had similar issues when I was mixing REISERFS and XFS, I migrated all data without issue and it's been stable since then (until now!). I have upgraded unraid - is it possible (advisable?) to downgrade back to a version which did not exhibit these errors? I have also taken the plunge and gone for one of these puppies: https://www.scan.co.uk/products/24-port-broadcom-sas-9305-24i-host-bus-adaptor-internal-12gb-s-sas-pcie-30 it's on the recommended HW list so I ought to be golden with this fella - will I?? I have another question regarding rebuilding now. I have disabled all software which might be trying to write changes to my unraid array but with one drive (allegedly) missing and and another in a very off state, how should I proceed to get back healthy? Obviously if both drive refuse to get recognised i cant rebuild the data from parity :(
  8. O-K.. I had an almost identical issue again a couple fo days ago and followed the process described above (Maintenance mode, disk checks etc, rebuild array after remounting drive and array returned to health after a parity rebuild. Today, I have the same symptoms again but with a different drive again - diag attached prior to doing anything:. I notice that two drives from my array appear in my unassigned drives section on the main screen. One of them is the drive reporting failed and the other claims to still be healthy in the array, screenshot below: Array still started but not happy at all, lots of data missing Am I doing something really wrong somewhere, been running Unraid for a very long time without issues at all, seems to be all wrong right now! Please help! server-diagnostics-20181205-2219.zip
  9. Half way through rebuilding and the contents do seem to be emulated again😄 (I was worried there!). Thank you SOOOOO much for the help, I think without this assistance I would have removed the drive from the array, rebuilt parity, mouted the drive externally and copied any working content back to the array. I had a power incident at home a couple of weeks ago, while the machine stayed up, one drive stopped working completely and I suspect another had a similar issue to this one (it mounted externally and worked, then passed a preclear without issue!) Time I think to invest in fresh batteries for the UPS which isn't on at the moment!!
  10. It just says not installed when started, unassigned when not
  11. Errr . I just clicked on disk17 in the GUI, I dont see any reference to which device it's working on..
  12. OK, did not mount when I restarted the array so ran with -L: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:138984) is ahead of log (1:2). Format log to cycle 4. done when I try to start the array again, disk17 says unassigned... I mean with the array stopped, there is no disk assignment in disk17 slot. The drive does appear in the drop down but I guess if I reassign it here it'll erase / overwrite it? Do I need to force it back into the array or something?
  13. Thank you so much for helping so quickly! 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 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 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. So, do I just mount in unassigned drives, or start the array?
  14. 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.
  15. Unraid Pro v6.6.3 - diag attached. I noticed a drive was emulated earlier today (only after the Mrs said that Plex was misbehaving! - must check my notification setting!!) The GUI says that content is emulated but actually, it's not there. The user share is available but the files which were on the faulty drive are not there. At first, navigating to the parent directory in a shell errored: an@Server:/mnt/user/TV$ cd The\ Deuce/ ian@Server:/mnt/user/TV/The Deuce$ ls -la /bin/ls: reading directory '.': Input/output error total 0 ian@Server:/mnt/user/TV/The Deuce$ So I stopped the array and restarted, now I can navigate to the directory, but not the sub directory which was mounted on the failed drive (split season directories) The faulty drive (disk17 appears in unassigned drives section now (ST3000DM001-1CH166_W1F47CAF) How should I proceed? server-diagnostics-20181201-1739.zip