Hack a Snap Sever 1000?

[blue68f100]

These have been problem childs. Some work some don't.
The best sucess has been with the unit is in JBOD (individual) drives. If an array is set it doesn't work. Even if not present. It remembers drive data.
This works best with just one drive in the server. I had one user say that was the only way it worked.
Once in JBOD. Do one reboot. clears cache
then issue the "co de format 10000 /reinit"
if it is capable of supporting 48bit this is your best bet.
Then check your log as you did before.
Changing the BIOS settings have not worked.
Then install 1 drive at a time. and issiue the format cmd if needed.
Seagates and Hitiachi have worked best.

[firestar2k3]

I have at the moment only one hitachi 250GB drive attached, no others, where shall i start from here? do you have any recommended steps and commands?

Im so desperate for 250GB!!!

[dgoodrich]

Originally Posted by kcrossley

That's pretty interesting. How would you set something like that up? Is it an iTunes collection?

I've got about 40gb of .mp3s, mostly ripped from my own (and friends) CDs. I copied it all over to the Snap last night. It was all ripped using the Lame Encoder with CDex as the GUI front end.

My goal is to free up disk space on my various computers. Currently I have three copies of the music collection, because I am paranoid about losing it all. This means that every time I rip some new CDs, I have to copy the files out to the various computers to keep it all backed up. So I set up the Snap as Raid 1 to provide better data protection, and will maintain one other backup copy on an external hard drive (and I should probably burn it all to DVD-ROM too). Once I am confident that the Snap is reliably set up, I will be able to delete about 40gb each from my home machine and from my notebook.

I have recently started using iTunes because I love the interface. iTunes is a little sluggish over a wireless g connection, but not too bad. It is quite responsive over the 100mb/s LAN. iTunes maintains the music library as a XML database on the local machine. So I thought that once it had built the local database, that searching, sorting, etc. would be just as fast as a local collection. This turns out not to be true because iTunes appears to verify the actual existence of each file as it displays the tracks in its interface. If the network share isn't available, it flags the tracks as unavailable, but fortunately does not delete the database entry.

When I added the tracks to the library by browsing to the network share, I found that iTunes was unacceptably slow using wireless. If I mapped a drive to the network share, and added the tracks by browsing to the drive letter, iTunes seems to be much quicker, and is actually quite usable over a wireless g connection. I've only just started to play with this, so these conclusions are preliminary.

A third party program called "iTunes Library Updater" can update the library when tracks are added to any path you specify. Therefore, I should be able to maintain the files on the Snap (other users will have read-only access to the files), and then update the libraries on each client machine semi-automatically. I've also thought about setting the "my music" location to be on the mapped drive, and then map "M:" on all the computers to the music share. This way, the Library files would be on the Snap. All users would share the same library, and all playlists would be available to everyone. This would probably be very slow, but I plan on trying it.

I don't have an iPod (yet), so I don't know if syncing an iPod will be unreasonaby slow from the network share.

[kcrossley]

Very interesting. I know that some companies are promoting that their NAS solution can do this. One that comes to mind is the N2100P by Thecus. http://www.thecus.com/products_over....e32b2cf4e032f3

Although I don't know very much about this product it seems to be getting fairly good reviews on newegg.com. What Snap Server are you using? Are you using it with a Mac?

[firestar2k3]

Hi all!
Im having a nightmare regards to getting 48bit enabled on my 4100. Please give me any ideas or tips to get this to work, I think this is a newer bios >v2 and I am getting Lba enabled drive but not being used... when i use info log t method..

please give me a shout!

cheers

[re3dyb0y]

Mine now shows
1 for ide 48bitLBACounter get

I presume that means 1 drive over 137GB?

As that is what i have

[blue68f100]

What brand drives are you using?

Check to see what config the missing drives are in. "info devices" if it has records of a drive that does not require 48bit it locks all out. I ran into this with another user, he was at the pont of giving up.

Send me a copy of the "info devices" so I can see if were over looking something.

