logical set 60000, error -1 - Page 2

blue68f100 · 03-30-2007, 05:40 PM

The cmd I gave you is like a low level format. It ignors the previous settings, correcting anything that is not correct.

You need to to all drives. Either remove them all and use the mfg utility to format (quick zero of mbr will work). Then let the snap do a complete setup like all new drives.

The reason why all drives must be done.:
On some version of the os the starting point was determined by taking the number of sectors divided by 7. Then snap changed it to divide by 8.

Phoenix32 · 03-30-2007, 08:08 PM

Quote:

Originally Posted by ShrewLWD

OK, I broke the array, then sent that command to the 10010 drive (drive 3). While it's formatting, I did notice that upon breaking the array it formatted and reinitialized all the drives (or at least it said it was in the Disk Config view). Is the command you gave me going to do something different than what it did?

UPDATE: After running that command and re-running in de, the start block is still different than the others (the 3 originals are starting at 95927, this last one starts at 104776)

I don't see how formatting the others will make them jump up to that block, since he didn't bother to ask the others what block they are starting at.

Is there a different command to use?

Use the command he gave you on ALL 4 DRIVES. This causes a full reinit of the drive (including start block), where normal format does not.

Early version of the SNAP OS and the later versions had different start blocks. This unit has probably had the OS updated since the original init.

ShrewLWD · 03-30-2007, 09:43 PM

I ran it on all, one at a time, rebooting so the command could run, and it still shows different start blocks.

ShrewLWD · 03-31-2007, 09:03 AM

Is there an option to have it run simultaneously on all of them?

If not, should I take them all out, attach them to a generic computer, and do a low level format on each of them?

eschw95458 · 03-31-2007, 10:45 AM

When you type in "co de format 10000 /reinit" you should then get a message that says
"The requested operation will be executed after the next reboot.
Look in log for progress..."

DO NOT reboot type in the next one IE....."co de format 10008 /reinit" etc, etc,
Then when you have all the drives ready simply type r and hit enter

ShrewLWD · 03-31-2007, 01:12 PM

Cool! I'll try it right away.

I do have a question though..it appears as if 10000 and 10008 are designations of partitions, while 1000f and 10007 etc., are physical drives. Shouldn't I be be doing something to the physical drive, rather than a partition on a drive?

ShrewLWD · 03-31-2007, 01:26 PM

Unfortunately, it still starts 3 of them at 95927 and the new drive at 104776.

Anything else I can try?

eschw95458 · 03-31-2007, 01:36 PM

Yes, you can pull all the drives and format them, it's been a while but I think you can do fat32, put them back in and power the unit back up. That will of course wipe everything.

ShrewLWD · 03-31-2007, 01:41 PM

will give that a try next! Thanks for you guys' patience! It's frustrating for me too, just wanting to get this thing back up and running.

eschw95458 · 03-31-2007, 01:49 PM

If you look right under where it says Logical device it says Label. Then you can see where it says Drive1 2 etc.

ShrewLWD · 03-31-2007, 02:03 PM

Now one thing I read is that, because I'm going to be wiping drive 0, I will not have access to the admin screens for awhile, until it does it's internal formatting and setting up, correct?

eschw95458 · 03-31-2007, 02:17 PM

It really shouldn't be too long, really not much longer than when you issued the /reinit cmd. It is possible to log in to the 4100 with no drives installed :-)

ShrewLWD · 03-31-2007, 02:21 PM

Hey hey..MN too? Cool!

So do a low level format, or just connect them to a PC and do a Windows format?

UPDATE: Man, I hope doing a quick format will suffice...doing a full format for each 120Gig HD is going to take forever! (I know, I have no patience! heh!)

ShrewLWD · 03-31-2007, 03:36 PM

*Sigh* OK, even after formatting all of them separately in a Windows machine, then putting them back, the in de shows the starting blocks off.

Low level format next?

blue68f100 · 03-31-2007, 03:49 PM

The snap will take ~5-10 min before you will gain access to the admin.

Make sure the larger drive is not installed in position 1 or 2.

