Ok, it tested out the "if it ain't broke...." saying and suffered this weekend.
I will try and keep it concise but could be a long post.
I have two machines, a workstation (Win7 Pro) and NAS (Fedora 14). Both machines were working fine but there were a few improvements I wished to make.
The workstation was using 2x60GB Vertex IIs striped on an Adaptec raid controller but they were getting slow. 1x WD Black 1TB for storage.
The NAS is in a 20 bay Norco case but I was only able to run one 8 drive LSI raid card on my current motherboard although I had two cards at home. I was also running out of space and had no more available bays. My stripped media array had 3x1TB WD Blacks.
The mission.....
1. Split the 2 Vertex II drives, one for each machine.
2. Put an i3 motherboard and processor in so I can use both LSI cards and use the i3s GPU for video.
3. Transfer the 1TB black from the workstation and and use it to recreate a new stripped array for my media.
4. Transfer a 1.5TB Seagate 7200.11 to the workstation to replace the WD Black.
5. Reinstall Win7 HomeP on the workstation (look at relocating the users and program files to the Seagate drive)
6. Install Fedora 15 to the NAS.
Getting the hardware up and running on the Nas I set about installing Fedora 15. The install process kept failing with a unspecified error (the dvd had been verified). Turns out one of my 2TB WD Green drives was causing issues when in a specific bay in the case. After loosing all the data I moved it to another bay and it worked fine (data was recoverable from my array which the WD Green was a partial backup for). After finally giving in I tried to reinstall Fedora 14 to get an error message that highlighted what was wrong. Fedora 15 also would not install to the Vertex drive as it was detected as part of an array (the Adaptec ray from the WS) and it would not let me clear or use it. I had to boot a live DVD and wipe the partition before the Fedora 15 installer would allow me to install to it.
Finally got Fedora 15 installed and some of the software I usually use is missing. Most notably is the service management gui. Gnome 3 is ok but it does take longer for me to access what I want. I installed Samba 3 and the config gui. I then configured the Samba shares, rebuilt my Win7 machine (big issues moving the program files directories) and tried the shares. Only getting 2MB/s max. Checked my Nas to media player connection with the same result indicating the issue is with the Nas.
I checked all the settings I could think of (Firewall open for Samba and Samba Client, NIC reporting 1Gb network connected, switch reporting 1Gbit link). I finally reverted back to Fedora 14 with difficulty, my original Fedora 14 install DVD now errored with package dependency clashes and there was no link (that I could find) to Fedora 14 on the Fedora website as everything pointed to Fedora 15.
With a little url editing I managed to download and burn a Fedora 14 live DVD and ran an install off of that. Once installed I tried Samba again with the same results. The Service management gui was also still missing. I tried moving the NIC to another PCI slot which saw the speed jump to 40MB/s for around 15 minutes before dropping back to the original 2MB/s max. I tried the M/B NIC but that didn't seem to be detected at all (forget the make but not realtek).
What I have noticed is that I have Samba log files from my old WS are connections on the SSD Fedora boot drive. The SSD came from the WS and when I rebuilt the WS I gave it a new name. My downloads drive used to be my old Nas Fedora 14 boot drive so I am wondering if Fedora 15 tried to upgrade even though I asked for a custom install and changed the boot and root drive to the SSD.
Ok, two questions;
1. How do I get my Samba speeds back to the 70-80MB/s they used to be (internal Nas drive to drive copies are upto 90MB/s so the drives seem fine).
2. Where is the services management gui as I cannot find anything that looks like it in YUM and I found it a lot easier than having to drop to the command line to set services to run on boot or to restart them.
Thanks
RB
I will try and keep it concise but could be a long post.
I have two machines, a workstation (Win7 Pro) and NAS (Fedora 14). Both machines were working fine but there were a few improvements I wished to make.
The workstation was using 2x60GB Vertex IIs striped on an Adaptec raid controller but they were getting slow. 1x WD Black 1TB for storage.
The NAS is in a 20 bay Norco case but I was only able to run one 8 drive LSI raid card on my current motherboard although I had two cards at home. I was also running out of space and had no more available bays. My stripped media array had 3x1TB WD Blacks.
The mission.....
1. Split the 2 Vertex II drives, one for each machine.
2. Put an i3 motherboard and processor in so I can use both LSI cards and use the i3s GPU for video.
3. Transfer the 1TB black from the workstation and and use it to recreate a new stripped array for my media.
4. Transfer a 1.5TB Seagate 7200.11 to the workstation to replace the WD Black.
5. Reinstall Win7 HomeP on the workstation (look at relocating the users and program files to the Seagate drive)
6. Install Fedora 15 to the NAS.
Getting the hardware up and running on the Nas I set about installing Fedora 15. The install process kept failing with a unspecified error (the dvd had been verified). Turns out one of my 2TB WD Green drives was causing issues when in a specific bay in the case. After loosing all the data I moved it to another bay and it worked fine (data was recoverable from my array which the WD Green was a partial backup for). After finally giving in I tried to reinstall Fedora 14 to get an error message that highlighted what was wrong. Fedora 15 also would not install to the Vertex drive as it was detected as part of an array (the Adaptec ray from the WS) and it would not let me clear or use it. I had to boot a live DVD and wipe the partition before the Fedora 15 installer would allow me to install to it.
Finally got Fedora 15 installed and some of the software I usually use is missing. Most notably is the service management gui. Gnome 3 is ok but it does take longer for me to access what I want. I installed Samba 3 and the config gui. I then configured the Samba shares, rebuilt my Win7 machine (big issues moving the program files directories) and tried the shares. Only getting 2MB/s max. Checked my Nas to media player connection with the same result indicating the issue is with the Nas.
I checked all the settings I could think of (Firewall open for Samba and Samba Client, NIC reporting 1Gb network connected, switch reporting 1Gbit link). I finally reverted back to Fedora 14 with difficulty, my original Fedora 14 install DVD now errored with package dependency clashes and there was no link (that I could find) to Fedora 14 on the Fedora website as everything pointed to Fedora 15.
With a little url editing I managed to download and burn a Fedora 14 live DVD and ran an install off of that. Once installed I tried Samba again with the same results. The Service management gui was also still missing. I tried moving the NIC to another PCI slot which saw the speed jump to 40MB/s for around 15 minutes before dropping back to the original 2MB/s max. I tried the M/B NIC but that didn't seem to be detected at all (forget the make but not realtek).
What I have noticed is that I have Samba log files from my old WS are connections on the SSD Fedora boot drive. The SSD came from the WS and when I rebuilt the WS I gave it a new name. My downloads drive used to be my old Nas Fedora 14 boot drive so I am wondering if Fedora 15 tried to upgrade even though I asked for a custom install and changed the boot and root drive to the SSD.
Ok, two questions;
1. How do I get my Samba speeds back to the 70-80MB/s they used to be (internal Nas drive to drive copies are upto 90MB/s so the drives seem fine).
2. Where is the services management gui as I cannot find anything that looks like it in YUM and I found it a lot easier than having to drop to the command line to set services to run on boot or to restart them.
Thanks
RB
. Obviously not my preferred choice.