July 3, 201115 yr Firstly I'd like to thank everyone who helped me when my parity drive died. With your help i've learnt a lot. This weekend i installed unmenu and have been playing around with it, trying to learn how it all works before I attempt to install sabnzb & sickbeard. today i've installed an old 320g drive and precleared it. I then used unmenu to partition it. The disk management tab lets me mount the drive as read only or read/write. There is also an option to share the drive. Theres 2 things I need help with. 1. Is there a way to make the drive mount and share automatically after a restart? My guess is that i need to add some lines to the go file 2. on the unmenu main page the drive has two entries: /dev/sdi ST3320620AS_9QF0P38M /dev/sdi1 ST3320620AS_9QF0P38M I'm guessing the sdi1 refers to the partition? but don't know why this is different to array drives...
July 3, 201115 yr 1. Is there a way to make the drive mount and share automatically after a restart? My guess is that i need to add some lines to the go fileYour guess is correct. 2. on the unmenu main page the drive has two entries: /dev/sdi ST3320620AS_9QF0P38M /dev/sdi1 ST3320620AS_9QF0P38M I'm guessing the sdi1 refers to the partition? Yes, it (sdi1) refers to the 1st partition. but don't know why this is different to array drives... The first partition of the data drives assigned to the array are connected through the "md" device driver and show as /dev/mdX devices you then mount as the protected array drives.
July 3, 201115 yr Author Thanks Joe 1. Is there a way to make the drive mount and share automatically after a restart? My guess is that i need to add some lines to the go fileYour guess is correct. could you please help me out with the lines I need to add?
July 4, 201115 yr Author after reading some tutorials on linux and giving it some more thought I decided that maybe snap would be a better solution. This is mainly because I've noticed the "sdx" assigned to drives can change when more drives are added to the system and I would like a set and forget solution, and snap sounded straight forward to setup. unfortunately the install script would not work so I had to install it manually... some hours latter I now have a mounted shared hard drive outside the array. Yaa! I can't help thinking about the post I saw recently about everything to do with unraid being hard. oh well.. now I am finally ready to have a go at installing sabnzb & sickbeard..... this should be fun....
July 5, 201114 yr after reading some tutorials on linux and giving it some more thought I decided that maybe snap would be a better solution. This is mainly because I've noticed the "sdx" assigned to drives can change when more drives are added to the system and I would like a set and forget solution, and snap sounded straight forward to setup. unfortunately the install script would not work so I had to install it manually... some hours latter I now have a mounted shared hard drive outside the array. Yaa! I can't help thinking about the post I saw recently about everything to do with unraid being hard. oh well.. now I am finally ready to have a go at installing sabnzb & sickbeard..... this should be fun.... What you are attempting to do is outside the purview of base unRAID. unMenu makes a lot of it easier, but there can still be some stuff that is difficult. You may also be complicating things by using a beta version of unRAID. Some of the people here that write the add-ons have not updated there stuff to work with the beta... it is a moving target and continually patching it to allow it to run on 5.0bX can get old quickly.
Archived
This topic is now archived and is closed to further replies.