stv29

Members
  • Posts

    22
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

stv29's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Good Morning All, I am not finding in my search what I am looking for, probably because I'm not sure exactly what I am looking for. I added a passthrough disk to my Areca 1222; the first passthrough worked fine the array saw it with an differing naming convention but worked with a "new config". The second disk (want to move two more after this one) is not recognized in my device list. I am moving an existing array disk from the motherboard's SATA port to the Areca. Is there something special I should be doing with the SCSI ID and LUN on the Areca controller? Log.txt
  2. I've cleared all the drives and started fresh with 6.2.4 with the module from Areca's site for this version. I tried 6.3.2 but they module was an improper format. (Also tried without Areca's drivers on 6.3.2 following the below thread without success. I set the display name to automatic, installed my pro key and assigned the parity and one drive. Same results as before. I have confirmed the parity drive is still assigned to sdb. Any guidance is greatly appreciated. Thank you! Log.txt
  3. Thank you for the reply. I'm currently pre-clearing all the discs. I moved everything off the server to start fresh. I was poking around the forum and found Areca has an updated driver and indicated that v6.0 had native support (what I came from before upgrading). When I'm able to rebuild the kernel after the pre-clear I'll attempt the updated driver as well.
  4. Tried with 6.2.4, same settings as previously suggested, no success.
  5. Thank you for the reply. That seems a little more complicated than I was after. I removed the app and went back to dual booting to a windows/unraid.
  6. Hello! John_M assisted me in directing me to this app but I believe I am doing something wrong. I have 6 drives I would like to use. I used the app-created configuration as a template and added the other drives but I cannot tell it is doing anything. The drive activity lights aren't flickering. Should the drives be a path or a device - I tried both but they did the same? The log (attached) shows all the disks inserted but only one folder appeared and it is empty (dev5). Ripper_Log.txt
  7. I tried it, it didn't work. I've started syncing everything with my offsite backup and will start over with this one. Thank you for you help!
  8. Would initiating the "new config" do any harm? I knew I was in for a lengthy parity re-build but I certainly don't want to lose anything.
  9. Yes, sir. I attached an image of the current setting. Is this correct?
  10. I changed the "Display world-wide-name" in device ID from "Disabled" to "Automatic", unfortunately without success in assigning the parity drive. Does the same as before. Sys_Log.txt
  11. I'm sorry to be so needy recently; I very rarely tinker with hardware but necessity arose. My parity drive was on its last spins and I decided to move the entire system to a new case. Everything went fine until it was time to replace the parity drive. I previously had it in a RAID0 on an ARC 1222, 2x4tb drives for 8tb total. The only thing I did was swap the dying drives and pre-cleared for two rounds. I left the truncation off. Now, when I am able to select it as the parity drive and start the array, it acts like it is going to start and then stops and brings me back to the main screen to start the server again. It does the same thing when I assign it as a regular disk and start. Leaving it unassigned I can start the array unprotected. What did I do wrong? I've attached my log from a fresh reboot and starting as a parity drive. Any assistance or insights someone can offer is greatly appreciated. Thank you! Sys_Log.txt
  12. I do have the pro license, that won't be an issue for me. For an even dumber follow-up: I'm assuming I don't have to assign it as an array device? They are not detailed under unassigned devices when I start the array. I do see them when I searched for the devices.
  13. That is exactly what I was after. I've setup ripper in a docker and found I can point to multiple optical drives but I'm not sure their paths. Do you know what the proper entry into the console is to list all the devices with their name/paths? I have searched online but I'm probably not using the correct terminology.
  14. Thank you for the quick reply. I moved everything off that card and it seems to be working fine, now.