coupas

I can confirm it is working now. For some reason it didnt look like there was an update. But there was. All is well now. Thanks again for your work.

How can I test it? I'm just using your template and just updates that when it gets updated.. no update so far. And the problem is still there as of now though.

Thanks a lot. It seem to be getting fixed in a coming update of the docker template. https://github.com/benbusby/whoogle-search/pull/320

Dear Whoogle, Thanks for this glorious piece of docker. It's a wonderful tool. However, I can no longer get it to work. Everytime I try and search I keep getting hit by google wanting me to accept cookies. And no matter what I choose.. I keep getting the same page. I can not get past it. So atm I am using google.com. The horror. Please advise.

Thanks alot guys. I have ordered some new disks. I will replace it! Thanks for your time and knowledge. Much appreciated!

Yes, I understand that Unraid thinks that. I was hoping the disc might be ok, and that someone could interpret SMART and/or syslog to tell me if they can see that the disc has a chance of glorius return. Or scrap. But thanks for the reply! Still undecided on the movie.

Hi there community, I've had my server since 2011, pro user. It's been working great ever since. I have had nearly zero problems since the beginning, and my latest reboot is 318 days ago. I ran into some issues with me being greedy and thought I could run too many VM's and Dockers. I simply ran out of memory. And some of my VM's simply went down. When I tried to rectify the problem I got som write errors on of the discs. And eventually it got disabled. Now. Was the problem caused because of my greed or is the disc a goner? Please advise if you have the time and knowledge. PS. I have a lady friend coming over this weekend and I promised her we'd watch some movies... so I hope you understand that I need this taken care of asap. Thanks in advance fellow unraid user. WDC_WD40EFRX-68WT0N0_WD-WCC4E6ZPE8H2-20210217-2013 disk13 (sdt) - DISK_DSBL.txt syslog.txt

This was a case of pebkac. One of my disks were full. And I had something configured wrong. This is solved. Any admin can feel free to delete the thread.

Dear community, I am running various vm´s via UnRaid and now one of them is giving me some trouble. This is an Ubuntu headless server and is pretty much only running Nextcloud. It boots. But halts, and goes to pause after a while. "fsck not present, so skipping root file system" seem to be the culprit.. but I am not sure. I changed the boot order and booted gparted. But it freezes when I try to use the check command on the boot partition. I took a screenshot from the ubuntu-boot view, where it halts. And I attached the unraid diagnostics. Please advice, what should I do next? tower-diagnostics-20200703-1944.zip edit: cool, looked at my profile, it´s more then 9 years since i registered here.. been a long time user.

Hi there, I am a long time user of unraid, and everything have worked like a charm from day 1 many years ago. But now I see in the log that the USB is about to go broken. What are my steps to resolve? Thanks in advance for any help you smart people can give me! May 4 04:40:59 Tower kernel: blk_update_request: critical medium error, dev sdq, sector 104 May 4 04:40:59 Tower kernel: Buffer I/O error on dev sdq, logical block 13, async page read May 4 04:41:35 Tower kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 Sense Key : 0x3 [current] May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 ASC=0x11 ASCQ=0x0 May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 May 4 04:41:35 Tower kernel: blk_update_request: critical medium error, dev sdq, sector 0 May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 Sense Key : 0x3 [current] May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 ASC=0x11 ASCQ=0x0 May 4 04:41:35 Tower kernel: sd 3:0:0:0: [sdq] tag#0 CDB: opcode=0x28 28 00 00 00 00 08 00 00 08 00 May 4 04:41:35 Tower kernel: blk_update_request: critical medium error, dev sdq, sector 8 May 4 04:41:36 Tower kernel: sd 3:0:0:0: [sdq] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 4 04:41:36 Tower kernel: sd 3:0:0:0: [sdq] tag#0 Sense Key : 0x3 [current] May 4 04:41:36 Tower kernel: sd 3:0:0:0: [sdq] tag#0 ASC=0x11 ASCQ=0x0 May 4 04:41:36 Tower kernel: sd 3:0:0:0: [sdq] tag#0 CDB: opcode=0x28 28 00 00 00 00 18 00 00 08 00 May 4 04:41:36 Tower kernel: blk_update_request: critical medium error, dev sdq, sector 24 sdq is the usb. I am running Unraid 6.3.2, I havn't updated yet as I don't want to reboot. Right now I have full functionality. Unraid runs in a virtual machine, started by plop kexec. Do you need any more information? Diagnostics are attached, Please help! Coupas. tower-diagnostics-20170506-1332.zip

I had this exact problem and you need to edit 2 files: ui.info is the first file. Replace that IP in there with: 172.17.42.1 the other file is: my.service.xml , in there you need to replace 127.x.x.x with 0.0.0.0 Not sure why it works, but it did for me.

I just wanted to say thanks to everyone that contributed in the thread. I am now up and running with this. I would never have figured it out that I had to edit two files in app-data.. Hopefully the dockers will survive next upgrade by Code 42..

This tread is holding me back from doing the upgrade to V6. I hope this gets resolved soon!

I would love to see a v6 final VMDK posted. I will follow this thread in hopes it happen! https://drive.google.com/file/d/0B93BSpm4tzDMTHo0Nmk0RHVzcTA/view?usp=sharing Much love!

I would love to see a v6 final VMDK posted. I will follow this thread in hopes it happen!

Great guys! One of these days I will muster up the courage to upgrade from 5.0 ..

Thanks a million!

You should post the log.

Thanks!

Can anyone provide a play by play on this operation. I find myself in the midst of doing the same thing. Going from a 3TB parity to a 4TB. And then adding the old parity as a datadisk. Is it something like: 1. Preclear new parity disc 2. Stop array 3. Ubselect the 3TB parity disc 4. Select the new 4TB disc as parity 5. rebuild parity 6. preclear 3tb (old parity) 7. stop array 8. add 3TB to the array Or do I need to something else?

Ja

Have you tried reading and writing to the disks outside UNRAID? Might be a faulty card? My card turned out to have a broken port. Redballed disks one on of the ports.

What are you trying to accomplish here? You want to use HDD's attached to a saslp as datastore? Wouldn't it be better to hook a hdd a SATA-port on the MB? I haven't tried using my sas2lp with attached HDD as a datastore. Why are you trying to do this?

This is how mine looks most of the time..

I haven't looked to be honest.