|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
Thread Tools |
04-11-2006, 11:09 AM | #1 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
2200 w/dead drive
I am sooo happy to find this forum. You folks are doing good work. It astounds me that adaptec will sell a device and when it is out of warranty and not working not offer any hardware support even if you are willing to pay for it. But enough rant.
I have a 2200 with 2x160g, o/s v4, using Raid 1, and one drive died. I believe it's the top one. I haven't cracked it open to verify but that's what it looks like from the debug command. The device is working fine at the moment, meaning that it boots and the data is accessible. The only issue is the dead drive and lack of mirroring. I want to go ahead and upgrade the drives while I am at it. First, I want to verify exactly what type of drive will work. I can get a good price on a WD Caviar SE16 250GB Hard Drive 7200RPM, Internal, SATA-300. Are these specs that will work in my 2200? Presuming it's the top drive that is dead, can I simply replace the top drive with a larger one, mirror the data up, replace the bottom drive with a larger one, and mirror the data down? Thanks in advance for your help! |
04-11-2006, 03:54 PM | #2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
The 2200 uses IDE (ATA100) drives, EIDE cause problems. I know of no one that has installed 500gig drives, several have done 300, one was thinking about 400's.
The top drive has a ID of 10000, Bottom 10010, raid 1 drive id is 50000. There are several sub slices/partitions also. if you had an email sent by your snap it should have indicated which drive. If not the log will show. If you install a new drive it will format the drive but will not mirror (report as orphan) till you issue a cmd to mirror. Check the wiki section out for detailed instructions. Replace, mirror, fail and replace, then remirror will work, but is a slow process. As a rule of thumb you should backup your data before you proceed. Allway safe than sorry. If you break the raid back to JOBD, all data will be on the top 10000 drive. One the 2200, you can move the drive to a different position, if needed. If you change to raid 1, all data on the second/bottom 10010 drive will be lost.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
04-11-2006, 11:03 PM | #3 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Great, thanks. I'm going to get Seagate 300gb ATA/100 drives.
I have confirmed that it's the 10000 drive that has failed. If I understand correctly, my procedure will be: replace the 160gb 10000 drive with the new 300gb drive co de format 10000 /reinit reboot the snap and wait for the reformat to complete co de config mirror 10010 10000 reboot the snap and wait for the mirroring process to complete Is all that correct? |
04-12-2006, 07:11 AM | #4 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Whoops, I woke up this morning and realized I left off some steps on the procedure. I think it should be:
replace the failed 160gb 10000 drive with the new 300gb drive co de format 10000 /reinit reboot the snap and wait for the reformat to complete co de config mirror 10010 10000 reboot the snap and wait for the mirroring process to complete replace the good 160gb 10010 drive with a new 300gb drive co de format 10010 /reinit reboot the snap and wait for the reformat to complete co de config mirror 10000 10010 reboot the snap and wait for the mirroring process to complete Now, is *that* correct? |
04-12-2006, 08:26 AM | #5 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
HAVE YOU BACKED UP YOUR DATA????????
IF NOT DO SO NOT NOW, NOT RESPONSABLE FOR LOST DATA Correct = NO After replacing the drive, login and see if the new drive is being formated. If so allow. After format is complete is should show up as a orphan drive, if so jump to step 4. if not execute step 2. 2. Execute the following command from the ipaddress/config/debug web page. Note: DD is the number of the problem hard disk. Yours is 10000 co de format 100DD /reinit (After reboot, this configures 100DD as a SINGLE drive and FORMATS it.) 3. Reboot the Snap server. 4. After the ORPHANED disk is formatted, execute this command from the ipaddress/config/debug page. co de config mirror 100SS 100DD (yours will be "co de config mirror 10010 10000" SS is the source disk, DD is the destination disk. (This step mirrors the drive with data to the drive without data.) 5. Reboot the Snap. If everything works according to plan, the View Disk Status page should report ?Rebuilding backup disk? when it comes back online. This may fail due to 2 different size drives These instructions are from the wiki section http://wiki.procooling.com/index.php...air_for_Orphan
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
04-12-2006, 09:29 AM | #6 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Ok, got it. Thanks. Data is backed up already, the copy took 4 hours.
Will let you know how it turns out. |
04-14-2006, 06:30 PM | #7 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Ok, I have the drive installed.
The Snap is not responding to ip_address/config, and I cannot ping it. The system and disk lights are blinking slow and concurrently indicating the system is in diagostic mode, the link light is on steady, and the disk light is blinking irregularly. If I unplug the new drive, then the Snap responds normally, and all the data is fine. With the new drive plugged in, it is not on the network. The drive I have installed, for reference, is a Seagate Ultra ATA/100, 7200 rpm, 16 mb cache, 3.5 inch. Any ideas for next steps? |
04-14-2006, 08:59 PM | #8 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
Is the drive jumper set to master?
When the new drive is installed, it will take sometime for it to format. But after 10-15 min you should be able to connect. I think the different drive size may be causing a problem. Option 2. Move the good Snap drive to the top 10000 position. New drive not installed. Change to disk setup to JBOD. NO RAID. All data should be intact. Power down and install/ connect the new drive. Powerup Check drive status, should be formatting new HD
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
04-15-2006, 12:17 AM | #9 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
The jumper was set to CS. I reset the jumper to master, but still no go, same result as above. I notice now that there are no jumpers set on the good WD 160g disk. Could that be a factor?
Switched the drives so that the good 160g drive is in the 10000 position and booted with the new drive not plugged in so I could switch to JBOD configuration. Under the Configure Disks option is the message: "The disk configuration cannot be changed. This server's disks are currently configured for data protection (mirroring) and one of the disks has failed. Please contact Snap Server Technical Support." That's a laugher. I booted with the good 160g WD drive at 10000 and the new 300g disk at 10010 and the new drive formatted on its own. Configure Disks still has the same message as above. The command to mirror the disks fails with an error message (I forgot to copy it). The Snap boots with no problem with the newly formatted 300g disk plugged in at 10010 and the good 160g disk at 10000 disconnected. My current plan is to make a new backup of the data (the original backup is at the office), replace the good 160g disk with a new 300g disk, let the Snap format it, establish the mirror configuration, and restore from the backup. Further comments are welcome as always. |
04-15-2006, 02:24 AM | #10 | |
Cooling Savant
Join Date: Aug 2004
Location: UK
Posts: 909
|
Re: 2200 w/dead drive
Quote:
__________________
Snap Server Help Wiki - http://wiki.procooling.com/index.php/Snap_Server Snap Server 2200 v3.4.807 2x 250GB Seagate Barracuda 7200.9 w/ UNIDFC601512M Replacement Fan "Did you really think it would be that easy??" Other NAS's 1x NSLU2 w/ 512mb Corsair Flash Voyager Running Unslung 6.8b 1x NSLU2 w/ 8Gb LaCie Carte Orange Running Debian/NSLU2 Stable 4.0r0 250GB LaCie Ethernet Disk Running Windows XP Embedded |
|
04-15-2006, 10:25 AM | #11 | |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Quote:
Do you think setting it to master would do the trick? Also, is there a debug command to set the WD to JBOD configuration since I can't do it through the Snap UI? |
|
04-15-2006, 12:00 PM | #12 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
If you can force it to master go ahead.
From debug enter "co de config individual /force" it should break the raid set. Then copy the data to the new drive.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
04-15-2006, 12:37 PM | #13 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
I think no jumpers on this WD drive indicates a single master and a jumper in the middle indicates a master with a slave present, which I don't think is what we want.
That command returns: "04/15/2006 12:18:47 Command: co de config individual /force 'Individual' JBOD devices require a single Logical Device Id or a Public Partition Id ------------ Command returned with console error 1." Is that a syntax error, or something else? Below is my current configuration. Anything else you can think of? "4/15/2006 12:20:26 Command: co de info Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22432 Private Mounted Label:Private Contains system files only Unique Id: 0x383225CC23B21F7D 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): 156290560 Fixed Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 22544 Private Mounted Label:Private Contains system files only Unique Id: 0x3040E75C77ABEE4A Mount: /pri2 Index: 13 Order: 1 Partition: 10016 Physical: 10017 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10017 Drive Slot: 2 IDE Size (KB): 293036032 Fixed Logical Device: 10010 Position: 1 JBOD Size (KB): 287482384 Free (KB): 287194592 Public Mounted Labelrive2 Single disk Unique Id: 0x3040E75C77ABEE4A Mount: /2 Index: 2 Order: 2 Partition: 10010 Physical: 10017 FS Size (KB): 291467920 Starting Blk: 195886 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 293036032 Fixed Logical Device: 50000 Position: 2 MIRROR_CRACKED Size (KB): 153281104 Free (KB): 89033760 Public Mounted Label:Mirror Data protection disk Unique Id: 0x6B4B6DB62268786E Mount: /0 Index: 0 Order: 3 Partition: 10000 Physical: 10007 M 50000 Size (KB): 155406176 Starting Blk: 110420 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 156290560 Fixed" |
04-15-2006, 02:21 PM | #14 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
try "co de predict individual 10000 (/force)" force is optional
or "co de config individual 10000 (/force)" this is with the good/org drive on top. I went through this with my 2000, but that was 4-5 yrs ago.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
04-15-2006, 02:24 PM | #15 |
Cooling Neophyte
Join Date: Apr 2006
Location: Austin, TX
Posts: 9
|
Re: 2200 w/dead drive
Good news. I discovered that when the new drive was plugged in by itself, although it had none of the data or file structure, it did retain all the user, share, and security data, so it knew what the file structure was supposed to be. By going into the Network Shares/Properties page for each share, I was able to select the new disk as valid and the snap created the path. I was then able to access the snap from the backup location and copy the files.
The 2nd 300g drive would not format when I installed it in the 10000 position, but I moved the 1st 300g drive to the 10000 position and put the 2nd 300g drive in the 10010 position and it formatted. The Configure Disks menu item now indicates that I have 2 individual disks and I have the option to select Data Protection or One Large Disk. Looks like I am home free. Thanks so much for the help and support. You guys rock. |
06-05-2007, 07:21 AM | #16 |
Cooling Savant
Join Date: Oct 2001
Location: Dallas, Tx
Posts: 469
|
Re: 2200 w/dead drive
Bump. This should be kept near the top. I've got it bookmarked for when i need to remember the syntax for breaking up a RAID set. As i did with my new 2200. Which after getting it working i descovered one drive was bad. Luckilly it was set to mirror and not stripe.
Shane
__________________
Snap Servers: 1100 - 1x300gb Seagate Baracuda (SnapOS Version 3.4.807) 2200 - 2x80gb Maxtor (one dead) (SnapOS 4.0.860) Last edited by Hallis; 06-05-2007 at 09:23 AM. |
06-05-2007, 02:43 PM | #17 |
Cooling Savant
Join Date: Aug 2004
Location: UK
Posts: 909
|
Re: 2200 w/dead drive
David - Sticky Please?
__________________
Snap Server Help Wiki - http://wiki.procooling.com/index.php/Snap_Server Snap Server 2200 v3.4.807 2x 250GB Seagate Barracuda 7200.9 w/ UNIDFC601512M Replacement Fan "Did you really think it would be that easy??" Other NAS's 1x NSLU2 w/ 512mb Corsair Flash Voyager Running Unslung 6.8b 1x NSLU2 w/ 8Gb LaCie Carte Orange Running Debian/NSLU2 Stable 4.0r0 250GB LaCie Ethernet Disk Running Windows XP Embedded |
06-05-2007, 04:36 PM | #18 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: 2200 w/dead drive
I added it to FAQ's
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
|
|