-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Cornbreadman
-
-
Looking good. Had to rebuild the one drive that had issues and ran into nothing during the 36 hours it took. Rebooted and logs look clear to me.
Which means sometime this weekend the tower will burst into glorious flames, because...........why not?
Anyway I appreciate the experienced eyes and knowledge in pointing me to the issue. I do think one of my power cables is bad. One of the hard drives I had outside the cages wasn't powering on when using it after putting everything back together. Redid all the cabling and everything working now.-
1
-
-
1 hour ago, JorgeB said:
There are what look like power/connections issues with disk5, replace cables and post new diags after starting a new parity check.
Thank you. I suspected power or some type of connection issue. I use 2 sets of drive cages, and every little thing that has been happening the past couple weeks has been associated with drives in the top cage. I took out all the drives, disconnected all the cabling and then hooked everything up outside the cage. And alot less red in my boot up.
If its power or cable issues, I can start playing around and narrowing it down what and where. Just wanted to rule out other things first. -
In the last week I have been having some issues with my server. Out of nowhere the system will just hang. All dockers become unresponsive, cannot reach the server though any WebGUI or via Putty. Single power button push appears to not do anything and a forced shutdown is the only option.
Now I have done it back to back days. Yesterday when it rebooted I had a file system error, that I was able to recover from via google searches and repair. Today I woke up to the same frozen server. I have rebooted and no obvious drive issues listed on main page, but in the logs I am getting errors. It looks like (sde) drive could have something going on with it. But I am not sure how to read the logs to know exactly the cause, or what to start ruling out.
Its running a parity check now, VERY slowly (4.3 mb/sec) which will never finish. But I am hesitant to cancel because I did yesterday and this is obviously something failing/failed that needs to be addressed.
Before I start pulling things apart, wanted to see if someone more versed in reading the logs could point me in a direction.
Appreciate any help. -
Ok I can mount the drive again, and I can see the data on shared windows. Now I need to get it saved somewhere!!!!
Holy crap. Fingers crossed here.
I hope this works. Thank you so much! -
root@Matrix:~# xfs_repair /dev/sdk1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_icount 0, counted 570016 sb_ifree 0, counted 126 sb_fdblocks 122036997, counted 47513804 - 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 = 3 - agno = 2 - agno = 1 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... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=<value>,swidth=<value> if necessary done
-
Just now, JorgeB said:
You can try something like UFS explorer, but btrfs not finding a backup superblock suggests the device was fully trimmed, and in that case those programs will also be unable to find anything.
Okay I am trying that now. Sorry for asking questions. As mentioned I am a linux moron. How about XFS? The new cache was installed as that file system and was what I thought screwed something up with the old one, changing the file system. Could it have been changed? Not even sure that is possible.
I know atleast enough to know it wouldnt be usable if the FS was changed, but thought maybe data recovery would work.
I am just grasping at this point. I feel defeated and dont even know where to start rebuilding docker. -
5 minutes ago, JorgeB said:
If the previous cache was really btrfs looks like the device was fully trimmed, so IMHO not much you can do now.
No way to get the files anymore. Was thinking maybe some file recovery software out there. Not sure if you would know that answer.
-
No valid Btrfs found on /dev/sdk1 ERROR: open ctree failed -
WDC_WDS500G2B0A_201681482904 - 500 GB (sdk)
-
12 minutes ago, JorgeB said:
Connect the drive to the main server and post diags and the output of:
btrfs fi showNothing happens at all.
-
Had some issues with server a week ago. So had to rebuild entire plex libary and had to built new parity. To put it lightly, I am done.
Anyway, while waiting for all this to happen, I have been reading up on Cache drives and what not. Decided now would be a good time to add a NVME drive to put my plex data on only. Currently have appdata and system files on cache.
Tonight final step finished, I installed the new NVME drive, assigned it to the Cache, and in doing so, forgot to backup the current cache at all. Started it all up and then I knew.....I just f*cked up.
Unmountable - No Pool UUID
Anyway, all jacked up as I just changed the cache drive to cache pool using a XFS system where the old system was btrfs.
Tried moving the caches around and can get:
Unmountable - Wrong or no file system on the old cache drive. But nothing more.
I have a test unraid server, that I popped the old cache in and was able to mount it as Unassigned Device. I can see all the files and access them. Was going to copy them somewhere and then just format and copy back, but its going to take over a day, and I am not even sure if that works that way with the cache drive?
Before I start that process, just wanted to ask is there anyway to restore the file system? I tried some stuff listed in the FAW and keep getting error messages, so no luck there.
I suck at anything non windows to be honest, and rely on just following instructions for Unraid, so on the fly "trying" things is not good for me, as I probably have no idea what any of it means.
Is it time for me to start screaming yet? I want to scream. Ugh, been trying to fix the server in general for a week and thought I was minutes away from back up and running.
Update: after trying some of the stuff in FAQ, I now cant get the drive to mount in Unassigned Drives, so thats great. Option is just greyed out. -
[Support] xthursdayx - YACReaderLibraryServer
in Docker Containers
Posted
I seem to be having issues getting this program to update my library.
I installed the docker from official repo, set it all up and created the library without issue. WebUI shows I have a "comics" library, however when I click on it, it just reloads the page. When I am in CLI and I use the command to update the library it just says processing and quickly changes back to prompt but nothing happens/processes. No comics are added. In the mapped folder I have almost 1TB of comics. I have tried in other sub folders, and just loose in the mapped directory. None are being loaded in.
I even went and put full access permissions on the app and folders to try and see if it was a permission issue, but nothing changed.
Saw on the forums and reddit the dev preferred Unraid support in this thread.
I normally would just move on and chalk it up to user error, but I had already paid to download the iOS app, so wanted to get it up and running if possible.