Any hints tips or tricks?  Do I move everything at once or just the USB thumb drive first get it going and then move the drives (all together?).  I am afraid if I move just the USB thumb drive and the drives on a subsequent reboot unraid is going to say WOAH I lost all my drives?!

 

Thanks!

 

Neil

 

Any hints tips or tricks?  Do I move everything at once or just the USB thumb drive first get it going and then move the drives (all together?).  I am afraid if I move just the USB thumb drive and the drives on a subsequent reboot unraid is going to say WOAH I lost all my drives?!

 

Thanks!

 

Neil

 

 

I am confused at what you are talking about and what you are trying to accomplish.

 

If you are moving stuff to a new motherboard/system just plug everything in and start the server up.  unRAID should tell you what drives go where and you may have to reassign them on the devices page, but you should be fine.

Totally new system with different chassis.  I moved the USB and next the drives.  Testing now.

None of the devices were assigned.  I assigned all the devices and I have green balls next to each of them.  Problem is now I can't get the array to start.  I click start and it says starting.  When I refresh is says configuration is valid and the start button is back?

From syslog:

 

Apr 15 09:52:46 Storage kernel: mdcmd (1): set md_num_stripes 1280 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (2): set md_write_limit 768 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (3): set md_sync_window 288 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (4): set spinup_group 0 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (5): set spinup_group 1 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (6): set spinup_group 2 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (7): set spinup_group 3 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (: set spinup_group 4 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (9): set spinup_group 5 0 (unRAID engine)

Apr 15 09:52:46 Storage kernel: mdcmd (10): set spinup_group 6 0 (unRAID engine)

Apr 15 09:52:56 Storage emhttp: shcmd (28): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (29): /usr/local/sbin/set_ncq sdc 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (30): /usr/local/sbin/set_ncq sdb 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (31): /usr/local/sbin/set_ncq sdd 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (32): /usr/local/sbin/set_ncq sde 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (33): /usr/local/sbin/set_ncq sdg 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: shcmd (34): /usr/local/sbin/set_ncq sdh 1 >/dev/null (Drive related)

Apr 15 09:52:56 Storage emhttp: mdcmd: write: No such device or address (Other emhttp)

Apr 15 09:52:56 Storage kernel: mdcmd (11): start STOPPED (unRAID engine)

Apr 15 09:52:56 Storage kernel: md: do_run: lock_rdev error: -6 (Errors)

Apr 15 09:52:56 Storage emhttp: shcmd (35): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)

Apr 15 09:52:56 Storage emhttp: shcmd (36): cp /etc/exports- /etc/exports (Other emhttp)

Apr 15 09:52:56 Storage emhttp: shcmd (37): killall -HUP smbd (Minor Issues)

Apr 15 09:52:56 Storage emhttp: shcmd (38): /etc/rc.d/rc.nfsd restart | logger (Other emhttp)

Apr 15 09:53:13 Storage emhttp: shcmd (39): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (40): /usr/local/sbin/set_ncq sdc 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (41): /usr/local/sbin/set_ncq sdb 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (42): /usr/local/sbin/set_ncq sdd 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (43): /usr/local/sbin/set_ncq sde 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (44): /usr/local/sbin/set_ncq sdg 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: shcmd (45): /usr/local/sbin/set_ncq sdh 1 >/dev/null (Drive related)

Apr 15 09:53:13 Storage emhttp: mdcmd: write: No such device or address (Other emhttp)

Apr 15 09:53:13 Storage kernel: mdcmd (12): start STOPPED (unRAID engine)

Apr 15 09:53:13 Storage kernel: md: do_run: lock_rdev error: -6 (Errors)

Apr 15 09:53:13 Storage emhttp: shcmd (46): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)

Apr 15 09:53:13 Storage emhttp: shcmd (47): cp /etc/exports- /etc/exports (Other emhttp)

Apr 15 09:53:13 Storage emhttp: shcmd (48): killall -HUP smbd (Minor Issues)

Apr 15 09:53:13 Storage emhttp: shcmd (49): /etc/rc.d/rc.nfsd restart | logger (Other emhttp)

Apr 15 09:54:54 Storage emhttp: shcmd (50): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (51): /usr/local/sbin/set_ncq sdc 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (52): /usr/local/sbin/set_ncq sdb 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (53): /usr/local/sbin/set_ncq sdd 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (54): /usr/local/sbin/set_ncq sde 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (55): /usr/local/sbin/set_ncq sdg 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: shcmd (56): /usr/local/sbin/set_ncq sdh 1 >/dev/null (Drive related)

Apr 15 09:54:54 Storage emhttp: mdcmd: write: No such device or address (Other emhttp)

Apr 15 09:54:54 Storage kernel: mdcmd (13): start STOPPED (unRAID engine)

