mostlydave

Members
  • Posts

    268
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

mostlydave's Achievements

Contributor

Contributor (5/14)

1

Reputation

  1. Here's a current Diagnostics, I'll work on the firmware zelda-diagnostics-20211117-1919.zip
  2. I don't have a good feeling about things so far
  3. So I just powered off, reseated the Controller card, and the server rebooted without prompting to do a parity check: The array did start and seems ok, Should I start a noncorrecting parity check now?
  4. My server boots, but parity check stops progressing at random point. I have powered off and check all connections, they seem good to me. I have attached a diagnostic before starting the array and after, and current syslog. I am unable to get a diagnostic download after the parity check hangs. Please let me know if this server can be salvaged, I'm about ready to give up on it. zelda-syslog-20211117-1339.zip zelda-diagnostics-20211116-1913.zip zelda-diagnostics-20211116-1912.zip
  5. I'll give that a try, but I probably won't be able to do anything now until Sunday. Would grabbing the diagnostics before starting the array or before the freeze up occurs help?
  6. I can open all of the pages, I can even start my Plex docker, but it won't play anything and errors out when trying to browse. I can open \\zelda in file explorer in Windows and see my shares, but none of them can be opened. The parity check is still at 98.6%, it's been there for about 12 hours Should I try to cancel the parity check?
  7. I tried to get the diagnostics, but downloading never gets past here: Parity check has been stuck here for at least 2 hours: And I have this disk with a ton or errors: I do have a 6tb disk on hand I could use to replace disk 5, but I wanted to check in what the best way to proceed was before making any changes.
  8. The "Capture your log" link on this page: Need help? Read me first! - General Support - Unraid
  9. I'll check that out, The diagnostic link in the getting started post is dead, so I posted what I could find
  10. I just replaced a disk in my array and the rebuild appeared to have stopped part of the way through, but the yellow rebuild message on the web interface was gone and none of the commands in Array Operations were working for me so I did a hard reset The server rebooted okay and the new disk looked good and a parity check started last night. The parity check is currently stuck at 70.2 % with the yellow text saying a parity check is running gone again but still showing in in progress in Array operations. System log download is attached. zelda-syslog-20211111-1435.zip
  11. I'm switching from Plex to Jellyfin and everything seems to be working great except all of my art looks blurred like this, does anyone know if this is a bug or something related to the existing Plex .NFO data? Editing a movie or show and selecting new images isn't fixing the selected title either.
  12. Thanks for all of your help. I'm going to shut the server off until my new breakout cables arrive to be safe. I'll post again once it's been replaced, hopefully with some good news.
  13. zelda-diagnostics-20210417-2241.zip Here is my current diags, should I run something with the -b option? I have ordered a new set of breakout cables and it this point just want to salvage as much data as possible.
  14. I ran the --rebuild-tree option this morning with this output: reiserfsck 3.6.27 ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ************************************************************* Will rebuild the filesystem (/dev/md2) tree Will put log info to 'stdout' Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Sat Apr 17 07:29:40 2021 ########### Pass 0: Loading on-disk bitmap .. ok, 1232478446 blocks marked used Skipping 52923 blocks (super block, journal, bitmaps) 1232425523 blocks will be read 0%....20%. The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (344162632): (Input/output error).
  15. I have an unmountable disk I ran a check on with the following results: reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' ########### reiserfsck --check started at Fri Apr 16 16:36:26 2021 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) I have attached my diagnostic as well I unfortunately also have a red x on my parity drive, I'm afraid I'm going to lose all of my data and would appreciate any help. zelda-diagnostics-20210416-1714.zip