IF individual, unmount 10000, then try the "co de format 10000 /reinit" again.

Your unit may have one of the promise controllers that has a problem with LBA48. If this is the case there is nothing We can do. One user reported this problem on " hack a snap 1000" thread. You may need to go through that thread to find the post. He gives the chip ID with the problem.

[re3dyb0y]

Call Stack : 
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
 System   1/19/2006   3:16:00 PM  
F  PANIC : Maximum yield time exceeded at $002BCEC4  System   1/19/2006   3:16:00 PM

Anyone got any ideas what it is/was?

[re3dyb0y]

Firestar

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 31792 Private Mounted
Label:Private Contains system files only
Unique Id: 0x75FEAC3C60655D39 Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 131554128 Free (KB): 131422264 Public Mounted
Labelrive1 Single disk
Unique Id: 0x75FEAC3C60655D39 Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133377984 Starting Blk: 104776 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

[firestar2k3]

Hitachi Drive 1x 250GB Brand New.

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 31832 Private Mounted
Label:Private Contains system files only
Unique Id: 0x25C01D1E319BDA4F Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 131554128 Free (KB): 131422296 Public Mounted
Labelrive1 Single disk
Unique Id: 0x25C01D1E319BDA4F Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133377984 Starting Blk: 104776 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed


Im going to unmount then reformat..

Please give any more help if poss!

Thanks!

[blue68f100]

Originally Posted by poogles_uk

Call Stack : 
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
 System   1/19/2006   3:16:00 PM  
F  PANIC : Maximum yield time exceeded at $002BCEC4  System   1/19/2006   3:16:00 PM

Anyone got any ideas what it is/was?

Is this on your 2000 ?
Haven't seen this before, maybe a drive failure in mirror?

[re3dyb0y]

Its my 2200 yeah

No drive mirror, only 1 drive (the WD 250GB)

Just seems to be doing a standard drive check atm, just taking a long time, suppose its because there is a bit of data and a large drive

[re3dyb0y]

I  Jrc: exiting  Unknown   1/19/2006   3:41:13 PM  
I  Jrc.execute() starting  Unknown   1/19/2006   3:41:13 PM  
I  Jrc created  Unknown   1/19/2006   3:41:13 PM  
I  SnapOS.init() executed  Unknown   1/19/2006   3:41:13 PM  
I  SnapExtension Framework 1.2 initialized  Unknown   1/19/2006   3:41:13 PM  
I  No startup snaplets  Unknown   1/19/2006   3:41:13 PM  
I  done  Unknown   1/19/2006   3:41:13 PM  
I  building info for ssl.jar  Unknown   1/19/2006   3:41:12 PM  
I  done  Unknown   1/19/2006   3:41:12 PM  
I  building info for hello.jar  Unknown   1/19/2006   3:41:12 PM  
I  installed security manager  Unknown   1/19/2006   3:41:12 PM  
I  Java: Native methods linked OK  Unknown   1/19/2006   3:41:11 PM  
I  Jrc.main() starting  Unknown   1/19/2006   3:41:11 PM  
I  System Initialization : Initialization Complete! Memory to be released: 22304544 bytes.  System   1/19/2006   3:41:06 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000 
Individual   1/19/2006   3:41:06 PM  
I  File System Check : Cleanup completed...  Disk 10000 
Individual   1/19/2006   3:41:04 PM  
I  File System Check : ***** File system was modified *****  Disk 10000 
Individual   1/19/2006   3:41:04 PM  
I  File System Check : 971 files, 6545315 used, 23398862 free (0 frags, 23398862 blocks, 0.0%% fragmentation)  Disk 10000 
Individual   1/19/2006   3:41:04 PM  
W  File System Check : Clean flag not set in superblock (Fixed)  Disk 10000 
Individual   1/19/2006   3:41:04 PM  
W  File System Check : Modified flag set in superblock (Fixed)  Disk 10000 
Individual   1/19/2006   3:41:04 PM  
W  File System Check : Summary information bad (Salvaged)  Disk 10000 
Individual   1/19/2006   3:36:38 PM  
W  File System Check : Blk(s) missing in bit maps (Salvaged)  Disk 10000 
Individual   1/19/2006   3:36:38 PM  
W  File System Check : Free blk count(s) wrong in superblk (Salvaged)  Disk 10000 
Individual   1/19/2006   3:35:31 PM  
I  File System Check : ** Phase 5 - Check cylinder groups  Disk 10000 
Individual   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 4b - Check backlinks  Disk 10000 
Individual   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 4 - Check reference counts  Disk 10000 
Individual   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 3 - Check connectivity  Disk 10000 
Individual   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 2 - Check pathnames  Disk 10000 
Individual   1/19/2006   3:35:24 PM  
I  File System Check : ** Phase 1b - Rescan for more duplicate blocks  Disk 10000 
Individual   1/19/2006   3:35:24 PM  
I  File System Check : ** Phase 1 - Check blocks and sizes  Disk 10000 
Individual   1/19/2006   3:22:17 PM  
W  File System Check : partition is NOT clean.  Disk 10000 
Individual   1/19/2006   3:22:17 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000 
Individual   1/19/2006   3:22:17 PM  
I  File System : Opened FDB for device 0x10006  Disk (Priv)   1/19/2006   3:22:17 PM  
I  File System Check : partition is clean.  Disk (Priv)   1/19/2006   3:22:17 PM  
I  File System Check : Executing fsck /dev/ride0g /fix /fixfatal  Disk (Priv)   1/19/2006   3:22:17 PM  
I  INIT: Setting IP address to 192.168.0.200  Network   1/19/2006   3:21:21 PM  
S  System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:55
Boot Count: 223  System   1/19/2006   3:21:21 PM  
F  Call Stack : 
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
 System   1/19/2006   3:16:00 PM  
