NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Tips from other users
875 TopicsFrom the Netgear Blog - Data Explosion
When it comes to choosing a networking and storage setup, small and medium businesses set their priorities in a very straightforward way: It needs to simply work It should be affordable It needs to be easy to install and use In our latest blog Netgear's Vice President of SMB Product Line Managment - Richard Jonker lays out clear arguments for controlling for these priorities with a local ReadyNAS appliance vs. storing all your files in the cloud or local storage. Check out the blog post here: Did you solve or are planning to solve your data issue with a ReadyNAS? Let us know in the comments below.Terrible new forum format
Is there a way of vwing all messages in all categories as there was before? That made it much easier for me to find messages to which I might add a solution or comment.. Half the time (like with this message), it's not evben clear what the correct category is, but it didn't really matter since you could view all at once. The format also now has fewer messages listed on a page and a lot more fluff. I don't know who thinks this is an improvement, but I don't see it as one. I know you didn't write the software, but you could have chosen to not update it. You'll probably be seing a lot less of me.
V+12 power is out of normal range -- changing power plug worked
there's already some other threads about the same problem (see below), but as the devices get older every day, the problem may occure more often -- and of course, it's not covered by warranty. symptoms: * my ReadyNas Ultra2 log got flooded with warning messages like: V+12 power is out of normal range [expected: 12.00 current: 10.82]. * later, the NAS would turn itself off, later not boot again * the sound while booting suggested a lack of power...the disks would try to spin, but stop again * at some point, the NAS would not even start without disks in it, but would turn off after some seconds * replacing the power supply ("brick") would not solve the problem other solutions: * in the thread: Ready NAS Ultra 2 power supply issue and out of support the solution is: cleaning the inner side of the chassis! the problem seemed to be dust. * in the thread: V+12 voltage in enclosure Internal is out of spec. (10.72 V) it's discussed, if the device can run at a lower voltage -- and revealed that you can measure the voltage on the SATA backplane. Running at higher voltage: bad idea. * there's also a description on how to change the sensor's limits, if the sensor got corrupt (but voltage on the backplane is fine) my experience: * changing the power supply -- no difference * opened and disassembled the chassis, cleaned everything -- no difference * measuring voltage on SATA backplane: <11.0V! * measuring the downside pins of the power plug on the main board: <11.0V -- BINGO! solution: * the inner pin of the power plug was corroded/worn out. Soldered cables to the pin and a new plug outside of the chassis -- works great! pictures of today:
Think twice before committing to X-RAID or RAID-5. What is your recovery plan?
TL;DR: Because I chose RAID-1 over X-RAID, I easily survived a disk failure. I'm back to having a working RAID-1 array, with no loss of data, no support contract, no data recovery fees, no proprietary programs, no shipping drives across the country, and my only cost (besides the replacement drive, of course) was a single SATA-to-USB device ($30). What worked? Boot up with Active@ LiveCD (http://www.livecd.com/) and use the File Manager. 5 years ago, when I bought my ReadyNAS, I engaged in these forums a debate between RAID-1 and X-RAID. My #1 priority was ability to recover data after a failure, while other people focused on maximizing disk space. Well, finally, one of my disks failed recently. No warning ahead of time, no SMART data indicating a disk might fail, just "Disk failure detected" in the logs after it was too late. My shares or volumes were inaccessible via normal Windows networking, and not available in RAIDiator either. There was no indication whether my data was still intact or not. Because I was using RAID-1, I believed that the good disk should still be OK, the hard part was figuring out how to read it. I connected the working drive to my laptop using a SATA-to-USB converter. Many software ideas did not work because the RAID data volume is seen as RAW and not Ext4, so Ext4 readers in Windows don't work. In the end it was one of the simplest options: I booted up using the Active@ LiveCD with the drive already attached. Once booted, the simple Linux File Manager ("Dolphin") was able to see and read all my files perfectly. I did NOT need any of the proprietary software on the CD, just the simple File Manager. And of course, it was possible to plug in a portable drive and copy everything from the source drive to the portable backup. Easy and Free. (I will also note that the basic file manager on the UFS Explorer emergency CD worked as well, although I found Dolphin slightly easier to use) (Later, I also found out that the volumes and shares were all available directly from the NAS after removing the failed drive. In other words, when the good drive was by itself without a failed mirror drive, the NAS made all the data and files available again, with an "unprotected" warning. So essentially, you don't even need a LiveCD... but the biggest advantage is being able to copy data at USB3 speed) Finally, restoring the NAS to RAID-1 was incredibly easy. I put the good drive back into its original slot on the ReadyNAS, ordered a replacement drive (same make and model as the failed drive), and popped it in. The ReadyNAS immediately began copying everything, it had a percentage indicator on the front panel, and only took about 10 hours to mirror 2.7 GB of data. Contrast this with the restoration of an X-RAID array. Start with trying to connect 3 drives to a laptop, plus a portable backup drive. You can easily run out of ports (especially at USB3 speed) or power outlets to plug everything in. Sure you can overcvome this but you're paying for SATA-to-USB enclosures, USB hubs, power strips, etc. Now, is there a definitive guide to restoring an XRAID array to read its data? Not from Netgear. There are some helpful tips and recommendations in these forums but certainly nothing that is foolproof or easy. There is a good chance you'll need to learn to use mdadm. And if it isn't working, is it because the array is not set up correctly, or the data itself is corrupted. Assuming you aren't a full time data recovery expert, how would you tell? There are many more reports of destroyed, overwritten and lost data, or expensive support contracts, than there are of successful DIY recoveries. And if it isn't DIY, it's certainly going to be expensive and often require you to send the physical drives somewhere. Bottom line: after going through this process, I am more convinced than ever that RAID-1 is superior to any other RAID option, unless your data is disposable or 100% backed up in real-time. RAID-1 is not failsafe of course (fire, theft, deleting/overwriting a file, etc), but it is just as compatible with any other backup methods (2nd NAS, drive-swapping, portable backup drives, rsync, cloud storage) as any other RAID type, PLUS you get the benefit of the easiest and fastest recovery process in the case of a drive failure. I would also like to thank StephenB for participating in the initial debate. His ability to see the pros and cons of both methods was appreciated.Complete guide for JDownloader (and VNC) in OS6
Hi, this if my first tip (I hope not last) were I'm going to explain how to install and configure a VNC screen sharing system to get JDownloader (or any X-window application) running. Below steps are intented to be run with a minimum of Unix/Linux understanding, if you are newbie in Linux, don't try it, you can mess up your NAS!!. Remember to backup valuable data in your NAS before any attempt to continue reading, it's always better loosing time backing up than crying later ;) I've tested it both in x86 and ARM processors. First you have to enable SSH within your Netgear NAS: You can loose support in case SSH has been enabled!!! After connect through SSH into the server as root (your admin frontview password will be the same for root). Let's start with the command line... Wait... have you back up your data already?, no?, well, later on, complains to /dev/null. ok, go ahead... Wait... did you understand the joke about /dev/null?, no??, I recommend you to stop here. Don't say I didn't warn you about you can mess up your NAS data if you're bit lost with VNC, SSH, root account, package installation skills, /dev/null and you don't have a minimum set of Linux (debian) skills. If you are now connected as root into your NAS, remember. Big power comes with big responsibility If you're still here reading, well... may the force be with you. Now I will put a secuence of commands you have to run as root, I will explain them later. Note: Run them one by one, understanding what is showing each command. If you don't understand output, stop after running the first. There is one change to be done to start. Check /etc/apt/sources.list, and include below line and save the file: deb http://ftp.se.debian.org/debian/ wheezy main contrib non-free Time to install new packages: apt-get update apt-get install dialog apt-get install bzip2 apt-get install tightvncserver apt-get install x11vnc apt-get install xvfb apt-get install xli apt-get install fluxbox menu apt-get install fbautostart apt-get install unrar apt-get install xterm mkdir -p /usr/X11R6/bin/Xvfb cd /usr/X11R6/bin/Xvfb/ ln -s /usr/bin/Xvfb . apt-get install xmodmap apt-get install x11-xserver-utils I use vnc through xvfb, it's faster and memory consumption is lower than tightVNC, feel free to use one or another, this document is based on xvfb. Window Manager will be fluxbox, another low-memory-consumption window manager. Now, it's time to install java. Download it from Oracle web page from your laptop and copy it into the NAS over AFP or SMB in a folder (Video shared resource for example) and returning to the SSH connection you've opened previously, run the following... TIP: there is a way to download Oracle software with wget directly from the NAS (try "wget oracle" in google). mkdir /usr/java cd /data/[shared resource where you've placed the jdk downloaded] gzip -d jdk-7u6-linux-x64.tar.gz tar xvf jdk-7u6-linux-x64.tar mv jdk1.7.0_06/ /usr/java/ update-alternatives --install /usr/bin/java java /usr/java/jdk1.7.0_51/bin/java 1 java -version Note: "java -version" command has to give an output about current java version that has to be the same as the one installed by you :) Now, install jDownloader. cd /root wget http://installer.jdownloader.org/jd_unix_0_9.sh chmod 755 jd_unix_0_9.sh ./jd_unix_0_9.sh It has to give you an output similar to this: testing JVM in /usr ... Starting Installer ... SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. This will install JDownloader on your computer. OK [o, Enter], Cancel [c] o JDownloader Downloadmanager JDownloader is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details. Want to contribute? Check out the Sourcecode and "Gettings Started" Developer Tutorial! JDownloader is FREE Software. If you paid for it you should claim your money back. Make sure that you downloaded the official JDownloader Version at JDownloader.org. Where should JDownloader be installed? [/opt/jdownloader] Create a desktop icon? Yes [y, Enter], No [n] n Extracting files ... Please wait. Completing Systemintegration. Setup has finished installing JDownloader on your computer. Run JDownloader? Yes [y, Enter], No [n] n Finishing installation ... Answers to the above questions are: "o" (to continue), "/opt/jdownloader" (folder where to install it), "n" (to avoid creating destktop icon) and "n" (to don't run jdownload now). Time to create vnc password: # vncpasswd Using password file /root/.vnc/passwd VNC directory /root/.vnc does not exist, creating. Password: typeyourpasswordhere Verify: typeit again Would you like to enter a view-only password (y/n)? n and the tricky part: create the following file into /etc/init.d/jd and set 755 permissions (chmod 755 /etc/init.d/jd). Copy/paste below content: #! /bin/sh #set -e # Run VNC in OS6 by Carlos Villabrille export USER="root" export PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/var/run/vncserver" NAME="jd" XVFB="/usr/bin/X11/Xvfb" XVFBARGS=":1 -screen 0 1024x700x24 -fbdir /var/run " PIDFILE="/var/run/xvfb.pid" start() { echo -n "Starting virtual X frame buffer: Xvfb" export DISPLAY=:1 /sbin/start-stop-daemon --start --quiet --pidfile $PIDFILE --make-pidfile --background --exec $XVFB -- $XVFBARGS /bin/sleep 2 /usr/bin/x11vnc -display :1 -bg -xkb -shared -8to24 -o /var/log/x11vnclog -nolookup -rfbauth /root/.vnc/passwd -forever -nap -many & /usr/bin/x-window-manager & echo "Conect with vnclient :1" } stop() { export DISPLAY=:1 /usr/bin/x11vnc -R stop /sbin/start-stop-daemon --stop --quiet --pidfile $PIDFILE } case "$1" in start) echo -n "Starting VNC server (connect with vnc on :1): " start ;; stop) echo -n "Stopping VNC Server " stop ;; restart) echo -n "Restarting VNC server " stop start ;; *) echo "Usage: /etc/init.d/$NAME {start|stop|restart}" exit 1 ;; esac exit 0 Set it to start on next boot: ln -s /etc/init.d/jd /etc/rc3.d/S99jd Now, it's time to connect through a VNC client to your NAS IP port 5901 ip_of_your_nas:1 After login with your prevsiouly set password in the VNC client, open a bash shell (right button and will appear a menu, find "shell" or "bash" option) and run /opt/jdownloader/JDLauncher & Actually, you can install any X-Window application you need like iceweasel for browsing any graphical application. As you wish.
Installing and running OpenVPN @ boot - PrivateInternetAcces
Hi All, I have been trying to install OpenVPN and use PrivateInternetAccess (PIA) as my VPN Server on my ReadyNAS for a while now - my prime usecase was that I wanted all the connection to be encrypted while exposing it to external world (like sharing files right out of my NAS or torrent). The following are the steps which worked for me and my NAS is always on VPN now. 1. Enable SSH by going into System -> Settings in your WebView PS: This may cause problem with Netgear support - so do @ your own risk. However, I am not modifying anything with system and it looks safe to me. 2. Download Putty from link below http://the.earth.li/~sgtatham/putty/0.63/x86/putty.exe 3. Go to command prompt, navigate to the directory where you placed putty. Once in the directory, execute the following command putty <NAS Address> 4. You will see a terminal window open up asking for your login. enter your login info that you use to access your NAS from webbrowser 5. Now enter the following command on the terminal prompt apt-get install openvpn 6. This will install OpenVPN. Now, you need to get the VPN config files from PIA. Use the following commands below to navigate the OpenVPN directory and get the files cd /etc/openvpn wget https://www.privateinternetaccess.com/openvpn/openvpn.zip 7. Extract the files using unzip command. If you dont have the program, use apt-get command as above (replace openvpn with unzip) unzip openvpn.zip 8. Now, create a file - say userpass.file and type username on first line and password on the second line and save it. To save a file, press Esc and type :wq (including the colon) and press enter vi userpass.file 9. Chose one of the .ovpn file - for this eg, I chose France.ovpn and edit it. When you open it using the vi command, there will be a line auth-user-pass. Change it to auth-user-pass userpass.file and save the file as mentioned above. vi France.ovpn 10. at this time, you are all set to create a VPN connection. However, the issue is that now you need to always activate it manually. So, now we will create a startup file which runs automatically everytime you boot your NAS. Use the following commands to create a new file called startvpn.sh - you can name whatever you want cd /etc/init.d vi startvpn.sh 11. Now type the following lines and save the file #!/bin/bash cd /etc/openvpn openvpn France.ovpn 12. Once saved, you need to make the script executable. Use the command below for the same chmod +x startvpn.sh 13. Now, you need to add this script to run at everyboot. To do so, you need to add the following command in crontab file. Open the crontab file using command crontab -e and then add the following line anywhere in the file @reboot ./etc/init.d/startvpn.sh & . Save it using the Esc -> :wq! 13a. You can also use the following command to add this command to startup update-rc.d startvpn.sh defaults 14. Now you need to see if the VPN has started. To do so, type ifconfig on the command line and you will see a new connection starting with a config similar to below tun0-00 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 This means your vpn is running perfectly and you added another layer of security. Please let me know if this worked for you - i am not a Linux expert but will try to answer any questions you may have Linux experts - comment/add anything to make it better. Thanks, ArpanSolved
How to control fanspeed on a RN104
On special request, here is a workaround for controling the fanspeed of the RN104 ( most likely the same on a 102). For this you will have to SSH in to the NAS. Thanks to Moseleypj for doing the work. First you create a file in /root with the name fanoveride. Put the following lines in to the file. #!/bin/bash ## Variables ## FANPWMPATH=/sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1 FANSPEEDPATH=/sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/fan1_input CORETEMPPATH=/sys/devices/platform/axp-temp.0/temp1_input MAXFAN=100 # Maximum operable speed MINFAN=0 # Minimum operable speed MINPWM=75 # PWM Limit MAXPWM=255 # PWM Limit MINTEMP=35 # Min temp -> Fan slowest MAXTEMP=75 # Max temp -> Fan fastest NEWSPEED=50 # Initial fan speed (%) ## Functions ## function getReadings { FANPWM=$(cat $FANPWMPATH) FANSPEED=$(cat $FANSPEEDPATH) CORETEMP=$(cat $CORETEMPPATH) } function setFanSpeed { if [ $NEWSPEED -lt $MINFAN ]; then NEWSPEED=$MINFAN fi if [ $NEWSPEED -gt $MAXFAN ]; then NEWSPEED=$MAXFAN fi NEWPWM=$(expr $MAXPWM - $MINPWM) NEWPWM=$(expr $NEWPWM \* $NEWSPEED) NEWPWM=$(expr $NEWPWM / 100) NEWPWM=$(expr $NEWPWM + $MINPWM) echo $NEWPWM > /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1 } function calcFanPercent { TEMPRAN=$(expr $MAXTEMP - $MINTEMP) TEMPREL=$(expr $CORETEMP - $MINTEMP) TEMPREL=$(expr $TEMPREL \* 100) TEMPPER=$(expr $TEMPREL / $TEMPRAN) NEWSPEED=$TEMPPER } ################################################################### echo "Automatically controlling fan speed..." while true do getReadings echo "Temp: $CORETEMP C FAN: $NEWSPEED% [$FANSPEED RPM] [$FANPWM]" calcFanPercent setFanSpeed sleep 10 done ################################################################### Now chmod 755 /root/fanoveride =================== Now create a file in /etc/init.d with the name fanoveride. Put the following lines in to this script #!/bin/sh ### BEGIN INIT INFO # Provides: FanOveride # Required-Start: $local_fs $network $named $time $syslog # Required-Stop: $local_fs $network $named $time $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Description: FanOveride overides the default ReadyNAS fan control ### END INIT INFO SCRIPT=~/fanoveride RUNAS=root PIDFILE=/var/run/fanoveride.pid LOGFILE=/var/log/fanoveride.log start() { if [ -f /var/run/$PIDNAME ] && kill -0 $(cat /var/run/$PIDNAME); then echo 'Service already running' >&2 return 1 fi echo 'Starting service.' >&2 local CMD="$SCRIPT &> \"$LOGFILE\" & echo \$!" su -c "$CMD" $RUNAS > "$PIDFILE" echo 'Service started' >&2 } stop() { if [ ! -f "$PIDFILE" ] || ! kill -0 $(cat "$PIDFILE"); then echo 'Service not running' >&2 return 1 fi echo 'Stopping service.' >&2 kill -15 $(cat "$PIDFILE") && rm -f "$PIDFILE" echo 'Service stopped' >&2 } uninstall() { echo -n "Are you really sure you want to uninstall this service? That cannot be undone. [yes|No] " local SURE read SURE if [ "$SURE" = "yes" ]; then stop rm -f "$PIDFILE" echo "Notice: log file is not be removed: '$LOGFILE'" >&2 update-rc.d -f <NAME> remove rm -fv "$0" fi } case "$1" in start) start ;; stop) stop ;; uninstall) uninstall ;; retart) stop start ;; *) echo "Usage: $0 {start|stop|restart|uninstall}" esac Now make sure it is executable and starts on boot: chmod +755 /etc/init.d/fanoveride update-rc.d fanoveride defaults To control it manually: service fanoveride start service fanoveride stop In my case i have the min and max temp in the script set to 35 and 75 degrees to create a nice fan response wich is not to nervous. If you set it between 40 and 65 the regulating becomes more agressive. Just play with the values for your needs.
Complete guide to install godaddy SSL to your readynas duo
IMPORTANT NOTES: i am not affiliated with godaddy and went through a very painful process of learning the basics of ssh and putty commands and httpd configuration "directives" to enable godaddy certificate for my webserver (apache on readynas duo, last available firmware). this process included crashing of my apache server purely due to my mistake and wrong configuration which resulted in loss of access to frontview. this is the danger of messing with httpd.conf file. i had to backup almost a terabyte of data, reinstall the OS on the readynas device to regain access, and then the below settings worked for me. very important, do the following at your sole risk, I will not be responsible for any data loss. I describe my self as an "informed" newbie in this field. However doing these below steps saved the day. Now I do not see the ugly certificate warning each time i visit my website over https:// (which i host from my readynas duo). Experts please feel free fill in for your comments. thanks to other senior forum members who have posted earlier tutorials, i just wanted to post a complete tutorial for newbies who have zero know how about this process like i had when i started, many many many google searches ago.... :D I have changed my domain name url for privacy, i will refer it to as coolexample.com. i also used tips from following earlier post, but they did not work for me, however it seems to have worked for some people: http://www.readynas.com/forum/viewtopic.php?t=18251 **************************************************************************************************** TOOLS: before attempting installing your ssl certificate, you obviously have to have to buy a domain name, dynamic dns service did not workfor me (i have dynamic ip), so i had to subscribe to Standard DNS (http://dyn.com/dns/dyn-standard-dns) worked for me. then i generated the CSR from godaddy and validated my domain using their TXT method. you may copy the generated intermediate and final certificate to one of your shares, eg., Documents. From there you can move them to the right location. so type following command for example: cp /c/documents/gd_bundle /etc/ssl/certs cp /c/documents/coolexample.com.crt /etc/ssl/certs where gd_bundle.crt is the intermediate certificate and coolexample.com.crt is the purchased SSL certificate 1. enable SSH access, search prior posts 2. PUTTY , google to download for free, can also try ApacheConf PRO, trial version is free. i only used it to view, not make any changes. "DO NOT" MAKE CHANGES TO OPENSSL.CONF FILE [/etc/ssl/openssl.conf], as may appear from prior posts, it may have worked for them, but didnt for me, got my cue from this webpage from symantec: [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR1095] PUT intermediate certificate "gd_bundle.crt", final certificate "coolexample.com.crt" and key file "coolexample.key", the only 3 files in the folder "certs"[/etc/ssl/certs], YOU WILL GET THESE FILES FROM GODADDY DURING CSR GENERATION. CSR generation is described on godaddy website: [http://support.godaddy.com/help/article/5269/generating-a-certificate-signing-request-csr--apache-2x using this command: openssl req -new -newkey rsa:2048 -nodes -keyout yourdomain.key -out yourdomain.csr [Replace yourdomain with the domain name you're securing. For example, if your domain name is coolexample.com, you would type coolexample.key and coolexample.csr] WORKING FILE: /etc/frontview/apache/httpd.conf ------------------------------------------ helpful link for To Install Renewed SSL Certificates and the Intermediate Certificates: http://support.godaddy.com/help/article/5349/installing-ssl-certificate--apache-2x ---------------------------------- COMMANDS COPY cp eg., cp etc/ssl/coolexample.key /etc/ssl/certs MOVE mv eg., cp etc/ssl/coolexample.key /etc/ssl/certs OPEN TEXT EDITOR: vi eg., vi /etc/frontview/apache/httpd.conf to save changes press esc, then type :wq then hit enter to exit without saving any changes, hit esc, then type :q! the hit enter restart server, 1. first kill and then 2. input command [root:~# only means to goto root with cd command first] 1. root :~# killall apache-ssl 2. root:~#/usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf **************************************************************************************************** my original httpd.conf file, locate the following directives by scrolling down: Listen xxx SSLEngine On SSLSessionCache dbm:/ramfs/gcache.db SSLSessionCacheTimeout 600 SSLCACertificatePath /etc/frontview/apache SSLCertificateFile /etc/frontview/apache/apache.pem **************************************************************************************************** ONLY changed settings: Listen xxx SSLEngine On SSLSessionCache dbm:/ramfs/gcache.db SSLSessionCacheTimeout 600 SSLCertificateFile /etc/ssl/certs/coolexample.com.crt SSLCertificateKeyFile /etc/ssl/certs/coolexample.key SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt ************************* where xxx is my port, masked for privacy *********************** save and exit, restart apache server, using above commands. visit your site over https:// i hope this is helpful. i wanted to give back to a community from which i have learned and benefited so much. thanks *************************
HOWTO: Prepare a 4TB GPT Drive for Duo/NV+ v2 USB3.0
After experimenting with a bare drive and USB3.0 docking station, I'm able to connect and use a 4TB Drive on a ReadyNAS NV+ v2 USB3.0 port :-D Here are the steps that were used. Notes: The drive connected to the PC was identified as /dev/sdc (determined by fdisk -l). After the drive was partitioned (using parted), it had a single partition. Once partitioned, it was referred to as /dev/sdc1 - where 1 indicates the 1st (and in this case, the only) partition. The commands were executed when logged in as root, if you're not logged in as root, you may have to prefix each command with sudo (super user do) Software: - Linux - Centos 6.2 - Live CD iso here: http://vault.centos.org/6.2/isos/i386/ Hardware: - Seagate ST4000DM000 - Uspeed 6618SUS3 (Anker 68UPSHDDS-BU) USB3.0 & eSATA Hard Drive Docking Station ################################################################################ # fdisk -l ################################################################################ Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table ################################################################################ # parted /dev/sdc ################################################################################ GNU Parted 2.1 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) ################################################################################ # (parted) mklabel gpt ################################################################################ # Comment: if the drive has an existing label, the following message will print # Type Yes ################################################################################ Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes ################################################################################ # (parted) unit TB ################################################################################ ################################################################################ # (parted) mkpart primary 0 -0 ################################################################################ ################################################################################ # (parted) print ################################################################################ Model: ATA ST4000DM000-1F21 (scsi) Disk /dev/sdc: 4.00TB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Flags 1 0.00TB 4.00TB 4.00TB primary ################################################################################ # (parted) quit ################################################################################ Information: You may need to update /etc/fstab. ################################################################################ # mkfs.ext4 /dev/sdc1 ################################################################################ mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=1 blocks, Stripe width=0 blocks 244195328 inodes, 976754176 blocks 48837708 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 29809 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848, 512000000, 550731776, 644972544 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 27 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. ################################################################################ # Comment: # Now you can disconnect the drive from the PC and connect to the ReadyNAS v2 # Some may prefer to use mkfs.ext3 ################################################################################