I have noticed on some units installing 1 drive at a time works.
You can also try adding the "/nocore" flag to the /init cmd.
Last but not least, use WD drive utility to read the size of your original HD then adjust the new drive to match.

ShrewLWD · 03-31-2007, 05:03 PM

Dang it! I did a low level format on drive 0, then put it back (only) and powered it up. It took awhile (as you said) to get to the admin window, but when I finally did, it showed it going to its original starting block (95927)
I can only hope that low level formatting the new drive will allow the snap to start at that same starting block.
I got Z & W, but they require true dos bootup, and I have been attaching these drives as USB to wipe them. I will need to monkey with my setup a bit to get them to be true local drives.

Update: hey blue, when you say dont put it in pos1 or 2, is that counting 0 1 2 3, or 1 2 3 4?

ShrewLWD · 03-31-2007, 05:50 PM

OK, this is getting a tad absurd! What is dictating the use of the starting block..the snap or the drive? I low-level formatted the new one, put it in slot 3 (drive bay 4, where it has not been before) and fired it up with newly ll-formatted drive 0 in its normal bay. Same thing...the new drive wants to start on 104776.

Should I send it back to adaptec and insist they send me a drive that starts on 95927?

It shouldn't be this hard to get something this trivial up and running! Why does it even care that they all need to start on the same block? Can it not keep individual tabs on each drive?
/rant off

blue68f100 · 03-31-2007, 05:57 PM

Did you tried the following "co de format 10018 /reinit /nocore" ? Where the HD is in drive 4 position.

Also go to WD and download there drive utility. It will allow you to adjust the drive size. If you do not find it let me know and I will send it to your.

WHAT OS VERSION are YOU RUNNING ?????

ShrewLWD · 03-31-2007, 08:49 PM

My setup is
OS 4.0.860,
HW 2.2.1,
BIOS 2.4.437

I am running the /nocore option now.
I think I know what software you are referring to, but I don't understand how setting it to a size is also going to tell it to move the starting block. It seems to have remarkable resilience to any change.

UPDATE: OK, /nocore did move the starting block! Unfortunately, not to the same as the others! It's a smaller number, but still an even number (88472)

Should I now try reinit again without the /nocore ?

ShrewLWD · 03-31-2007, 08:58 PM

Just to make sure I'm not wasting you guys' time...I am not rebuilding any raid everytime. I simply follow your suggestions, then watch it format the drive and initialize it. I then check in de to see what the starting block is. I didn't think building a RAID was going to change what the suggestions you offered could not.

ShrewLWD · 03-31-2007, 09:05 PM

Nope, redoing the format without the /nocore took it back to 104776.

blue68f100 · 04-01-2007, 01:41 PM

Use the mfg utility to change the drive size. Since all else has failed.

snap-tech · 04-01-2007, 07:03 PM

ShrewLWD

The following error means that the last drive has a an issue reading/writing to

DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20
DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20
DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20

This line tells you what drive. The last digit = the drive. 0-3.

dev=0xc0003

Your options are to either send drive back if this is the drive you just received. Or to run some kind of drive repair util to locate bad sectors and mark them bad, then retry to use drive in snap.

I will post another message in an hour or so, explaining when you need to worry about starting blocks and when not to worry.

Douglas Snap-Tech

snap-tech · 04-01-2007, 07:56 PM

Do you know if the snap was running a 2x version or a 3x version when the raid was originally built ( in other words the first time).

ShrewLWD · 04-02-2007, 09:50 AM

Well, geat news late last night! I had wiped all the drives, and was resetting them up in the original RAID5 configuration so that when it crashed I would have up to date logs for an adaptec support call I was going to make this morning. It got to the 71% mark... then kept going! It actually completed the process and gave a greenlight to the setup!

Of the things different, all drives were low level formatted, and the newer, larger drive was moved from bay 3 (drive 2) to bay 4 (drive 3)
The starting block is still off, but it's working.

A really big thank you to you guys for assisting, even on weekends!!!

snap-tech, yes, knowing when starting blocks are an issue would be very useful info! Please do share!

As far as updates go, we only went from the version prior to .860 (.805?), to the 860 update, due to the Windows SMB patch issue.

