Teza

Have not installed the lastest version update of unraid, but installed the previous one. System was shut down normally due to a problem with the UPS. (Raid was stopped and system shut down normally) During boot the power was lost and after that the unraid will not boot again. Is it easy to spot and solve the problem or do I need to find an old backup of the USBdrive and try to recover it? Thanks

It seems like there is several peoples that have problems with dvd hardware and unraid/makemkv. I barely know anything about unraid/linux, but linux finds the drive when I use the command line. The drive is also found inside unraid, and it seems like the container finds it as well. If I remember it correctly, back in 1998-2000 it could be difficult to find CD burner hardware and software that worked well with each other, and many cd burners was not working in some of the programs but worked just fine in other. Is it correct that it is different types of containers in unraid? If so can the problem might be in the container setup or that makemkv is selective regarding to hardware support? Or might it be as simple as a new linux driver is needed for the dvd burner? Linux find it but can't use it?

Oh, thank you. So with this information I can rebuild the raid on any computer:

I am sorry if there is something basic I should have understood, but have not, but I am trying I have installed the binhex-makemkv app. But what ever I try I get "The program can't find any usable optical drives." message. This is the drive I try to include: Setup: Repository: binhex/arch-makemkv Network Type: Bridge Console shell command: Shell Privileged: ON Host port 1: 6080 Host Path 2: /mnt/user/Multimedia/ Key 1: Tower Key 2: Key 3: 000 Key 4: 99 Key 5: 100 AppData Config Path: /mnt/user/appdata/binhex-makemkv Have also tried to add all of the devices I could find related to the internal blue-ray /dev/disk/by-id/ata-PLEXTOR_BD-R_PX-B950SA_2512075_216201500042 /dev/sr0 (listed in scsi devices) /dev/dvd /dev/dvd0 /dev/dvdr /dev/dvdr0 /dev/dvdrw /dev/dvdrw0 /dev/dvdwriter /dev/dvdwriter0 /dev/sg8 /dev/cdr /dev/cdr0 /dev/cdrom /dev/cdrom0 /dev/cdrw /dev/cdwriter /dev/cdwriter0 Have also tried these, but I then get an error: --device/dev/sr0 is not an absolute path --device=/dev/sr0 is not an absolute path --device /dev/sr0 is not an absolute path Edit: found the advanced view. Have tried to add: --device=/dev/sr0 and --device=/dev/sr0 --device=/dev/sg0 But still with no luck. Edit 2: Have logged in on the terminal (?) for the first time and ran: lsscsi -g [1:0:0:0] cd/dvd PLEXTOR BD-R PX-B950SA 1.01 /dev/sr0 /dev/sg8 lsscsi -l state=running queue_dept=1 scsi_level=6 type=5 device_blocked=0 timeout=30 lsscsi -v [1:0:0:0] cd/dvd PLEXTOR BD-R PX-B950SA 1.01 /dev/sr0 dir: /sys/bus/scsi/devices/1:0:0:0 [/sys/devices/pci0000:00/0000:00::11.0/0000:07:00.0/host1/port-1:0/end_device-1:0target1:0:0/1:0:0:0] Have tried the following under the advanced tab: Extra Parameters: --device=/dev/sr0 --device=/dev/sg8 --device=/dev/sg8 --device=/dev/sr0 --device /dev/sg8 --device /dev/sr0 --device /dev/sr0 --device /dev/sg8 What am I missing?

I also see that some recommend to use usb2 flash drives. My flashdrive is a USB3, but I hope I do not need to replace it with a usb2 as well.

Ok, this is what happend. I took a new usb drive, instead of formatting the existing one, created a new install and replaced the config folder. The computer did not want to boot from the usb drive and just went into bios. I recreated the usb one more time, without replacing the config folder, and the computer would still not boot. I then compared the usb drives and found that the "EDI" folder was named "EDI-" on the new drive so tried to change that. Computer did still not boot. Then tried the new usb stick in another usb port, and computer booted. Um, ok... ...then tried the first usb key that crashed in the same usb port that would boot with the usb stick with a new install. Computer booted, unraid started, I got access to my server, was able to remove the makemkv app and everything seems to work just fine. So why did this happen? I guess the usb3 ports is not bootable, might be fixed by a bios configuration. The usb 2 ports seems to boot normally. What a relief... Next step is to create a backup of the usb stick!

I have crashed my unraid server, the server will not boot, and I did this before I got to the point of creating a backup of the usb stick, but after installing a license key and moving ~400 GB of data to the raid. Things to do different on my next attempt: Get the server up and running with a working array Create a backup of the usb stick! Install apps... At the moment I am not to worried about loosing data, and I know what disks where placed where. What did I do to prior to the crash: I tried to install Makemkv, it did not work, app would not start in web gui as it could not connect to something. I tried to stop the app, but the app/browser stop responding, I refreshed the browser and the app was stopped after a few long attempts. I tried to remove the app, but unraid could not do this, it just hanged in the browser, tho I could go to other menu choices. I was thinking it might help rebooting the server, to get rid of the app, witch most likely was my biggest mistake... Now the boot stops, and 2 leds are flashing on the keyboard 103 MB movie of the boot Before I start over by creating a fresh installed usb stick, I want to learn from my mistake. Is it possible fix the boot so the server will start? What should I had done, instead of rebooting the server? Is this enough information her to give an idea of what went wrong? Thanks

It took 7 hours and 27 minutes. Transferred 220 GB to the array and did a parity-check with no reported errors. Thank you for fast help!

Stop the array Set disk 2 to no device Start the array Stop the array Set disk 2 to... Start the array The disk will rebuild. Followed this to get the drive back into the array. Is it normal to use 6h 30m on this process with empty disks, or does it not matter how much that is stored, as all calculations must be redone anyway? What testing should i do before storing data onto the array, when rebuilt?

Intel ones is 3.0 Gb/s while the grey ones is 6.0 Gb/s. Not sure if that matters with the cache drive?

What controller would be recommended for this setup?

After installing unraid (first time user) disk 2 had a bad file system and it's 4GB capacity was not counted in the array. Parity read/check had 968081081 errors after 1h 3m. After a reboot, I formatted disk 2 and it became part of the array, and the array capacity increased to 12 TB. Everything looked ok. Then I tried to run a new parity-check, which I canceled after 160276490 errors, and because disk 2 status is now "Device is disabled, contents emulated". Searched the forum and did a diagnostics test that gave me the following info on disk 2: filserver-diagnostics-20191120-1252.zip Not sure how to proceed? Unraid 6.7.2 Hardware setup: Chieftec 19" 4U UNC-410F-B-OP Corsair AX 1200i, 1200W PSU ASUS Z9PE-D8 WS, 2xSocket-2011 2 ea Intel® Xeon® Processor E5-2660, 8-Core, 2.2GHz, 20MB 64 GB - Corsair Dominator DDR3 1600MHz 2 ea Intel® High Performance Liquid Cooling 3 ea ASUS GeForce GTX TITAN 6GB PhysX CUDA, 837MHz, 384bit Plextor PX-B950SA Blue-Ray writer 2 ea Chieftec Backplane CMR-2131 SAS (2x 5,25" bays for 3x SATA/SAS HDDs/SSDs) (NEW) 5 ea Seagate IronWolf 4TB 3.5" NAS HDD (NEW) Samsung SSD 860 EVO 500GB Kingston MicroDuo USB 3.0 16GB (NEW)