F  PANIC : Maximum yield time exceeded at $002BCEC4  System   1/19/2006   3:16:00 PM

Drive Log

  File System : Opened FDB for device 0x10000  Disk 10000   1/19/2006   3:41:06 PM  
I  File System Check : Cleanup completed...  Disk 10000   1/19/2006   3:41:04 PM  
I  File System Check : ***** File system was modified *****  Disk 10000   1/19/2006   3:41:04 PM  
I  File System Check : 971 files, 6545315 used, 23398862 free (0 frags, 23398862 blocks, 0.0%% fragmentation)  Disk 10000   1/19/2006   3:41:04 PM  
W  File System Check : Clean flag not set in superblock (Fixed)  Disk 10000   1/19/2006   3:41:04 PM  
W  File System Check : Modified flag set in superblock (Fixed)  Disk 10000   1/19/2006   3:41:04 PM  
W  File System Check : Summary information bad (Salvaged)  Disk 10000   1/19/2006   3:36:38 PM  
W  File System Check : Blk(s) missing in bit maps (Salvaged)  Disk 10000   1/19/2006   3:36:38 PM  
W  File System Check : Free blk count(s) wrong in superblk (Salvaged)  Disk 10000   1/19/2006   3:35:31 PM  
I  File System Check : ** Phase 5 - Check cylinder groups  Disk 10000   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 4b - Check backlinks  Disk 10000   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 4 - Check reference counts  Disk 10000   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 3 - Check connectivity  Disk 10000   1/19/2006   3:35:25 PM  
I  File System Check : ** Phase 2 - Check pathnames  Disk 10000   1/19/2006   3:35:24 PM  
I  File System Check : ** Phase 1b - Rescan for more duplicate blocks  Disk 10000   1/19/2006   3:35:24 PM  
I  File System Check : ** Phase 1 - Check blocks and sizes  Disk 10000   1/19/2006   3:22:17 PM  
W  File System Check : partition is NOT clean.  Disk 10000   1/19/2006   3:22:17 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/19/2006   3:22:17 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/19/2006   2:11:42 PM  
I  File System Check : partition is clean.  Disk 10000   1/19/2006   2:11:42 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/19/2006   2:11:42 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/19/2006   7:29:36 AM  
I  File System : Extended Rights Backup for device 0x10000 has completed successfully  Disk 10000   1/19/2006   3:01:07 AM  
I  File System : Extended Rights Backup for device 0x10000 has begun  Disk 10000   1/19/2006   3:01:05 AM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   8:51:52 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   8:51:52 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   8:51:52 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   8:47:59 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   8:35:12 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   8:35:12 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   8:35:12 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   8:32:46 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   8:16:18 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   8:16:18 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   8:16:18 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   8:13:40 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   8:10:36 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   8:10:36 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   8:10:36 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   7:54:19 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   7:51:31 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   7:51:31 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   7:51:31 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   7:48:52 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   7:42:48 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   7:42:48 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   7:42:48 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   7:27:49 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   7:23:52 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   7:23:52 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   7:23:52 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   7:18:26 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   7:13:22 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   7:13:22 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   7:13:22 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   7:09:46 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   6:26:40 PM  
I  File System Check : partition is clean.  Disk 10000   1/18/2006   6:26:40 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   6:26:40 PM  
I  File System : Closed FDB for device 0x10000  Disk 10000   1/18/2006   6:14:32 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000   1/18/2006   1:44:57 PM  
I  File System Check : Cleanup completed...  Disk 10000   1/18/2006   1:44:54 PM  
I  File System Check : 1018 files, 7989412 used, 1581762 free (0 frags, 1581762 blocks, 0.0%% fragmentation)  Disk 10000   1/18/2006   1:44:54 PM  
W  File System Check : Clean flag not set in superblock (Fixed)  Disk 10000   1/18/2006   1:44:54 PM  
W  File System Check : Modified flag set in superblock (Fixed)  Disk 10000   1/18/2006   1:44:54 PM  
I  File System Check : ** Phase 5 - Check cylinder groups  Disk 10000   1/18/2006   1:42:21 PM  
I  File System Check : ** Phase 4b - Check backlinks  Disk 10000   1/18/2006   1:42:21 PM  
I  File System Check : ** Phase 4 - Check reference counts  Disk 10000   1/18/2006   1:42:19 PM  
I  File System Check : ** Phase 3 - Check connectivity  Disk 10000   1/18/2006   1:42:19 PM  
I  File System Check : ** Phase 2 - Check pathnames  Disk 10000   1/18/2006   1:42:17 PM  
I  File System Check : ** Phase 1b - Rescan for more duplicate blocks  Disk 10000   1/18/2006   1:42:17 PM  
I  File System Check : ** Phase 1 - Check blocks and sizes  Disk 10000   1/18/2006   1:39:34 PM  
W  File System Check : partition is NOT clean.  Disk 10000   1/18/2006   1:39:33 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000   1/18/2006   1:39:33 PM

