sfleck

Members
  • Posts

    35
  • Joined

  • Last visited

Recent Profile Visitors

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

sfleck's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Apparently, if the server goes offline for some period of time (I think I read 5 days) the license gets suspended from the server. In any case, I had to go to the server and login and that enabled the server to reconnect the license to unraid.net All I had to do was login on the local network with the local IP of the server
  2. Recently one of my servers disappeared from my dashboard. I have the following message left in its place: 1 License Key Not Registered With Connect My Keys What's the fix? Do I have to go to the physical site and connect directly or can it be fixed remotely? thanks!
  3. i can ping domainname.com i can ping dynamic.domainname.com i can get an IP for domainname.com and dynamic.domainname.com and ping that too I cannot get to my unraid server interface or any docker interface the key is signed out ... any thoughts on why?
  4. I have a server that is a couple hundred miles away. I can see this in the Dashboard: "Signed Out Keys (Possibly available for use on other servers)." I have a Cloudflare connection and can ping the server domain name and IP address Is there a way I can remotely re-auth the key?
  5. I have a new 12TB drive I am trying to add (replace older 2TB drive) but constantly fails ebery attempt. Tried preclearing and get this: Jul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 143.094 s, 0.0 kB/sJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: dd: error reading '/dev/sdg': Input/output errorJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 147.468 s, 0.0 kB/sJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: dd: error reading '/dev/sdg': Input/output errorJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 151.842 s, 0.0 kB/sJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 151.842 s, 0.0 kB/sJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: dd: error reading '/dev/sdg': Input/output errorJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:40 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 156.215 s, 0.0 kB/sJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: dd: error reading '/dev/sdg': Input/output errorJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 160.589 s, 0.0 kB/sJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: dd: error reading '/dev/sdg': Input/output errorJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 164.987 s, 0.0 kB/sJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records inJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0+0 records outJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-Read: dd output: 0 bytes copied, 164.987 s, 0.0 kB/sJul 08 08:17:41 preclear_disk_ZRT0866X_30059: Pre-read: pre-read verification failed!Jul 08 08:17:41 preclear_disk_ZRT0866X_30059: error encountered, exiting ... #################################################################################################### # Unraid Server Preclear of disk ZRT0866X # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 5 - Pre-read verification: FAIL # # # # # # # # # # # # # # # #################################################################################################### # Cycle elapsed time: 0:13:38 | Total elapsed time: 0:13:38 # #################################################################################################### Anything else I can try to do to recover the use of the disk?
  6. I found this command to wipe the radarr.db, but what is the command to rename radarr.db to radarr.db.old ? new to linux mv /mnt/user/appdata/binhex-radarr/radarr.db radarr.db.old
  7. I did as you suggested. Drives i want to keep are now allocated and parity is rebuilt and good and all drives in the array are good. The suspect disk, 8tb seagate barracuda, had 744 reallocated sectors before the preclear and that number increased by 24 to 768 reallocated sectors. The drive has 15,830 hours on it now. Should I assume it will continue to degrade or should the fact that it successfully finished the preclear give me confidence? I bought this HDD in a lot of 4 8tb identical drives on eBay, basically paying $75 for each. Is there any point in keeping this one? Certainly don't plan to use it in the array, but can it be added somehow outside the array and used in some other capacity?
  8. Will do, thanks JorgeB. My plan is to get the data off the drive (Disk1) on to Disk2 physically remove the drive (Disk1), swap the current parity drive to the 2nd CMR drive once the data is in place (not sure how yet ... but I have 40 hours to research as data moves), then reinstall the "bad" Disk1 drive and try to preclear it to see just how bad it is. If it's really done then I will toss it.
  9. I started the process of moving the data from Drive1 to Drive2 using Unbalance Diagnostics attached scytale-diagnostics-20230109-1235.zip
  10. Can I follow this video: ... and move all the data from Disk1 to Disk2 using unbalance Then, I would need to know how to remove the Parity drive, replace it with the CMR drive and then rebuild the Parity disk
  11. Oh, and both Disk2 and Disk3 currently have NO data on them.
  12. The current Disk 1 (with errors) will not remain as Disk 1 Currently the CMR drives are Disk2 and Disk3 I would like the data on Disk1 to go to Disk2 and move Disk3 to the Parity position That would make Parity and Disk1 the CMR drives