January 12, 201115 yr So I think I'm all about setup, just a few quick questions. 1. It shows the flash drive on the network, how do I hide that? 2. Do I need to format the drives? I thought pre-clearing formats them? Do I need to click on format in the picture below? 3. And so if I format the drive by pushing the button is that it? I'm good to go as far as everything else? I just add data to the drives? I'm guessing by default it is read/write for anyone on the network? 4. Lastly, how do I set it up so I don't need it to boot with a keyboard? I need to enter root when it turns on right? Anyway to make it so it automatically starts up? Thanks
January 12, 201115 yr 1. It shows the flash drive on the network, how do I hide that? In the shares set to hidden 2. Do I need to format the drives? I thought pre-clearing formats them? Do I need to click on format in the picture below? Yes preclear set your drives up, but you still need to hit format for the first time 3. And so if I format the drive by pushing the button is that it? I'm good to go as far as everything else? I just add data to the drives? I'm guessing by default it is read/write for anyone on the network? No, normally you have to add users and then setup your shares with user names so you can tell unRAID who can access what. 4. Lastly, how do I set it up so I don't need it to boot with a keyboard? I need to enter root when it turns on right? Anyway to make it so it automatically starts up? Thanks Nope when you turn it on it will automatically start the array. You just use a http://tower or you can use telnet to access it. You don't have to use either a keyboard or a mouse
January 13, 201115 yr 2. Do I need to format the drives? I thought pre-clearing formats them? Pre-clearing writes zeros to the entire drive. It also writes a special signature to allow the disk to be recognized as cleared. It does not format the drive.Do I need to click on format in the picture below? Yes. Formatting typically takes under 10 minutes on a large drive.
January 13, 201115 yr Author Okay and lastly, so according to the picture above, I have set a parity drive. So now that I have shares setup, 2 questions. 1. For my Movies share, I have no minimum amount set, but for my movies, I have 150gb setup(converted to kb) will this cause any problems? 2. So when I start copying files, my data is being backed up as of now? Parity-Sync in progress. Cancel will stop Parity-Sync. WARNING: canceling Parity-Sync will leave the array unprotected! So it says in progress, does that mean it is backing up the data I just put on? I just put on an album about 50mb and it says its going to take an estimated 700+ minutes? Estimated speed is only at 44,000kbps? Is that roughly 44mbps? Is it best to stop parity and copy all my files over first?
January 13, 201115 yr Okay and lastly, so according to the picture above, I have set a parity drive. So now that I have shares setup, 2 questions. 1. For my Movies share, I have no minimum amount set, but for my movies, I have 150gb setup(converted to kb) will this cause any problems? "The "Min amount free" is not really useful for you until there is a second data disk to use when the first has less then the "min free" left on it to write to. 2. So when I start copying files, my data is being backed up as of now?Your data is NEVER backed up. It will be protected from a disk failure by parity once parity has been calculated on the entire array. From what you are showing, that Parity-Sync is in progress. Let it complete. So it says in progress, does that mean it is backing up the data I just put on? What will it say when the sync is complete? Do not confuse a backup of your data with parity protection against a disk failure. They are two entirely different things. A backup is on different media, preferably off-site. unRAID provides protection from a single failed disk. It does that by calculating parity on the entire array. Parity protection from a single disk failure will be in effect once the initial parity-Sync is complete. Parity is being calculated as you initially load your data. Parity is a set of XOR operations across the entire set of data drives. What is stored on the parity drive is just a set of bit-wise math calculations that allow the array to re-construct a single missing/defective disk. The parity disk is not a "backup" of your data. You are not protected from a disk failure until the initial parity calculation is complete. Do not interrupt it. Joe L.
January 13, 201115 yr Author ations across the entire set of data drives. What is stored on the parity drive is just a set of bit-wise math calculations that allow the array to re-construct a single missing/defective disk. The parity disk is not a "backup" of your data. You are not protected from a disk failure until the initial parity calculation is complete. Do not interrupt it. Joe L. Do I do this every time data is added or just this once? Isn't raid basically making mirrors of your data in case your drive becomes corrupt?
January 13, 201115 yr ations across the entire set of data drives. What is stored on the parity drive is just a set of bit-wise math calculations that allow the array to re-construct a single missing/defective disk. The parity disk is not a "backup" of your data. You are not protected from a disk failure until the initial parity calculation is complete. Do not interrupt it. Joe L. Do I do this every time data is added or just this once? the initial parity calculation will occur once. It will be re-checked if the array is not "Stopped" before powering down. So, basically always stop the array first, then power down. If you lose power with the array started parity cannot be trusted, so a full parity check will begin when you next power up. Let it finish. Isn't raid basically making mirrors of your data in case your drive becomes corrupt? No. Parity is not a mirror or a copy of your data. It is a math calculation that allows you to re-construct any one failed drive. Do not think of it as a copy, or a mirror, or a backup. It is none of those. Furthermore, once the initial parity calculations are written to the parity drive you can not really be sure you are protected until you know what you write to the parity drive can be read back. To verify it is all working, you must click on the "Check" button and let it verify it cal read all that was written to the parity drive. Let the "Check" complete. Joe L.
January 13, 201115 yr Author ations across the entire set of data drives. What is stored on the parity drive is just a set of bit-wise math calculations that allow the array to re-construct a single missing/defective disk. The parity disk is not a "backup" of your data. You are not protected from a disk failure until the initial parity calculation is complete. Do not interrupt it. Joe L. Do I do this every time data is added or just this once? the initial parity calculation will occur once. It will be re-checked if the array is not "Stopped" before powering down. So, basically always stop the array first, then power down. If you lose power with the array started parity cannot be trusted, so a full parity check will begin when you next power up. Let it finish. Isn't raid basically making mirrors of your data in case your drive becomes corrupt? No. Parity is not a mirror or a copy of your data. It is a math calculation that allows you to re-construct any one failed drive. Do not think of it as a copy, or a mirror, or a backup. It is none of those. Furthermore, once the initial parity calculations are written to the parity drive you can not really be sure you are protected until you know what you write to the parity drive can be read back. To verify it is all working, you must click on the "Check" button and let it verify it cal read all that was written to the parity drive. Let the "Check" complete. Joe L. How long does the check take? Also so what is the best way to backup the data to prevent it from being lost?
January 13, 201115 yr ations across the entire set of data drives. What is stored on the parity drive is just a set of bit-wise math calculations that allow the array to re-construct a single missing/defective disk. The parity disk is not a "backup" of your data. You are not protected from a disk failure until the initial parity calculation is complete. Do not interrupt it. Joe L. Do I do this every time data is added or just this once? the initial parity calculation will occur once. It will be re-checked if the array is not "Stopped" before powering down. So, basically always stop the array first, then power down. If you lose power with the array started parity cannot be trusted, so a full parity check will begin when you next power up. Let it finish. Isn't raid basically making mirrors of your data in case your drive becomes corrupt? No. Parity is not a mirror or a copy of your data. It is a math calculation that allows you to re-construct any one failed drive. Do not think of it as a copy, or a mirror, or a backup. It is none of those. Furthermore, once the initial parity calculations are written to the parity drive you can not really be sure you are protected until you know what you write to the parity drive can be read back. To verify it is all working, you must click on the "Check" button and let it verify it cal read all that was written to the parity drive. Let the "Check" complete. Joe L. How long does the check take? A parity check will occur at a rate somewhere between 12MB/s and 100MB/s. Most modern motherboards and disk controllers average about 75MB/s. That would result in a parity-check time of somewhere around 7 1/2 hours for your 2TB drives.Also so what is the best way to backup the data to prevent it from being lost? Good question... off-site backup. Perhaps a portable hard-disk, writable DVDs/CDs, etc. Cloud storage.
January 14, 201115 yr Author How often does the parity check do its thing? I was just copying files and it just shutdown. When I turned it back on, it started doing a parity check.
January 14, 201115 yr How often does the parity check do its thing? I was just copying files and it just shutdown. When I turned it back on, it started doing a parity check. A parity check is run every time you do not "Stop" the array before shutting off the server. If the server "just shut down" you have bigger problems to concern yourself about than the parity check on restart. (Hint: the server should NEVER just shut down) Joe L.
January 14, 201115 yr Author Will it show in the logs why the server shutdown? Its plugged into a Upc battery backup so it wasnt a power issue. What is the log named?
January 14, 201115 yr The logs get lost on a reboot so no it won't show. I would be concerned with things like loose cables, the proper heatsink installation, and improperly installed RAM. I've also done stupid things like not fully plugged the power cord in before and it would intermittently cut out. If you go to http://tower/syslog you should get the current log. Peter
January 14, 201115 yr Author So its not a software error? Could it be the upc? If its loose cables why would it happen when i start copying data?
January 15, 201115 yr Author Not sure what you can make out of this, but it said it found 2 errors. What does that mean/what do I do? Jan 14 05:26:27 Tower kernel: unraid: allocating 13240K for 1280 stripes (2 disks) Jan 14 05:26:27 Tower kernel: md1: running, size: 1953514552 blocks Jan 14 05:26:27 Tower emhttp: shcmd (6): udevadm settle Jan 14 05:26:27 Tower emhttp: shcmd (7): mkdir /mnt/disk1 Jan 14 05:26:27 Tower kernel: mdcmd (9): check Jan 14 05:26:27 Tower kernel: md: recovery thread woken up ... Jan 14 05:26:27 Tower kernel: md: recovery thread checking parity... Jan 14 05:26:27 Tower emhttp: shcmd (: set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Jan 14 05:26:27 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Jan 14 05:26:27 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jan 14 05:26:27 Tower kernel: REISERFS (device md1): using ordered data mode Jan 14 05:26:27 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 14 05:26:27 Tower kernel: REISERFS (device md1): checking transaction log (md1) Jan 14 05:26:28 Tower kernel: skge eth0: Link is up at 100 Mbps, full duplex, flow control both Jan 14 05:26:29 Tower ifplugd(eth0)[1245]: Link beat detected. Jan 14 05:26:30 Tower ifplugd(eth0)[1245]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Jan 14 05:26:30 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:01:29:D3:4E:3E Jan 14 05:26:30 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.106 broadcast 192.168.1.255 netmask 255.255.255.0 Jan 14 05:26:30 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1 Jan 14 05:26:30 Tower ntpd[1743]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1) Jan 14 05:26:30 Tower ifplugd(eth0)[1245]: client: Starting NTP daemon: /usr/sbin/ntpd -g Jan 14 05:26:30 Tower ntpd[1744]: precision = 1.000 usec Jan 14 05:26:30 Tower ntpd[1744]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 14 05:26:30 Tower ntpd[1744]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jan 14 05:26:30 Tower ntpd[1744]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Jan 14 05:26:30 Tower ntpd[1744]: Listening on interface #2 eth0, 192.168.1.106#123 Enabled Jan 14 05:26:30 Tower ntpd[1744]: kernel time sync status 0040 Jan 14 05:26:30 Tower ifplugd(eth0)[1245]: Program executed successfully. Jan 14 05:26:39 Tower ntpd[1744]: synchronized to 207.61.229.70, stratum 3 Jan 14 05:28:42 Tower kernel: REISERFS (device md1): replayed 657 transactions in 135 seconds Jan 14 05:28:42 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Jan 14 05:28:44 Tower emhttp: shcmd (9): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 14 05:28:44 Tower emhttp: _shcmd: shcmd (9): exit status: 1 Jan 14 05:28:44 Tower emhttp: shcmd (10): cp /etc/exports- /etc/exports Jan 14 05:28:44 Tower emhttp: shcmd (11): mkdir /mnt/user Jan 14 05:28:44 Tower emhttp: shcmd (12): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Jan 14 05:28:45 Tower emhttp: shcmd (13): killall -HUP smbd Jan 14 05:28:45 Tower emhttp: shcmd (14): /etc/rc.d/rc.nfsd restart | logger Jan 14 08:54:51 Tower kernel: md: parity incorrect: 2549930136 Jan 14 08:54:51 Tower kernel: md: parity incorrect: 2549930144 Jan 14 11:40:18 Tower kernel: md: sync done. time=22432sec rate=87086K/sec Jan 14 11:40:18 Tower kernel: md: recovery thread sync completion status: 0
Archived
This topic is now archived and is closed to further replies.