I think it just mis wrote it

[re3dyb0y]

And i think it just did it again!

[firestar2k3]

I dont know if im ever going to get LBA 48Bit >137GB to work!

I tried unmount, then remount, then co de reinit...but still 130gb showing up!

Time to call it a day....?

[re3dyb0y]

Strange thing with mine, it was fine moving 40gb last night.....

I wonder if its just not enough ram for movign large files

[re3dyb0y]

W  File System Check : Clean flag not set in superblock (Fixed)  Disk 10000   1/19/2006   4:10:44 PM  
W  File System Check : Modified flag set in superblock (Fixed)  Disk 10000   1/19/2006   4:10:44 PM  
W  File System Check : Free blk count(s) wrong in superblk (Salvaged)  Disk 10000   1/19/2006   4:06:18 PM

W  File System Check : Clean flag not set in superblock (Fixed)  Disk 10000   1/19/2006   3:41:04 PM  
W  File System Check : Modified flag set in superblock (Fixed)  Disk 10000   1/19/2006   3:41:04 PM  
W  File System Check : Summary information bad (Salvaged)  Disk 10000   1/19/2006   3:36:38 PM  
W  File System Check : Blk(s) missing in bit maps (Salvaged)  Disk 10000   1/19/2006   3:36:38 PM  
W  File System Check : Free blk count(s) wrong in superblk (Salvaged)  Disk 10000   1/19/2006   3:35:31 PM

