CyberMew
-
Posts
410 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CyberMew
-
-
I also just noticed that the logs are now 100% full and hence the logs are not showing anything, any idea how to clear it the proper way from the system? Seems like log are empty right now... Seems like something is bugged with the system
-
Ah I see.. thanks for the info! Yes I had this problem once before, long time I think. But I just went to click Container Size, and it says Total Size of 8.49GB, not 50GB though...Writeable is nan, so not sure which I should be seeing..
Also I went to Settings, Docker, I am seeing this:
btrfs filesystem show:
Label: none uuid: 82c80fd8-8bfa-4379-9cfa-37a7ca41205f Total devices 1 FS bytes used 13.34GiB devid 1 size 50.00GiB used 30.57GiB path /dev/loop2
which seems like it's not filled up yet as well. I can follow the wiki to delete and recreate but this might happen again without hitting 50GB... Any idea what is happening?
-
Not sure what is going on... quite sudden
-
On 7/31/2021 at 6:06 AM, Squid said:
There is no upgrade path. Uninstall, install v2 (which uses a tarball instead of individual files) and run a backup.
Thanks. One thing I would note is that v1 settings is not ported over so luckily I took a screenshot of existing settings beforehand. Also noticed the compression option is off by default and I have turned it on, hoping to use less space.
One more question, if I don't use unraid.net (My Servers), can I use the same destination folder for USB Backup Destination and libvirt.img Destination like how it was previously? In v1 the destination folder was the same for all and it created a folder named Community_Applications_USB_Backup and
Community_Applications_VM_XML_Backup in the e.g. CommunityApplicationsAppdataBackup/[email protected] folder.
-
I am getting this warning:
QuoteDeprecated plugin ca.backup.plgThis plugin has been deprecate and should no longer be used due to the following reason(s): While fully functional, development has ceased on this plugin and been replaced by v2. See HERE While this plugin should still be functional, it is no recommended to continue to use it.
How can I migrate over to v2 without loss to my old backups and retain the settings and still being able to be restored? What is the correct upgrade steps? I think currently the /mnt/user/appdata/ is being saved to a /mnt/user/cabackup folder, basically copied pasted the appdata folder together with some extra files and dumped into a dated folder in this cabackup i made last time.
-
Thanks! Trying it out now, the top right notifications shows this, should be ok/correct right?
Unraid Disk 7 error: 30-07-2021 09:29 PM
Warning [XXXX] - Disk 7, drive not ready, content being reconstructed
WDC_WD80EFZX-xxxx (sdj)Unraid Parity sync / Data rebuild: 30-07-2021 09:29 PM
Notice [XXXX] - Parity sync / Data rebuild started
Size: 8 TBThanks again in advance!
-
Turned off the pc, turn it on again. Became like this.. what do I do now to resolve it?
-
How do I know which version this is running?
Some trackers banned the latest R2 build for transmission due to a bug. How do I get the build before R2? Which tag should I use?
-
I see that iperf3 is 3.9, how can I get the latest 3.10.1 version?
-
Thanks. A reboot should be fine when the cache drive is detected again alright? Should I wait for the parity to complete first? I reckon it will start from zero again if I restart now
As for the invalid entry, any idea where can I find the source of it?
-
Having some errors, not sure when did the docker service failed and for how long (hope it wasn't long).
Saw the log with lots of errors, not sure what to do or what's happening.. currently the monthly parity check is running. Would appreciate any advice.
-
Thank you for the reassurance! Only seeing these yellow warnings:
Mar 22 22:19:24 Tower kernel: tsc: Fast TSC calibration failed Mar 22 22:19:24 Tower kernel: ACPI: Early table checksum verification disabled Mar 22 22:19:24 Tower kernel: pci 0000:27:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 22 22:19:24 Tower kernel: pci 0000:27:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 22 22:19:24 Tower kernel: floppy0: no floppy controllers found Mar 22 22:19:24 Tower kernel: random: 6 urandom warning(s) missed due to ratelimiting Mar 22 22:19:27 Tower rpc.statd[1933]: Failed to read /var/lib/nfs/state: SuccessBut so far so good, hope it stays that way.. thanks a lot!
-
Ok it's back after shutdown, but it is under unassigned, and if I select it as a cache drive, it says New device. Will my cache drive data still be there? How can I fix or restore it without causing further issues?
-
Seems like the cache drive is no longer detected
tower-diagnostics-20210322-2139.zip
-
Thanks, weird how it just dropped off. It didn't happened on the past few months until I updated the software and restarted the computer. Will restart and see if it makes any difference. I don't think the bios have any NVMe power states (I am using https://www.msi.com/Motherboard/support/x470-gaming-pro-carbon). Restarting now, will report back soon
-
Attached diagnostics as well.tower-diagnostics-20210322-2112.zip
-
I am seeing this on my cache drive:
Mar 21 22:26:12 Tower emhttpd: read SMART /dev/nvme0n1 Mar 21 22:52:12 Tower emhttpd: shcmd (1683): mount -t xfs -o noatime /dev/nvme0n1p1 /mnt/cache Mar 21 22:52:12 Tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem Mar 21 22:52:12 Tower kernel: XFS (nvme0n1p1): Ending clean mount Mar 22 03:01:36 Tower root: /mnt/cache: 190.3 GiB (204309774336 bytes) trimmed on /dev/nvme0n1p1 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0xf4afae0 len 32 error 5 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x2cf0d200 len 32 error 5 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x2cf8c7b0 len 8 error 5 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 42077208 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 88096136 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 809978401, offset 0, sector 754835864 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 500518589 op 0x1:(WRITE) flags 0x29800 phys_seg 1 prio class 0 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 12732352 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 256356112 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 16747910, offset 37883904, sector 42077232 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 502525672 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Mar 22 19:40:33 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): log I/O error -5 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 274737869, offset 32768, sector 256356120 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 274737869, offset 36864, sector 256356136 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 4573547, offset 24576, sector 4572576 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 4573547, offset 16384, sector 4572552 Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 4573547, offset 0, sector 4572520 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1196 of file fs/xfs/xfs_log.c. Return address = 000000007f16e358 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): Log I/O Error Detected. Shutting down filesystem Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): Please unmount the filesystem and rectify the problem(s) Mar 22 19:40:33 Tower kernel: nvme0n1p1: writeback error on inode 277207800, offset 528384, sector 258101072 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): log I/O error -5 Mar 22 19:40:33 Tower kernel: XFS (nvme0n1p1): log I/O error -5It is full of all these errors. See a
ttach screenshot.
-
Fixed after restarting the switch. It was in a stuck state. The lights weren’t moving and the lan port had no light as well. But the blue light was ready. What the heck.
-
Updated fine until 5.12.72 and shortly after updating and open the dashboard it took down the network. Completely dead. Any ideas why? Do I need to update my USG firmware in order to use the later controller version? Why can a controller update take down a network oh my goodness...
Update: turned off and on USG and now it’s blinking white light. The LAN port is still not lighted up, same as before the restart.
Update 2: steady blue light now. Still no go.
-
I just got a Unifi Flex Mini and the quick start guide says controller v5.12.5 and newer is required in order to adopt it.
I am currently on tag 5.10.26-ls32. Should I upgrade to latest of v5.10 (5.10.27-ls32) before moving to latest of v5.11 (5.11.50-ls40) and then latest of v5.12 (5.12.72-ls61), so on and so forth until v5.14 (5.14.23-ls76)?
Update: just realised 5.10.27-ls32 is not a valid one, will try the next latest version.
-
Thanks, I restarted and luckily all is working fine. I have also updated my bios for some good measure.
Just curious, is it possible for the Nvme SSD to fail? How would we find out in Unraid?
-
/bin/ls: cannot access 'user': Input/output error
/bin/ls: cannot access 'cache': Input/output error
Is this a serious problem?
-
Unfortunately no I didn’t. Right after I turned my machine off, I (iirc) updated my bios the next boot and it was back to normal. The drive was still secured so I didn’t touch it. Haven’t had this same issue since.
-
I thought that it was “disposable” and it would be great if it was in “incognito” mode everytime for just playing around. I just didn’t want the config folder to be the default folder since it isn’t multi tenant(?). I will figure out if it’s possible to change the default save directory to a folder that I will map it to. At the very least that will indicate users not to touch anything outside of my sandbox folder. Thank you both for your inputs.
Errors about BTRFS
in General Support
Posted · Edited by CyberMew
Thanks. Reboot works. No need for me to touch the docker image, it wasn't filled (30GB out of 50GB). Log usage is fine now. Not sure what was up initially that caused it to error/lock up..
Also checked the container size, and they seems ok (not sure why the docker image is 30GB though)