Apr 15 09:54:54 Storage kernel: md: do_run: lock_rdev error: -6 (Errors)

Apr 15 09:54:54 Storage emhttp: shcmd (57): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)

Apr 15 09:54:54 Storage emhttp: shcmd (58): cp /etc/exports- /etc/exports (Other emhttp)

Apr 15 09:54:54 Storage emhttp: shcmd (59): killall -HUP smbd (Minor Issues)

Apr 15 09:54:54 Storage emhttp: shcmd (60): /etc/rc.d/rc.nfsd restart | logger (Other emhtt

Please any idea why it won't start up?! Kids are getting home from school soon and the movies are on this machine 

Apr 15 13:31:25 Storage kernel: mdcmd (20): spindown 0 (Routine)

Apr 15 13:31:25 Storage kernel: mdcmd (21): spindown 1 (Routine)

Apr 15 13:31:26 Storage kernel: mdcmd (22): spindown 2 (Routine)

Apr 15 13:31:26 Storage kernel: mdcmd (23): spindown 3 (Routine)

Apr 15 13:31:27 Storage kernel: mdcmd (24): spindown 4 (Routine)

Apr 15 13:31:27 Storage kernel: mdcmd (25): spindown 5 (Routine)

Apr 15 13:31:28 Storage kernel: mdcmd (26): spindown 6 (Routine)

Apr 15 13:31:31 Storage emhttp: shcmd (30): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (31): /usr/local/sbin/set_ncq sdc 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (32): /usr/local/sbin/set_ncq sdb 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (33): /usr/local/sbin/set_ncq sdd 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (34): /usr/local/sbin/set_ncq sde 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (35): /usr/local/sbin/set_ncq sdf 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: shcmd (36): /usr/local/sbin/set_ncq sdh 1 >/dev/null (Drive related)

Apr 15 13:31:31 Storage emhttp: mdcmd: write: No such device or address (Other emhttp)

Apr 15 13:31:31 Storage kernel: mdcmd (27): start STOPPED (unRAID engine)

Apr 15 13:31:31 Storage kernel: md: do_run: lock_rdev error: -6 (Errors)

Apr 15 13:31:31 Storage emhttp: shcmd (37): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)

Apr 15 13:31:31 Storage emhttp: shcmd (38): cp /etc/exports- /etc/exports (Other emhttp)

Apr 15 13:31:31 Storage emhttp: shcmd (39): killall -HUP smbd (Minor Issues)

Apr 15 13:31:31 Storage emhttp: shcmd (40): /etc/rc.d/rc.nfsd restart | logger (Other emhttp)

 

Apr 15 13:31:31 Storage kernel: mdcmd (27): start STOPPED (unRAID engine)

Apr 15 13:42:30 Storage kernel: mdcmd (28): start STOPPED (unRAID engine)

 

Is what I get in the logs everyime I attempt a start?

Attach a complete syslog.

 

Looks very similar.

http://lime-technology.com/forum/index.php?topic=11886.msg113404#msg113404

Syslog

syslog-2011-04-15.txt.zip

This server is down. I rebooted without the drives and put the old drives in while off and powered up.  None of them assigned themselves so then I selected those drives as they were assigned before.  That was a-ok except I dropped off my cache drive and didn't move it.

 

I put each drive in the same place if it matters.  Still nothing?

First of all I see that you are running several Seagate LP drives with firmware CC34.  That's a good way to get an early drive failure (it happened to me).  I recommend that you upgrade each drive (one at a time) to CC35.  More details here.

 

Secondly, have you rebooted the new server since the migration?  The solution might be as simple as that.  It sounds to me like the unRAID web server is freaking out and not sending the correct 'start the array' command.  I've seen that once or twice as well.

 

Removing the cache drive shouldn't matter.  As long as all the array drives are present and the parity drive is assigned to the correct slot, then unRAID should be able to start normally.

Rebooted a couple times and still nothing.  No one told me about that firmware issue.  I would like to get everything up and running and then I guess I can deal with the firmware problemo?!

 

Please help

I would lie if I said I copied the config.  The way I assigned the drives was when I rebooted the server said drive missing and read it's serial.  I believe that is ok because it was reading it from the config.  Does that make sense?

I don't know if the array has to be up and running to access the drives via SMB or whatever the sharing technology is but I only have flash when I map over to it from a windows server

Yes that makes sense, and that is fine to do.  I agree that you should solve this issue first, then worry about the firmware thing later.

 

Do you have any add-ons running?  If so, disable them for now (comment them out in your go script) until we can get at least stock unRAID running.

 

Did you make any modifications to the flash drive, or did you simply unplug it from one server and plug it into the other?  The syslog indicates that there might be an issue with your smb-shares.conf file.  Perhaps it was corrupted?  Do you have any complicated shares settings that would be a pain to lose?  I'm tempted to have you just reformat the flash drive and start over with a clean unRAID install, but you would lose all your settings and add-ons by doing that.  Don't take any action just yet.

 

