PapaThiele
-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by PapaThiele
-
-
Saw this on my unraid server tonight. I cannot get diagnostics as the image & blue text are not active URL links. The same is true for the links on the Settings , Dockers & VM's tabs. I cannot start/stop dockers or VM's. I cannot see the drives in my array nor my cache drive.
Something really wrong went on during force_update
Post the ENTIRE contents of this message in the Community Applications Support ThreadOS: 6.10.3
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
Language:<br /> <b>Warning</b>: file_put_contents(): Only 143360 of 11759627 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>94</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only 135168 of 13056563 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only -1 of 3404 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only -1 of 144723 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only -1 of 7650 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only -1 of 10664 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only 135168 of 13056563 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only 135168 of 13184766 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> <br /> <b>Warning</b>: file_put_contents(): Only -1 of 55 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>62</b><br /> {"status":"ok","script":"feedWarning('Primary Server');$('.statistics').attr('title','December 23, 2022 @ 6:04 pm');"}
-
I'm having a similar issue with this unit:
Mediasonic PROBOX 4 Bay 3.5” SATA Hard Drive Enclosure – USB 3.0 & eSATA Support 18TB HDD (HF2-SU3S3) 2022 New Chipset
* Update: I reinstalled the drives with the largest capacity in the top slot, then next largest, etc...and now it's working. I had the smallest on top the first time, just an OCD/ADHD quirk I have
-
6 hours ago, JorgeB said:
Click the minus to hide the partition, you can also set to show or hide partitions by default for each device by clicking on its settings, and next time or if you have more questions please use the existing plugin support thread.
I tried collapsing using the minus icon many times (before I posted)) but it only worked on a few of the devices,not sure why but I suspect it had something to do with the external enclosure(s).
But...the settings for each disk werked just fine for getting me that 'clean, less is more' look that I prefer. In the past I thought I had seen a UD setting that offered that for all devices but this was just as good.
I didn't think this was a plugin issue, rather I though it was "I'm too dumb/intimidated" issue on my part. I'll look for that next time I have a BTS attack.
Thanks a ton, the support here is freakin awesome and fast.
-
1
-
-
I'd like to have all my UD appear with just the single like like dev2, not multiple lines like dev3. Is that possible? I poked around the UD settings but didn't see anything that seemed to apply.
-
11 minutes ago, trurl said:
Not a great loss then
I can find "Kathy_Bates_Naked_Bubble_Bath.avi" any old place
-
4 minutes ago, trurl said:
How much data is in your lost+found share after the filesystem repair?
4.22 MB
-
I removed everything from my case, replaced any splitters & made sure everything was secure. Seems to have done the trick.
-
Dangit! It went back to:
"Unmountable disk present:
Disk 7 • WDC_WD80EMAZ-00WJTA0_2SG6B9AJ (sds)"Befotre thiss happened I notice a s#!t-ton of errors being written while the parity was rebuilding.
I have another disk pre-clearing. I'll let that finish then replace #7, or at least let it run for now. It's late & I'm too tired to try anything but if anyon leaves unstructions, I'll run through them in the mornin.
-
Awesome, it worked! All my data appears to be there...from Golden Girls to ummm, never mind.
I really appreciate the help.
-
Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 1 - agno = 3 - agno = 4 - agno = 7 - agno = 6 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:2822794) is ahead of log (1:2820534). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. -
Parity is rebuilding, disk7 is unmountable. Is that correct?
I get nervous with this...is this correct? "xfs_repair -v /dev/md7"
-
I tried reseating the power & SATA cables but now all I get for Disk 7 is
"Unmountable disk present:
Disk 7 • WDC_WD80EMAZ-00WJTA0_2SG6B9AJ (sds)" -
Thanks! I'll check that out
-
I am seeing a lot of these errors in Tools/Syslog
ata3.00: failed command: READ FPDMA QUEUED
ata3.00: exception Emask 0x10 SAct 0x3ff8 SErr 0x4090000 action 0xe frozen
I assume I have one or more bad disks -OR- bad SATA cables, or worse yet a bad mobo. Can someone tell me which drive to focus on?
If I am totally wrong, can someone point me to what the culprit is?
-
I edited my last comment to add the diags
-
No, I just started the array with the new drive & it doesn't say exactly what it is doing (rebuild or sync).
-
I found this thread, but haven't tried the suggested step "Tools, New Permission, User shares" since the rebuild is ongoing
-
Everything was working fine after the re-cabling effort. I'd been using Plex all morning.
All of a sudden my dockers stopped working (but were still showing as started in the Dockers tab). When I tried to restart them, I got an error "Execution error. Server error" and it looks like /mnt/user has no owner & no perms.
(Edited for relevance) root@unraid:~# ll /mnt d????????? ? ? ? ? ? user
Is this normal during a rebuild or parity sync? Also, how can I tell which one it is doing since the Array Operations & Dashboard tabs both show "Parity-Sync/Data-Rebuild". I thought i had seen it somewhere before, but I cannot find it now.
-
Replacing cables...started by removing everything but the power supply. Hope this solves my woes. I've got my fingers & eyes crossed. I'll let it sit idle overnight, this old dog is whooped.
If it doesn't work, is it wrong to blame my 9 year old daughter since she was helping?
Again, I feel like a dolt for the 'uncountable' confusion. I should have caught that, but was juggling chainsaws with Unraid, work & family.
-
Thanks @trurl. I'll check out the cables to start with
-
Oh geez, that went right past me...
Anyhow, the only time I saw the unmountable error was after the rebuild. It's as if it rebuilt it, then forgot it did so.
-
There was no uncountable errors at any point, that I saw. I was replacing a good drive with a new larger drive.
-
I installed a new 8TB drive to replace a 4TB drive. After pre-clearing, I added it to the array. It rebuilt the data but then would not recognize it. Now I see it in Uassigned Devices. Its showing as xfs & I can see the data that was rebuilt onto it, but it won't add to the array & the Array Operations tab it has the option to format that drive. Please help!
-
Will Unraid see external Unassigned Drives individually if the are connected through a USB Hub? Data transfer speeds aren't too important. Trying to clean up my area.
These are non-array drives, used for various tasks.
I am running Unraid Version: 6.8.3
I didn't find any threads about this issue using the 'Search' feature. If there is a similar topic, I'd appreciate the link to it.
Something really wrong went on during force_update
in Plugin System
Posted
Thanks! It was junk in /tmp. Cleaned it up and all is well