July 23, 201213 yr Ok, I had to replace my parity drive today, v5 rc5. I did a parity check and zero errors. Powered down, swapped the drives, power up. The array was not started and showed a Red dot next to the missing drive it was looking for, as expected. I selected the new drive as the Parity drive (drop down list). At the bottom next to where it says the array is STOPPED, it says Upgrading Parity... The syslog is jamming by so it must be doing something. hd led light is flashing regularly too. My question is, should I Start the Aray and Start the Partiy Sync, or wait until the Upgrading Parity task is complete? Thanks! post a syslog. As far as I know, it has NOT yet started upgrading parity if the array is not started. It is waiting for you. Joe L. Exactly, as I said it was not started and I wasn't sure if I should start it or wait. I would wait if it was busy doing something. I guess the thing to do was Start it, so I just did. It's building the partiy now..... Update: The parity build process completed with no issues. I'm now running a parity check for the first time on this new parity drive. All good so far... Update: Everything completed fine. The parity drive swap worked with no issues. I have now moved to v5 rc6, so moving on to then next thread...
August 1, 201213 yr hi this is my first time ever testing unRAID, and i'm using the 5.0-rc5. I'm using it on an old PC 5-6 years old... it has realtek NIC RTL8110C/RTL8169, Pentrium 4 @ 2.6 Ghz, 3 GB RAM, and two hard drives, one is SATA 250GB and another is IDE 80GB. As per the configuration tutorial, to ensure that all drives are seen, i tried this command dmesg|grep SATA|grep link but nothing showed up. but anyway, i navigated from my laptop to the IP address of the unRAID system, and the main page loaded. but here are the issues I'm having (dunno, maybe i'm doing something wrong). It's way tooooooooo slow...and i need to click any tab twice for it to load (e.g. Main, Users) when i go to main, in the disks list, i'm able to see both HDDs, so I selected one for disk1 and another for disk2, i dont want a parity for now, i'm just testing unRAID at this stage clicking anything takes time, for example, when clicking "identify" it goes on forever... same with clicking "Refresh" under "Array"... what is going on here, it's really a bad impression on unRAID, as i'm about to spend around $4,000 USD in new system....this giving me doubts! am i doing anything wrong?
August 1, 201213 yr hi As per the configuration tutorial, to ensure that all drives are seen, i tried this command dmesg|grep SATA|grep link but nothing showed up. Obviously, it is based on a different release. There are no lines with the word "SATA" in your system log. am i doing anything wrong? Yes, you did not supply a system log and did not tell us exactly which rc5 release you are using. See here: http://lime-technology.com/forum/index.php?topic=9880.0 It sounds as if you have network issues. If you have to click twice, odds are high you have more than one device on your LAN with the same IP address. Joe L.
August 1, 201213 yr hi As per the configuration tutorial, to ensure that all drives are seen, i tried this command dmesg|grep SATA|grep link but nothing showed up. Obviously, it is based on a different release. There are no lines with the word "SATA" in your system log. am i doing anything wrong? Yes, you did not supply a system log and did not tell us exactly which rc5 release you are using. See here: http://lime-technology.com/forum/index.php?topic=9880.0 It sounds as if you have network issues. If you have to click twice, odds are high you have more than one device on your LAN with the same IP address. Joe L. Hi Joe i did mention im using 5.0-rc5 also, Im sure i dont have a duplicate IP on my network. and this is my full log (attached) log.txt
August 1, 201213 yr hi As per the configuration tutorial, to ensure that all drives are seen, i tried this command dmesg|grep SATA|grep link but nothing showed up. Obviously, it is based on a different release. There are no lines with the word "SATA" in your system log. am i doing anything wrong? Yes, you did not supply a system log and did not tell us exactly which rc5 release you are using. See here: http://lime-technology.com/forum/index.php?topic=9880.0 It sounds as if you have network issues. If you have to click twice, odds are high you have more than one device on your LAN with the same IP address. Joe L. Hi Joe i did mention im using 5.0-rc5 I missed that.... Sorry. also, Im sure i dont have a duplicate IP on my network. and this is my full log (attached) I see address 192.168.1.66 Aug 1 19:23:18 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Aug 1 19:23:18 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Aug 1 19:23:18 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.66 broadcast 192.168.1.255 netmask 255.255.255.0 Aug 1 19:23:18 Tower kernel: r8169 0000:02:04.0: eth0: link down Aug 1 19:23:18 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1 Interesting in that the unRAID "md' driver seems to be re-loading itself very frequently. (several times per second at times. ) We you refreshing the screen at that point? (or playing with assigning and un-assigning disks in the drop-down fields?) Aug 1 19:59:16 Tower emhttp: shcmd (194): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:16 Tower emhttp_event: driver_loaded Aug 1 19:59:37 Tower emhttp: shcmd (195): rmmod md-mod |& logger Aug 1 19:59:37 Tower emhttp: shcmd (196): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:37 Tower kernel: md: unRAID driver removed Aug 1 19:59:37 Tower emhttp: shcmd (197): udevadm settle Aug 1 19:59:37 Tower emhttp: Device inventory: Aug 1 19:59:37 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:37 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:37 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:37 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: initializing superblock Aug 1 19:59:37 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:37 Tower kernel: mdcmd (2): import 1 8,0 78150712 WDC_WD800BB-00DKA0_WD-WCAHL2678640 Aug 1 19:59:37 Tower kernel: md: import disk1: [8,0] (sda) WDC_WD800BB-00DKA0_WD-WCAHL2678640 size: 78150712 Aug 1 19:59:37 Tower kernel: md: disk1 new disk Aug 1 19:59:37 Tower emhttp: shcmd (198): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:37 Tower kernel: mdcmd (3): import 2 8,16 244198552 ST3250823AS_5NF0Y872 Aug 1 19:59:37 Tower kernel: md: import disk2: [8,16] (sdb) ST3250823AS_5NF0Y872 size: 244198552 Aug 1 19:59:37 Tower kernel: md: disk2 new disk Aug 1 19:59:37 Tower emhttp_event: driver_loaded Aug 1 19:59:37 Tower emhttp: shcmd (199): rmmod md-mod |& logger Aug 1 19:59:37 Tower emhttp: shcmd (200): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:37 Tower kernel: md: unRAID driver removed Aug 1 19:59:37 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:37 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: initializing superblock Aug 1 19:59:37 Tower emhttp: shcmd (201): udevadm settle Aug 1 19:59:37 Tower emhttp: Device inventory: Aug 1 19:59:37 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:37 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:37 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:37 Tower kernel: mdcmd (2): import 1 8,0 78150712 WDC_WD800BB-00DKA0_WD-WCAHL2678640 Aug 1 19:59:37 Tower kernel: md: import disk1: [8,0] (sda) WDC_WD800BB-00DKA0_WD-WCAHL2678640 size: 78150712 Aug 1 19:59:37 Tower kernel: md: disk1 new disk Aug 1 19:59:37 Tower emhttp: shcmd (202): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:37 Tower kernel: mdcmd (3): import 2 8,16 244198552 ST3250823AS_5NF0Y872 Aug 1 19:59:37 Tower kernel: md: import disk2: [8,16] (sdb) ST3250823AS_5NF0Y872 size: 244198552 Aug 1 19:59:37 Tower kernel: md: disk2 new disk Aug 1 19:59:37 Tower emhttp_event: driver_loaded Aug 1 19:59:37 Tower emhttp: shcmd (203): rmmod md-mod |& logger Aug 1 19:59:37 Tower emhttp: shcmd (204): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:37 Tower kernel: md: unRAID driver removed Aug 1 19:59:37 Tower emhttp: shcmd (205): udevadm settle Aug 1 19:59:37 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:37 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:37 Tower kernel: md: initializing superblock Aug 1 19:59:37 Tower emhttp: Device inventory: Aug 1 19:59:37 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:37 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:37 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:37 Tower kernel: mdcmd (2): import 1 8,0 78150712 WDC_WD800BB-00DKA0_WD-WCAHL2678640 Aug 1 19:59:37 Tower kernel: md: import disk1: [8,0] (sda) WDC_WD800BB-00DKA0_WD-WCAHL2678640 size: 78150712 Aug 1 19:59:37 Tower kernel: md: disk1 new disk Aug 1 19:59:37 Tower emhttp: shcmd (206): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:37 Tower emhttp_event: driver_loaded Aug 1 19:59:37 Tower kernel: mdcmd (3): import 2 8,16 244198552 ST3250823AS_5NF0Y872 Aug 1 19:59:37 Tower kernel: md: import disk2: [8,16] (sdb) ST3250823AS_5NF0Y872 size: 244198552 Aug 1 19:59:37 Tower kernel: md: disk2 new disk Aug 1 19:59:37 Tower emhttp: shcmd (207): rmmod md-mod |& logger Aug 1 19:59:37 Tower emhttp: shcmd (208): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:38 Tower kernel: md: unRAID driver removed Aug 1 19:59:38 Tower emhttp: shcmd (209): udevadm settle Aug 1 19:59:38 Tower emhttp: Device inventory: Aug 1 19:59:38 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:38 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:38 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:38 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: initializing superblock Aug 1 19:59:38 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:38 Tower kernel: mdcmd (2): import 1 8,0 78150712 WDC_WD800BB-00DKA0_WD-WCAHL2678640 Aug 1 19:59:38 Tower kernel: md: import disk1: [8,0] (sda) WDC_WD800BB-00DKA0_WD-WCAHL2678640 size: 78150712 Aug 1 19:59:38 Tower kernel: md: disk1 new disk Aug 1 19:59:38 Tower emhttp: shcmd (210): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:38 Tower kernel: mdcmd (3): import 2 8,16 244198552 ST3250823AS_5NF0Y872 Aug 1 19:59:38 Tower kernel: md: import disk2: [8,16] (sdb) ST3250823AS_5NF0Y872 size: 244198552 Aug 1 19:59:38 Tower kernel: md: disk2 new disk Aug 1 19:59:38 Tower emhttp_event: driver_loaded Aug 1 19:59:38 Tower emhttp: shcmd (211): rmmod md-mod |& logger Aug 1 19:59:38 Tower emhttp: shcmd (212): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:38 Tower emhttp: shcmd (213): udevadm settle Aug 1 19:59:38 Tower kernel: md: unRAID driver removed Aug 1 19:59:38 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:38 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: initializing superblock Aug 1 19:59:38 Tower emhttp: Device inventory: Aug 1 19:59:38 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:38 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:38 Tower emhttp: shcmd (214): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:38 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:38 Tower kernel: mdcmd (2): import 1 0,0 Aug 1 19:59:38 Tower kernel: mdcmd (3): import 2 0,0 Aug 1 19:59:38 Tower emhttp_event: driver_loaded Aug 1 19:59:38 Tower emhttp: shcmd (215): rmmod md-mod |& logger Aug 1 19:59:38 Tower emhttp: shcmd (216): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 19:59:38 Tower kernel: md: unRAID driver removed Aug 1 19:59:38 Tower emhttp: shcmd (217): udevadm settle Aug 1 19:59:38 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 19:59:38 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 19:59:38 Tower kernel: md: initializing superblock Aug 1 19:59:38 Tower emhttp: Device inventory: Aug 1 19:59:38 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 19:59:38 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 19:59:38 Tower emhttp: shcmd (218): /usr/local/sbin/emhttp_event driver_loaded Aug 1 19:59:38 Tower emhttp_event: driver_loaded Aug 1 19:59:38 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 19:59:38 Tower kernel: mdcmd (2): import 1 0,0 Aug 1 19:59:38 Tower kernel: mdcmd (3): import 2 0,0 Aug 1 20:00:09 Tower emhttp: shcmd (219): rmmod md-mod |& logger Aug 1 20:00:09 Tower emhttp: shcmd (220): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 20:00:09 Tower emhttp: shcmd (221): udevadm settle Aug 1 20:00:09 Tower kernel: md: unRAID driver removed Aug 1 20:00:09 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 20:00:09 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 20:00:09 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 20:00:09 Tower kernel: md: initializing superblock Aug 1 20:00:09 Tower emhttp: Device inventory: Aug 1 20:00:09 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 20:00:09 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 20:00:09 Tower emhttp: shcmd (222): /usr/local/sbin/emhttp_event driver_loaded Aug 1 20:00:09 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 20:00:09 Tower kernel: mdcmd (2): import 1 0,0 Aug 1 20:00:09 Tower kernel: mdcmd (3): import 2 0,0 Aug 1 20:00:09 Tower emhttp_event: driver_loaded Aug 1 20:00:09 Tower emhttp: shcmd (223): rmmod md-mod |& logger Aug 1 20:00:09 Tower emhttp: shcmd (224): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger Aug 1 20:00:09 Tower kernel: md: unRAID driver removed Aug 1 20:00:09 Tower emhttp: shcmd (225): udevadm settle Aug 1 20:00:09 Tower emhttp: Device inventory: Aug 1 20:00:09 Tower emhttp: WDC_WD800BB-00DKA0_WD-WCAHL2678640 (sda) 78150744 Aug 1 20:00:09 Tower emhttp: ST3250823AS_5NF0Y872 (sdb) 244198584 Aug 1 20:00:09 Tower emhttp: shcmd (226): /usr/local/sbin/emhttp_event driver_loaded Aug 1 20:00:09 Tower kernel: md: unRAID driver 2.1.4 installed Aug 1 20:00:09 Tower kernel: read_file: error 2 opening /boot/config/super.dat Aug 1 20:00:09 Tower kernel: md: could not read superblock from /boot/config/super.dat Aug 1 20:00:09 Tower kernel: md: initializing superblock Aug 1 20:00:09 Tower kernel: mdcmd (1): import 0 0,0 Aug 1 20:00:09 Tower kernel: mdcmd (2): import 1 0,0 Aug 1 20:00:09 Tower kernel: mdcmd (3): import 2 0,0
August 1, 201213 yr yah i was, cause it was showing as loading, so i was clicking again over many times. anything else wrong?
August 1, 201213 yr nothing else looks unusual... you should assign a drive and start the array. That should write an initial config/super.dat file. (the one it is complaining about it cannot open, that has not yet been created, since you've not yet defined a disk array)
August 3, 201213 yr Ok, I had to replace my parity drive today, v5 rc5. I did a parity check and zero errors. Powered down, swapped the drives, power up. The array was not started and showed a Red dot next to the missing drive it was looking for, as expected. I selected the new drive as the Parity drive (drop down list). At the bottom next to where it says the array is STOPPED, it says Upgrading Parity... The syslog is jamming by so it must be doing something. hd led light is flashing regularly too. My question is, should I Start the Aray and Start the Partiy Sync, or wait until the Upgrading Parity task is complete? Thanks! post a syslog. As far as I know, it has NOT yet started upgrading parity if the array is not started. It is waiting for you. Joe L. Exactly, as I said it was not started and I wasn't sure if I should start it or wait. I would wait if it was busy doing something. I guess the thing to do was Start it, so I just did. It's building the partiy now..... Update: The parity build process completed with no issues. I'm now running a parity check for the first time on this new parity drive. All good so far... Update: Everything completed fine. The parity drive swap worked with no issues. I have now moved to v5 rc6, so moving on to then next thread... what was the issue that caused your system to not boot?
Archived
This topic is now archived and is closed to further replies.