Kilrah
Members
-
Joined
-
Last visited
Solutions
-
Kilrah's post in Moving files cache issue was marked as the answerDelete the partial file from the cache, if you're sending it through the network temporarily set the share to cache:no so it goes straight to the array. If it's being transferred on Unraid itself e.g. from an unassigned device you could write it to /mnt/user0/[share].
-
Kilrah's post in Resilio sync - full disk was marked as the answer/mnt/disk1/whatevershare is disk1 specifically, no other.
/mnt/user/whatevershare is what goes through unraid's automatic management/splitting between disks.
-
Kilrah's post in Cache drive filling up - not sure if mover is working anymore was marked as the answerIf you're still seeding them the files will be open, and the mover can't move open files. Try stopping your torrent container and running the mover manually.
-
Kilrah's post in Cant use the network file sharing to put the iso windows file for a vm was marked as the answerOn Shares/isos what did you set the sharing options to? Either you set it Public and anyone can access it, or you create a new user in unraid, set sharing to private and give read/write access to that user, then the credentials will be what you've set for that user.
-
Kilrah's post in New hardware won'[t boot off existing Unraid USB stick was marked as the answerYou likely need to enable UEFI boot on the unraid USB, I believe that just means renaming the "EFI-" folder on it to "EFI".
Could probably enable CSM in the BIOS instead.
-
Kilrah's post in [SOLVED] Parity Sync Slow was marked as the answerYour syslog is full of read errors from disk1.
Jul 30 09:39:11 URNAS01 kernel: blk_update_request: I/O error, dev sdc, sector 1088 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Jul 30 09:39:11 URNAS01 kernel: sd 3:0:0:0: [sdc] tag#294 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=5s Jul 30 09:39:11 URNAS01 kernel: sd 3:0:0:0: [sdc] tag#294 Sense Key : 0x3 [current] Jul 30 09:39:11 URNAS01 kernel: sd 3:0:0:0: [sdc] tag#294 ASC=0x11 ASCQ=0x0 Jul 30 09:39:11 URNAS01 kernel: sd 3:0:0:0: [sdc] tag#294 CDB: opcode=0x28 28 00 00 1d 2c 40 00 04 00 00 Jul 30 09:39:11 URNAS01 kernel: blk_update_request: critical medium error, dev sdc, sector 1912512 op 0x0:(READ) flags 0x0 phys_seg 48 prio class 0 Jul 30 09:39:11 URNAS01 kernel: md: disk1 read error, sector=1912448 Jul 30 09:39:11 URNAS01 kernel: md: disk1 read error, sector=1912456 Jul 30 09:39:11 URNAS01 kernel: md: disk1 read error, sector=1912464
Check connection/power/change SATA cable... What's the machine set up like?
-
Kilrah's post in Error trying to re-install a container was marked as the answerJust had a look at that particular container and it seems you simply didn't follow the instructions in the app description.
-
Kilrah's post in Ubuntu Template - no Size option for vDisk? was marked as the answerYou might already have a folder called Ubuntu with an existing vdisk in it. If that belongs to another VM you might want to change the name of this new one.
-
Kilrah's post in Mishap - Initial setup with open port 443 was marked as the answerAnd AFAIK SSL is off by default, so it's only responding on 80, not 443.
Also your forward would only have worked if your new server uses the same internal IP as the old one, don't know if it's the case.
-
Kilrah's post in Generic Cache Pools -> Disk Array -> Mover question. was marked as the answerYou set up the spin down timeout in the disk settings, if nothing accesses them they'll stop after that. My array's all in standby at the moment.
The mover... moves things, so once they're moved if they're needed the drives will have to spin up. So it seems you don't want to use the mover, just run everything off the cache and run a backup process towards the array, luckybackup can do that for you for example.