03-30-2007, 05:40 PM	#26
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: logical set 60000, error -1 The cmd I gave you is like a low level format. It ignors the previous settings, correcting anything that is not correct. You need to to all drives. Either remove them all and use the mfg utility to format (quick zero of mbr will work). Then let the snap do a complete setup like all new drives. The reason why all drives must be done.: On some version of the os the starting point was determined by taking the number of sectors divided by 7. Then snap changed it to divide by 8. __________________ 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

03-30-2007, 09:43 PM	#28
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 I ran it on all, one at a time, rebooting so the command could run, and it still shows different start blocks.

03-31-2007, 09:03 AM	#29
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Is there an option to have it run simultaneously on all of them? If not, should I take them all out, attach them to a generic computer, and do a low level format on each of them?

03-31-2007, 10:45 AM	#30
eschw95458 Cooling Neophyte Join Date: Aug 2006 Location: Minnesota Posts: 52	Re: logical set 60000, error -1 When you type in "co de format 10000 /reinit" you should then get a message that says "The requested operation will be executed after the next reboot. Look in log for progress..." DO NOT reboot type in the next one IE....."co de format 10008 /reinit" etc, etc, Then when you have all the drives ready simply type r and hit enter

03-31-2007, 01:12 PM	#31
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Cool! I'll try it right away. I do have a question though..it appears as if 10000 and 10008 are designations of partitions, while 1000f and 10007 etc., are physical drives. Shouldn't I be be doing something to the physical drive, rather than a partition on a drive?

03-31-2007, 01:26 PM	#32
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Unfortunately, it still starts 3 of them at 95927 and the new drive at 104776. Anything else I can try?

03-31-2007, 01:36 PM	#33
eschw95458 Cooling Neophyte Join Date: Aug 2006 Location: Minnesota Posts: 52	Re: logical set 60000, error -1 Yes, you can pull all the drives and format them, it's been a while but I think you can do fat32, put them back in and power the unit back up. That will of course wipe everything.

03-31-2007, 01:41 PM	#34
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 will give that a try next! Thanks for you guys' patience! It's frustrating for me too, just wanting to get this thing back up and running.

03-31-2007, 01:49 PM	#35
eschw95458 Cooling Neophyte Join Date: Aug 2006 Location: Minnesota Posts: 52	Re: logical set 60000, error -1 If you look right under where it says Logical device it says Label. Then you can see where it says Drive1 2 etc.

03-31-2007, 02:03 PM	#36
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Now one thing I read is that, because I'm going to be wiping drive 0, I will not have access to the admin screens for awhile, until it does it's internal formatting and setting up, correct?

03-31-2007, 02:17 PM	#37
eschw95458 Cooling Neophyte Join Date: Aug 2006 Location: Minnesota Posts: 52	Re: logical set 60000, error -1 It really shouldn't be too long, really not much longer than when you issued the /reinit cmd. It is possible to log in to the 4100 with no drives installed :-)

03-31-2007, 02:21 PM	#38
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Hey hey..MN too? Cool! So do a low level format, or just connect them to a PC and do a Windows format? UPDATE: Man, I hope doing a quick format will suffice...doing a full format for each 120Gig HD is going to take forever! (I know, I have no patience! heh!) Last edited by ShrewLWD; 03-31-2007 at 03:06 PM.

03-31-2007, 03:36 PM	#39
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Sigh OK, even after formatting all of them separately in a Windows machine, then putting them back, the in de shows the starting blocks off. Low level format next?

03-31-2007, 03:49 PM	#40
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: logical set 60000, error -1 The snap will take ~5-10 min before you will gain access to the admin. Make sure the larger drive is not installed in position 1 or 2. I have noticed on some units installing 1 drive at a time works. You can also try adding the "/nocore" flag to the /init cmd. Last but not least, use WD drive utility to read the size of your original HD then adjust the new drive to match. __________________ 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