Yes, the array does have to be up and running for any of your shares (besides the flash) to work.

Ok no changes to the flash drive between the two machines and the original machine was a clean shutdown fyi.

 

I have some stuff installed like SSH and some other packages if they matter?

 

The share settings wouldn't be totally miserable.  I do have a backup that I made but it might be pre 4.7 update.  I did recently replace a drive that was suspect (so surprise now given what you said about the firmware).

 

What should I do?

 

You think it is unraid crapping the bed?

I'm not convinced this is unRAID's fault, I suspect your SSH add-on.  I'm no syslog expert, but here's what yours is telling me:

 

1) Everything is normal up to the point where emhttp (unRAID's web server) starts

 

2) emhttp reports this error:

Apr 15 10:16:18 Storage emhttp: mdcmd: write: No such device or address
Apr 15 10:16:18 Storage kernel: mdcmd (19): start STOPPED
Apr 15 10:16:18 Storage kernel: md: do_run: lock_rdev error: -6
Apr 15 10:16:18 Storage emhttp: shcmd (26): rm /etc/samba/smb-shares.conf >/dev/null 2>&1
Apr 15 10:16:18 Storage emhttp: shcmd (27): cp /etc/exports- /etc/exports
Apr 15 10:16:18 Storage emhttp: shcmd (28): killall -HUP smbd
Apr 15 10:16:18 Storage emhttp: shcmd (29): /etc/rc.d/rc.nfsd restart | logger

I don't know exactly what that means, but it seems to be saying that there's something wrong with the smb-shares.conf file

 

3) Immediately following that there about a page of SSHD errors.  If SSHD relies on the shares and the shares aren't starting, then that would make sense.  Or it could be that SSHD is causing the emhttp errors.  Chicken and egg scenario, and I don't know enough to tell you which is the case.  Still, standard operating procedure in troubleshooting unRAID is to first disable all add-ons...

 

4) smb-shares.conf file errors then repeat at the end.

 

First off, you may want to wait for Joe L. (might want to PM him directly) or someone who is more experienced at interpreting syslogs.  If you want to jump right into action, here's what I would do:

 

1) Make a backup of your entire flash drive onto another computer (or if you have another flash drive handy, then start using that one instead).

2) Edit your go script (use notepad++) and comment out everything except the first three lines with a preceding # (alternatively, you could download unRAID 4.7 again and extract just the go script onto your flash drive and overwrite your current one).

3) Reboot and see what happens.  If unRAID starts right up, then you know the issue resides with SSH (or some other add-on).  If not, then there's something wrong with unRAID itself.

 

Try the above three steps and we'll take it from there.

I removed everything from the GO file even the emhttp part.  so I went in and tried to run it and I get a warning that says:

 

can not make directory /boot/config/shares no such file or directory.

 

Does this help?

 

Also how can I shutdown cleanly from the command line? Thanks!

Yes I am doing that.  I copied the bzroot and bzimage and the go files from the clean install.  The rest I got from my backup before all this mess.  Let's see!

Ok things are a bit ugly.  I used the config with the old drive.  I do not want to start and rebuild So which file should I restore from my most recent backups so I have the write driv config?

 

Thanks!

 

Neil

 

super.dat contains your parity info.  It is probably best to copy your entire backed up config folder and just replace the go script with the clean one.

First of all, slow down and approach thing SLOWLY instead of this jumping around disconnecting and connecting and reformatting and so on crap as fast as possible hoping a solution magically falls from the sky. Otherwise, you're going to screw yourself. To be more exact, your problem has nothing to do with the flash drive so you might really screw yourself if you overwrite the config on the flash drive.

 

Do you still have the original flash with the original config? If you have not yet trashed it then leave it alone.

 

Boot the machine and run this command.

 

fdisk -l /dev/sdX

 

Replace the X with the letters a, b, c etc. On the devices page you will see this device reference, for example (sda). Do the command for every hard drive.

 

Here is an example of the results you are looking for on a 2T drive;

 

Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders
Units = cylinders of 63 * 512 = 32256 bytes
Disk identifier: 0x00000000

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               2    62016336  1953514552   83  Linux
Partition 1 does not end on cylinder boundary.

 

The last time that "md: do_run: lock_rdev error: -6" occurred in a syslog was caused by the MBR missing from a disk. So, run those commands and let us know what you find.

 

Peter

 

Can the mbr be fixed and retain data?

How about we figure out where the issue is first before worrying about fixing it?

 

The command should be fdisk -l. I put a space between the dash and the l.

 

Peter

Fair enough. I'm on the run so that was all I could right now.