nia
-
Posts
252 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by nia
-
-
I just moved my array of 16 disks from using reverse breakout cables directly to disks over to a 24 bay InterTech server cabinet https://www.inter-tech.de/productdetails-142/4U-4424_EN.html with a SAS backplane for each row, and connection to four rows with 8087 SAS cables to the backplane from my two IBM M1015 flashed to LSI9211-8i IT mode (running on an Asus X99-WS/IPMI).
Migration was completely transparent, unRAID automatically found all the drives, and booted as if nothing had happened, except the disks didn't spin down.
I quickly found this plugin, installed it, and voilá - spin down working flawlessly!
So this post just to confirm my configuration is working with the plugin, and first and foremost a big thank you for building and maintaining this @doron 👍😃
-
1
-
-
2 hours ago, wayner said:
I am on my way to 6.5.55. Just upgraded from 5.12.72 to 5.14.23. Everything looks good. My old UAPs now have an EOL indication beside them (see below) - this was not present in 5.12. I will let it run for a bit and then upgrade to 6.55.
Just remember to do the final updates to the UAP's before you go too far down the upgrade road (if you have not done so already)
-
23 hours ago, wayner said:
@nia How do you find 6.5.55? Any issues? Or is it too soon to tell
Soon-ish, but so far no issues at all (that I have noticed)
-
I was sitting fine on 5.10.14 for a looong time😴, but now wanted to upgrade, due to a U6 LR AP I finally will mount, the log4j-bug and also I have to install a new site at some friends house, and they will have a version 6 controller (on a RPi), so I have to look a little ahead into version 6 🧐.
Anyway - earlier in the thread, positive confirmations was sought for, so just for reference for anyone else coming from old v5.x-versions, I successfully upgraded in two steps.
The path I took was: 5.10.14 --> 5.14.23-ls76 --> 6.5.55. No issues whatsoever. 😃
Also, I will just mention, that my old EOL'ed UAPv2 (used for improved outdoor coverage) still works - I updated to the last ever firmware for it just before upgrading the controller. It works as before, just has a little yellow warning sign next to it indicating that its EOL.
Next step will be to install the U6 LR, that I have had laying for far too long 😏
For reference, my UniFi equip list: USG, US-8-150W, US-8-60W, US8, 2*UAP-AC-LR, UAPv2.
-
Reporting 2.27TB be moved from a 2TB drive with 162GB free???
I have one ReiserFS disk left in my system, that I would like to empty and convert to XFS.
However, after planning, the Plan says it will move 2.27TB from a 2TB drive with only 1.84TB data.
Also - in the GUI it suggests 2.27TB, in the log 2.11TB
Does this mean, that some files on that disk are corrupt in some way (I would assume yes)?
Any suggestions for how to proceed?
Thanks in advance for input.
-
I made a very similar mistake - or at least ended up with the same issue😖
However - the procedure above with
btrfs-select-super -s 1 /dev/sdX1 and btrfs-select-super -s 1 /dev/sdY1saved me 😅
Thank you so much @Robb3rt for posting here 👌🤘
-
I have a similar issue - any solution yet?
-
Regarding anniversaries: Later this year I will have the big 10 year anniversary with unRAID 😎. Through all these years, unRAID has always had my back.
Just now, I'm in the process of finally leaving my old setup with unRAID running in a vSphere VM alongside other Windows VM's, and in stead let unRAID be the host. I think it will be better that way 🙂 It would for that reason be ever the more appropriate with a sticker for my server 😏
Anyway - keep up the excellent work guys - Happy Birthday!
/Niels
-
1
-
-
I modified the Wiki to reflect the change 🙂
-
1
-
-
Thanks @bonienl- that was what I thought 😅 Just wanted to make sure. 😊
-
Hi.
I'm trying to move to XFS from ReiserFS, but I've run into an issue.
I'm following the steps in https://wiki.unraid.net/File_System_Conversion but I'm stuck in step 11.
It says:
Click on Tools, then New Config, then Retain current configuration:, then select All, then check Yes I want to do this, click Apply then Done
But in my "New Config" page I only have the option "Preserve current assignments".
Is the documentation not valid for my version 6.6.6? Is the effect the same, just in a new wording in the UI (I suspect this is the case)
Thanks for any input - I'm not comfortable continuing unless I get a confirmation in here :-}
-
@trurl You are right - I was not thinking it all the way through, sorry...
Now - thinking a bit more carefully, I still think I can find a way.
Adding a 4TB to replace the 2TB will add 2 TB free space.
- The data from the next 2TB can be copied to the free space on the 4TB,
- while the old 2TB disk (the one that was replaced by the 4TB) is formatted to XFS.
- Then I can remove the disk that has been copied to the 4TB from the array.
- Restart the array
- Then I can add the XFS-formatted disk, so now I have another 2TB of free space.
- I can then copy data from the NEXT ReiserFS-formatted 2TB (or 1TB) disk to the 'blank' XFS-disk just added to the array,
- while formatting the disk that was removed to XFS.
-
Then [Repeat from 3].
It should work. BUT - the question is: Is it worth all of this effort (including constantly adapting the config of the Shares) just to go to XFS?
I mean - ReiserFS has been doing the job well for a long time for many?
-
@trurl I found a place that can ship so I have a 4TB tomorrow.
Then it can run Preclear for the 24 hours or so that it takes(?), I can then swap it in to the old 2TB slot and rebuild on XFS in stead. I guess the risk profile of running with a emulated disk but the data safe on the physical one for a couple of days extra is lower than trying to rebuild, right?
Afterwards, I can start updating other disks to XFS on a 'rotational pattern' having an extra 2TB disk for the purpose I guess
(except for the three of four 4TB on ReiserFS 
) ...
-
-
Thanks or the quick answers guys!
@trurl I appreciate the thinking about the safest approach. I don't have a spare at hand unfortunately - only 1TB's. I think I will put it back into service again, as it was apparently a cable issue, and SMART looks OK (it would take 2-3 days before a spare can arrive, and I think I would rather replace other drives first).
@johnnie.black Regarding updating the filesystem. Can I do that on the current 2TB disk before re-creating the data on it - i.e. get XFS on it?
-
I stopped the server, massaged the cables, and the disk is back again
- but still with a red X in the UI, so the data is still Emulated. 
I can see, that only 9,03MB is free on the disk (ReiserFS).
Could that be contributing to the issue (if only a few sectors are failing, then there's nowhere to put the data i guess?)
Anyway, the SMART log is attached. One thing makes me think it should be replaced soon anyway - it's been powered on for 68595 hours (7y, 9m, 26d, 3h) !
Back to the current issue though. How can it get back into operation again. Would it help/do I need to delete some files from the emulated disk?
Thanks in advance for your input...
-
Hi.
A disk suddenly appears to be disabled. There has been no physical interaction with the server for a long time. I just recently upgraded unRAID to the latest version, and only afterwards discovered that Zerons OpenVMTools is no longer updated and compatible. I run on ESXi 6.0, but I don't think that has any influence on my issue.
Can anyone tell from the attached diagnostics (current logfile where the disk was disabled), if I need to replace the disk? Or should/can I do something else to bring it back online?
I think the interesting sequence in the log is the part that looks like this:
(---snip---)
Feb 19 11:02:02 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 Sense Key : 0x2 [current] Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 ASC=0x4 ASCQ=0x0 Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 43 07 28 90 00 00 08 00 Feb 19 11:02:02 Tower kernel: print_req_error: I/O error, dev sde, sector 1124542608 Feb 19 11:02:02 Tower kernel: md: disk9 read error, sector=1124542544 Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 Sense Key : 0x2 [current] Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 ASC=0x4 ASCQ=0x0 Feb 19 11:02:02 Tower kernel: sd 4:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 09 97 54 d8 00 00 08 00 Feb 19 11:02:02 Tower kernel: print_req_error: I/O error, dev sde, sector 160912600 Feb 19 11:02:02 Tower kernel: md: disk9 read error, sector=160912536 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 Sense Key : 0x2 [current] Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 ASC=0x4 ASCQ=0x0 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 CDB: opcode=0x2a 2a 00 43 07 28 90 00 00 08 00 Feb 19 11:02:10 Tower kernel: print_req_error: I/O error, dev sde, sector 1124542608 Feb 19 11:02:10 Tower kernel: md: disk9 write error, sector=1124542544 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 Sense Key : 0x2 [current] Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 ASC=0x4 ASCQ=0x0 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#2 CDB: opcode=0x28 28 00 2d 65 ba d0 00 00 08 00 Feb 19 11:02:10 Tower kernel: print_req_error: I/O error, dev sde, sector 761641680 Feb 19 11:02:10 Tower kernel: md: disk9 read error, sector=761641616 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#0 Sense Key : 0x2 [current] Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#0 ASC=0x4 ASCQ=0x0 Feb 19 11:02:10 Tower kernel: sd 4:0:0:0: [sde] tag#0 CDB: opcode=0x2a 2a 00 09 97 54 d8 00 00 08 00 Feb 19 11:02:10 Tower kernel: print_req_error: I/O error, dev sde, sector 160912600 Feb 19 11:02:10 Tower kernel: md: disk9 write error, sector=160912536 Feb 19 11:02:11 Tower kernel: sd 4:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 19 11:02:11 Tower kernel: sd 4:0:0:0: [sde] tag#0 Sense Key : 0x2 [current] Feb 19 11:02:11 Tower kernel: sd 4:0:0:0: [sde] tag#0 ASC=0x4 ASCQ=0x0 Feb 19 11:02:11 Tower kernel: sd 4:0:0:0: [sde] tag#0 CDB: opcode=0x2a 2a 00 2d 65 ba d0 00 00 08 00 Feb 19 11:02:11 Tower kernel: print_req_error: I/O error, dev sde, sector 761641680 Feb 19 11:02:11 Tower kernel: md: disk9 write error, sector=761641616 Feb 19 11:02:39 Tower kernel: sd 4:0:0:0: device_block, handle(0x000e) Feb 19 11:02:41 Tower kernel: sd 4:0:0:0: device_unblock and setting to running, handle(0x000e) Feb 19 11:02:41 Tower kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache Feb 19 11:02:41 Tower kernel: sd 4:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
(---snip---)
Any input appreciated :-)
-
1 hour ago, Squid said:
Your flash drive is dropping offline which plays havoc with the system when you change a setting, install an app, reboot, etc. Try a different USB controller
Thanks for the suggestion and fast response :-) (PS: Also just just discovered and installed your Ransomware Protection - thanks!)
According to your suggestion, I changed passthrough to one of the USB headers on the motherboard (connected to a USB bracket I had lying around) and mapped that through. Also in earlier I tried changing to FreeBSD64 bit in stead od 32 bit as someone in a different thread suggested. Unfortunately, the resets remain, and probably at some point the USB key will drop off again. BTW i have also tried mapping a second USB port through (another suggested fix) to no avail. This is an ongoing unRAID on ESXi issue, and unfortunately these suggestions did not solve it.
Also - this discussion is drifting off-topic fast, so to address the issue at hand in this thread, I have uninstalled preclear script, so the blocking pop-up should not pop up later if/when the USB key drops off again. Let's see how that pans out...
-
I'm starting to see the same behaviour - also on ESXi (version 6.0.0).
Could it be that the passthrough of the USB is not quite stable, and this triggers this?
Also - my syslog has this pattern repeating quickly filling the 3 generations saved in /var/log folder.
Please note: /boot folder is empty when looking at it from console login.
May 13 04:40:01 Tower liblogging-stdlog: [origin software="rsyslogd" swVersion="8.23.0" x-pid="1779" x-info="http://www.rsyslog.com"] rsyslogd was HUPed May 13 04:40:01 Tower root: May 13 04:40:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:40:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:40:01 Tower root: May 13 04:40:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:40:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:40:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:40:55 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci May 13 04:40:55 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) May 13 04:40:55 Tower kernel: sdr: sdr1 May 13 04:41:01 Tower root: May 13 04:41:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:41:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:41:01 Tower root: May 13 04:41:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:41:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:41:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:42:01 Tower root: May 13 04:42:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:42:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:42:01 Tower root: May 13 04:42:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:42:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:42:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:42:59 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci May 13 04:42:59 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) May 13 04:42:59 Tower kernel: sdr: sdr1 May 13 04:43:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:43:01 Tower root: May 13 04:43:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:43:01 Tower root: May 13 04:43:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:43:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:43:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:43:53 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci May 13 04:43:53 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) May 13 04:43:53 Tower kernel: sdr: sdr1 May 13 04:44:01 Tower root: May 13 04:44:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:44:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:44:01 Tower root: May 13 04:44:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:44:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:44:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:45:01 Tower root: May 13 04:45:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:45:01 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:45:01 Tower root: May 13 04:45:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:45:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:45:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:46:02 Tower root: May 13 04:46:02 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:46:02 Tower kernel: fat__get_entry: 86 callbacks suppressed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:46:02 Tower root: May 13 04:46:02 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:46:02 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:46:02 Tower kernel: floppy: error -5 while reading block 0 May 13 04:46:15 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci May 13 04:46:15 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) May 13 04:46:15 Tower kernel: sdr: sdr1 May 13 04:46:16 Tower kernel: fat__get_entry: 54 callbacks suppressed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:47:01 Tower kernel: fat__get_entry: 22 callbacks suppressed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed May 13 04:47:01 Tower root: May 13 04:47:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 May 13 04:47:01 Tower root: May 13 04:47:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 May 13 04:47:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0 May 13 04:47:01 Tower kernel: floppy: error -5 while reading block 0 May 13 04:47:15 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci May 13 04:47:15 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) May 13 04:47:15 Tower kernel: sdr: sdr1 May 13 04:47:16 Tower kernel: fat__get_entry: 54 callbacks suppressed May 13 04:47:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed May 13 04:47:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed -
Download starts but stops as nothing gets written to disk
Hi.
Feels like I'm so close - but yet so far away
I have the app running,
- VPN works, I can see it on CheckMyTorrent both with VPN turned on and off
- When I start, I get connections to many peers, but they soon die out - I assume because nothing gets written
- After each recent attempt to change the configuration, I have tried to add a fresh torrent to ensure nothing old was in play
To me it looked a lot like a permission issue, so I have tried moving the download location multiple times - even creating a special folder for it. All for locations with permissions "Public". Still no result.
Log and config attached. What to do next?
Thanks for any input - I'm sure it's a simple thing...
- VPN works, I can see it on CheckMyTorrent both with VPN turned on and off
-
Hi.
In the posts here, it appears as if there is an issue with native mSATA. Could it be related (even though my mSATA is 'behind' a SATA adapter), or is my problem a more simple issue?
Any thoughts, anyone?
/NiA
-
Hi trurl.
Thanks for responding.
It has already been formatted by unRAID from the start, and was working fine - this is a condition that has happened approx. one month after it got mounted to start with.
-
Web-UI reporting unmountable.
-
Then it can run Preclear for the 24 hours or so that it takes(?), I can then swap it in to the old 2TB slot and rebuild on XFS in stead. I guess the risk profile of running with a emulated disk but the data safe on the physical one for a couple of days extra is lower than trying to rebuild, right?
(except for the three of four 4TB on ReiserFS 
) ...
Could that be contributing to the issue (if only a few sectors are failing, then there's nowhere to put the data i guess?)
[Support] Linuxserver.io - Unifi-Controller
in Docker Containers
Posted
I have an AP-LR and I'm on 7.2.95 with no issues. The AP-LR won't update anymoe, but you can IMO safely upgrade the rest of your equipment. I have for many many versions with no issue.
There is a few things you can't do as long as you have the old AP, like e.g. assign devices to a specific AP, but otherwise you are fine. No reason to downgrade at all.