This has come up a few times

After checking, it seems it only has 22mb of ram

lol

Im gonna try moving one file at a time, see what happens

[blue68f100]

It sounds like you may have a ram failure. I thought 32 meg was the mimimun for a 2200.

As you know some units don't like WD or Maxtor drives. Try a Seagate or Hitachi drive.

How come you only have 1 drive in the 2200?

I just read a knowledge base article on the 2200 saying that it will boot from either drive. That should be true for any system running raid1.

[blue68f100]

Originally Posted by firestar2k3

I dont know if im ever going to get LBA 48Bit >137GB to work!

I tried unmount, then remount, then co de reinit...but still 130gb showing up!

Time to call it a day....?

Can you issue the format comand with it un-mounted?

[re3dyb0y]

Its done it again (3rd Time!)

Well, i can adn will try the other motherboard ive got for a 2200

I bought the WD drive, and i dont have any other larger drives. That are IDE anyway

Maybe it would be worth sticking my 2 80gb's back in and transferring some files to see if i get the same problem?

I only have one drive as i bought 1 drive to try it. A 250Gb IDE isn't much use as S-ATA is faster. And if that hadn't have worked in my snap, i had a buyer for it, who has a SAN with the WD drives in and wanted a 2nd

Also, i had Memory 22578576 bytes written down before, so i presume that is right!

Will also try copying large files from the snap and such



Strange thing is there were no problems last night

[re3dyb0y]

Seems fine just copying files from the snap server with my 250GB

[firestar2k3]

Originally Posted by blue68f100

What brand drives are you using?

Check to see what config the missing drives are in. "info devices" if it has records of a drive that does not require 48bit it locks all out. I ran into this with another user, he was at the pont of giving up.

Send me a copy of the "info devices" so I can see if were over looking something.

IF individual, unmount 10000, then try the "co de format 10000 /reinit" again.

Your unit may have one of the promise controllers that has a problem with LBA48. If this is the case there is nothing We can do. One user reported this problem on " hack a snap 1000" thread. You may need to go through that thread to find the post. He gives the chip ID with the problem.

OK, Its unmounted again, but the co de format 10000 /reinit does not work...

I get the following error...

Invalid device id 10000 requested

------------
Command returned with console error 1.


what else shall I try, I have thought about giving up and calling it a day, putting 60's in and getting rid of the box... unless you think its possible to get LBA...god knows how....

[dgoodrich]

Originally Posted by kcrossley

Very interesting. I know that some companies are promoting that their NAS solution can do this. One that comes to mind is the N2100P by Thecus. http://www.thecus.com/products_over....e32b2cf4e032f3

Although I don't know very much about this product it seems to be getting fairly good reviews on newegg.com. What Snap Server are you using? Are you using it with a Mac?

I am using a Snap 2000 with two 80gb drives configured as Raid 1. No, I have no Macs on my network.

I saw some of the N2100P on eBay when I bought my Snap, but they were too pricy for me. That said, the iTunes server feature of that device looks pretty cool. Basically, it maintains its own database of tracks on the server, and mimics a computer on the network that is sharing its collection through the standard iTunes sharing.

So far, I am pretty happy with how the Snap works with iTunes. I played with it again last night, and I am able to browse, search and play my collection through the wireless g connection quite well. Simply create a share for your music files on the snap, map that share as a drive on the local machine, load the files into this share, and use the "File>Add folder to Library..." to import the tracks on the mapped drive into the libaray.

[re3dyb0y]

Gonna try the old drives back in, and try swapping the ide cables

Its fine transferring large amounts of files to a pc

[re3dyb0y]

I've solved one thing that was annoying me

The fan didnt come on straight away, move power cable for fan from the secondary power slot to the primary, and it comes on at inital boot

Boot time is a lot longer now for some reason