thought I had everything going fine. I had the array started and was able to see the tower in finder. Once I opened tower I could see disk 1 and disk 2 as well as flash and cache. I copied and pasted 900 GB of files into disk 1. I wanted to copy certain files into disk 2. When I tried to copy the 500 GB of movies to second disk it said it would take 21 hours. Does this sound right? Thinking that I would start over I just highlighted and deleted all the folders on disk 1. One of the files was labeled photos, from my wifes files. Some how she protected those files from being deleted. I wanted to start with a fresh drive again so I attempted to reformat the disk 1 drive again. I tried using several commands. I shut the system down then logged into root from the server its self. I attempted the run the following /root/samba stop

unmount /dev/md1

md1 I thought was the same disk as disk 1 in the array, it also show sd1 and mdc. these commands did not work.

 

I restarted and stopped the array using unmenu and unmounted the disk. I then went back to the server itself and ran the folowin command mkreiserfs /dev/mdc.  I did get a warning saying it would reformat the whole drive.

 

this reformatted the correct drive but now the array will not start. My syslog is too big to attach all together so I will do it in two posts. here is the top part.

Syslogs

SyslogA.doc

and the rest of the syslog any and all help would be greatly appreciated.

SyslogB.txt

I'm not a lot of help, but when you visit http://tower what do you see?

Also are all your drives listed in the device section of http://tower?

Part of my issues are that I am on a mac so I have to use the ip address. To answer your question. It shows the flash drive.

So when you look at the main screen that normally shows the status of your array it doesn't show any drives at all nor doesn't show anything in devices other than your flash drive?

of sorry I thought you were talking about in finder. Oh boy. Ok on the main.htm page it shows the three drives I have mounted. the wd ears which is the drive I messed with. the other seagate and the other wd 500gb cache. Below it in the command area it says stopped:config valid.

of sorry I thought you were talking about in finder. Oh boy. Ok on the main.htm page it shows the three drives I have mounted. the wd ears which is the drive I messed with. the other seagate and the other wd 500gb cache. Below it in the command area it says stopped:config valid.

 

When the array is stopped you will not see the unRAID server on the network.  Starting the server will bring it back online and you should then be able to get to it again in Finder.

If I click start, nothing happens then I click on devices and come back it says stopped. Both the data drives have green lights flashing.

Next to the size on the disks is says mounting for all three disks. I am able to spin up all the disks manually.

Next to the size on the disks is says mounting for all three disks. I am able to spin up all the disks manually.

You will need to wait until the journal transactions are replayed before you will see the "mounting" complete.

 

It can take as long as 15 minutes or more if they are 2TB disks.

 

Joe L.

OK I will give that a shot. Thanks

This time I have not clicked off f the main page. It still says starting and mountiing.

This time I have not clicked off f the main page. It still says starting and mountiing.

 

The main page will not auto refresh.  Click the refresh button on your browser and see what the screen says.

After refreshing it says "stopped" configuration valid. Nothing in where is said mounting in the past.

 

version[7699]: Linux version 2.6.32.9-unRAID (root@Develop) (gcc version 4.2.3) #8 SMP Wed Nov 24 01:15:59 MST 2010

ls: cannot access /dev/hd[a-z]: No such file or directory

ls: cannot access /dev/hd[a-z]: No such file or directory

/etc/rc.d/rc.unRAID: line 84: /boot/config/shares/*: No such file or directory

status[7750]: State: STOPPED

status[7750]: D#          Model / Serial          Status        Device   

status[7750]: 0      rdevModel.0 / rdevSerial.0    DISK_DSBL_NP  rdevName.

status[7750]: 1  WDC WD20EARS-00 / WD-WCAZA0733471 DISK_OK        sdc     

status[7750]: 2    ST32000542AS / 5XW1JKS4        DISK_OK        sdd     

status[7750]: SMART overall health assessment

ls: cannot access /dev/hd[a-z]: No such file or directory

status[7750]: /dev/sda: SMART overall-health self-assessment test result: PASSED

status[7750]: /dev/sdb: SMART overall-health self-assessment test result: PASSED

status[7750]: /dev/sdc: SMART overall-health self-assessment test result: PASSED

status[7750]: /dev/sdd: SMART overall-health self-assessment test result: PASSED

status[7750]: /dev/sde: SMART Health Status: OK

status[7750]: No active PIDS on the array

/etc/rc.d/rc.unRAID: line 195: echo: write error: Invalid argument

Removing old syslog: /boot/logs/syslog-20101212-105227.txt

Saving current syslog: /boot/logs/syslog-20101223-151213.txt

-rwxrwxrwx 1 root root 143395 Dec 23 15:12 /boot/logs/syslog-20101223-151213.txt

zip not installed. Consider installing to automatically zip current syslog

 

I wonder if I should run "initconfig" ?

OK so I ran the initconfg command. Then the array started and it said the wd ears drive was not formatted. I am formatting it now.

Looks like that got me back to where I started. I only have two erros in the syslog now. Any Ideas

 

Dec 23 16:30:40 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors)

Dec 23 16:30:40 Tower kernel: ide1: DMA disabled (Errors)

Looks like that got me back to where I started. I only have two erros in the syslog now. Any Ideas

 

Dec 23 16:30:40 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors)

Dec 23 16:30:40 Tower kernel: ide1: DMA disabled (Errors)

Since you did not post the entire syslog, no.

 

It could be the drive on that port does not support DMA, or, it could be there is no drive on that port, or, it could be you used a 40 conductor cable where an 80 conductor cable is needed.

Ok. These are all fairly new drives purchased in the last 2 months. I will post the rest of the syslog. I think these errors were present in the logs I posted at the begining of this post however. I will post the latest logs.

syslog.zip

Do you have an IDE drive in there? If not, go into the BIOS and change the SATA mode to AHCI instead if IDE.

 

Here's a hint. You don't have to format a disk to remove some content.

 

Peter

Those DMA messages are not really errors.  They are simply indicating that in your BIOS settings, you do not have DMA enabled for the IDE disk channels.  Since you aren't using any IDE drives, those messages are irrelevant.

 

Your first syslog piece showed that the MBR on Disk 1 (the WD20EARS, md1, sdc) was messed up, reporting an 'unknown partition table'.  Your final syslog was fine.

 

The commands you used do not look right.  It is 'umount' not 'unmount', and it is probably best to use the unRAID web page for that, rather than unmounting an md device.  Also, 'sd1' and 'mdc' are incorrect, should be 'sdc1' and 'md1'.  Also, you would use 'ls' on the file systems, not the drives, use 'ls' on '/dev/[hs]d[a-z]1' rather than '/dev/[hs]d[a-z]'.

 

You obviously have more Linux knowledge than I did when I started.  And you aren't afraid of the command line!

I do not have any ide drives. I will look at the bios next time I boot up. More knowledge... I wish. Right now I have nothing to loose. I haven't transferred any data to the drives. I do read a lot of these posts. I am still trying to plan the best route for me. I am trying to grasp the whole user shares and split level stuff. At some point I have to figure out the Mac/safari //tower issues. Not there yet but I am learning.

Thanks for taking the time out to look at my syslog.

At some point I have to figure out the Mac/safari //tower issues. Not there yet but I am learning.

 

That is covered in the FAQ section of the unRAID wiki.