03-31-2007, 05:03 PM	#41
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Dang it! I did a low level format on drive 0, then put it back (only) and powered it up. It took awhile (as you said) to get to the admin window, but when I finally did, it showed it going to its original starting block (95927) I can only hope that low level formatting the new drive will allow the snap to start at that same starting block. I got Z & W, but they require true dos bootup, and I have been attaching these drives as USB to wipe them. I will need to monkey with my setup a bit to get them to be true local drives. Update: hey blue, when you say dont put it in pos1 or 2, is that counting 0 1 2 3, or 1 2 3 4?

03-31-2007, 05:50 PM	#42
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 OK, this is getting a tad absurd! What is dictating the use of the starting block..the snap or the drive? I low-level formatted the new one, put it in slot 3 (drive bay 4, where it has not been before) and fired it up with newly ll-formatted drive 0 in its normal bay. Same thing...the new drive wants to start on 104776. Should I send it back to adaptec and insist they send me a drive that starts on 95927? It shouldn't be this hard to get something this trivial up and running! Why does it even care that they all need to start on the same block? Can it not keep individual tabs on each drive? /rant off

03-31-2007, 05:57 PM	#43
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: logical set 60000, error -1 Did you tried the following "co de format 10018 /reinit /nocore" ? Where the HD is in drive 4 position. Also go to WD and download there drive utility. It will allow you to adjust the drive size. If you do not find it let me know and I will send it to your. WHAT OS VERSION are YOU RUNNING ????? __________________ 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

03-31-2007, 08:49 PM	#44
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 My setup is OS 4.0.860, HW 2.2.1, BIOS 2.4.437 I am running the /nocore option now. I think I know what software you are referring to, but I don't understand how setting it to a size is also going to tell it to move the starting block. It seems to have remarkable resilience to any change. UPDATE: OK, /nocore did move the starting block! Unfortunately, not to the same as the others! It's a smaller number, but still an even number (88472) Should I now try reinit again without the /nocore ?

03-31-2007, 08:58 PM	#45
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Just to make sure I'm not wasting you guys' time...I am not rebuilding any raid everytime. I simply follow your suggestions, then watch it format the drive and initialize it. I then check in de to see what the starting block is. I didn't think building a RAID was going to change what the suggestions you offered could not.

03-31-2007, 09:05 PM	#46
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Nope, redoing the format without the /nocore took it back to 104776.

04-01-2007, 01:41 PM	#47
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: logical set 60000, error -1 Use the mfg utility to change the drive size. Since all else has failed. __________________ 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-01-2007, 07:03 PM	#48
snap-tech Cooling Neophyte Join Date: Mar 2002 Location: Washington State Posts: 54	Re: logical set 60000, error -1 ShrewLWD The following error means that the last drive has a an issue reading/writing to DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20 DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20 DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20 This line tells you what drive. The last digit = the drive. 0-3. dev=0xc0003 Your options are to either send drive back if this is the drive you just received. Or to run some kind of drive repair util to locate bad sectors and mark them bad, then retry to use drive in snap. I will post another message in an hour or so, explaining when you need to worry about starting blocks and when not to worry. Douglas Snap-Tech

04-01-2007, 07:56 PM	#49
snap-tech Cooling Neophyte Join Date: Mar 2002 Location: Washington State Posts: 54	Re: logical set 60000, error -1 Do you know if the snap was running a 2x version or a 3x version when the raid was originally built ( in other words the first time).

04-02-2007, 09:50 AM	#50
ShrewLWD Cooling Neophyte Join Date: Mar 2007 Location: MN, USA Posts: 19	Re: logical set 60000, error -1 Well, geat news late last night! I had wiped all the drives, and was resetting them up in the original RAID5 configuration so that when it crashed I would have up to date logs for an adaptec support call I was going to make this morning. It got to the 71% mark... then kept going! It actually completed the process and gave a greenlight to the setup! Of the things different, all drives were low level formatted, and the newer, larger drive was moved from bay 3 (drive 2) to bay 4 (drive 3) The starting block is still off, but it's working. A really big thank you to you guys for assisting, even on weekends!!! snap-tech, yes, knowing when starting blocks are an issue would be very useful info! Please do share! As far as updates go, we only went from the version prior to .860 (.805?), to the 860 update, due to the Windows SMB patch issue.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)