Ok, running the boot disk in dos it can see the hard drive, however it is dark grey not black, and isn't clickable on. Any ideas?
|
I dont think ghost supports the format - the SCR=2 from my post means disk 2 (i can see the drive but it is grey as well). when i try to force it to copy the drive all it says is "Invalid Source Drive" - i dont think ghost 2003 will ever be able to recognise it. maybe you should try with hard drive upgrader, i will but it means installing a floppy drive
|
Whats hd upgrader? i have a floppy drive.
Thanks Sam |
Mg managed to clone his drive with ghost using the -ir switch (page 3). i have just tried this as well and although i managed to copy the drive (i had to use the -fro switch as well because norton found errors on the drive) it does not boot the snap server (hdd light remains lit)
if you want to try this poogles run ghost interactively (under advanced) and then when it boots into ghost dos find out the hard drive number and exit. press any key to go into pc dos and type in: ghost.exe -clone,mode=copy,src=3(drive number of source),dst=2(drive number of target) -ir(image raw) -fro(ignore errors) hdupgrader was mentioned on page 2 by danz |
Got it to work with an 250GB IBM Deskstar but only showed up as 130GB... I'm trying with 120GB IBM Deskstar and it doesn't seam to recognize the drive. I get this error in my log.
Disk Driver : Cannot Read Device 80070007 Block 13 LCD Message : FAILED: Disk 1 |
Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 23688 Private Mounted
Label:Private Contains system files only Unique Id: 0x1B3E34BA62A5C23D 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): 78124544 Fixed Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 22416 Private Mounted Label:Private Contains system files only Unique Id: 0x70A79B84562ECECC 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): 78150656 Fixed Logical Device: 10000 Position: 1 JBOD Size (KB): 76569392 Free (KB): 76492720 Public Mounted Label:Drive1 Single disk Unique Id: 0x1B3E34BA62A5C23D Mount: /0 Index: 0 Order: 2 Partition: 10000 Physical: 10007 FS Size (KB): 77630984 Starting Blk: 61567 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 78124544 Fixed Logical Device: 50000 Position: 2 MIRROR_CRACKED Size (KB): 76595040 Free (KB): 76513448 Public Mounted Label:Mirror Network Drive Unique Id: 0x329301B5625BE22C Mount: /2 Index: 2 Order: 3 Partition: 10010 Physical: 10017 M 50000 Size (KB): 77656968 Starting Blk: 61583 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 78150656 Fixed It seems like from looking at config devices info that that there is the os on the hard drive. If you look at the stats ive posted above. On both 10006 and 10016 there is a mount of /priv and /pri2 and Label:Private Contains system files only. Both with the size of 32296KB = 31.53mb. The OS file is 30093KB or 29.3MB. So that is where the OS must be. There is free kb of 23688 and 22416 on the drives free. IS this in anticipation of a larger os update file? I believe 0x1B3E34BA62A5C23D is my new drive it is mount /0. The raid is mount /2, does that mean the 2nd drive was the one that works? It you do 76569392 - 76492720 you get 76672. Then 32296 + 23688 gives 55984. Any ideas why it says 2000 not 2200 on the about screen? With just the new drive in i reinstalled snap os v4. When i try to install Snap Extensions i get: Unable to complete upgrade. Operation Aborted. The upgrade operation did not complete successfully so the advanced window will be closed. Any ideas why?? It will install it with the 2 drives in. Im a bit reluctant to reformat the original drive to remove the old mirror, because i may lose the facility to install the snap extensions. However, when i put the drive back in again, snap extensions had been removed (may have been snap os reinstallation). Command: qdl scantree /0 0 (new drive) BUILT: /0 - 14 records. BUILT: /0/rescued - 7 records. BUILT: /0/os_private - 32 records. BUILT: /0/os_private/Temp - 7 records. BUILT: /0/WWW - 7 records. qdlScanTree found NO problems with path: /0 Command: qdl scantree /2 0 (old drive 1 would be the other part of the raid set) BUILT: /2 - 12 records. BUILT: /2/rescued - 7 records. BUILT: /2/os_private - 32 records. BUILT: /2/os_private/Java - 11 records. BUILT: /2/os_private/Java/Jeode - 20 records. BUILT: /2/os_private/Java/Jeode/snapserver - 9 records. BUILT: /2/os_private/Java/Jeode/snapserver/snaplets - 11 records. BUILT: /2/os_private/Java/Jeode/snapserver/snaplets/confs - 9 records. BUILT: /2/os_private/Java/Jeode/snapserver/snaplets/jars - 11 records. BUILT: /2/os_private/Java/Jeode/bin - 26 records. BUILT: /2/os_private/Java/Jeode/lib - 15 records. BUILT: /2/os_private/Java/Jeode/lib/security - 13 records. BUILT: /2/os_private/Java/Jeode/lib/ext - 18 records. BUILT: /2/os_private/Java/Jeode/classes - 9 records. BUILT: /2/os_private/Java/Jeode/classes/com - 10 records. BUILT: /2/os_private/Java/Jeode/classes/com/snapserver - 9 records. BUILT: /2/os_private/Java/Jeode/classes/com/snapserver/demo - 21 records. BUILT: /2/os_private/Java/Jeode/classes/com/snapserver/demo/hello - 13 records. BUILT: /2/os_private/Java/Jeode/etc - 9 records. BUILT: /2/os_private/Java/Jeode/tmp - 7 records. qdlScanTree found NO problems with path: /2 It seems like they both have the os_private on them. Any ideas why i can't install os v4 on the new drive? Because i will never be able to remove this drive if i can't sort his out. |
BIOS problem I think
Has anyone found a way to flash the BIOS yet. I think I boat anchored mine by setting the level to 4.0.0 and rebooting.
When I upgraded to SnapOS 4 my 1000s would not see the 2nd drive at all. Anyone else had this problem? I am really, really thinking of forgetting the Snaps and just building a Server 2003 solution with a ton of drives in a RAID 5 array so I will have one place to put all my stuff. |
i would - server 2003 is avaliable for a free trial and the hardware wouldent need to cost more than £150 (~$300) + drives.
i spent £115 and bought a clearence mobo [sata, onboard lan], case & psu [chieftec beast], ram, amd 2100cpu, stole mouse, keyboard, monitor from old pcs (i only access it via remote access) and dropped as many drives as i could find in it. it transfers files at ~10MBps (16MBps full duplex) unlike my snap 1000 that has a maximum transfer rate of 1.5MBps (it drops further if you send and recieve at the same time) |
Recover from BIOS mistake
I may have found a way to recover from the dreaded BIOS faux pax. I too set my Hardware revision to 4.0.0 and did not back it down before a reboot so I faced the dreaded rapidly blinking system light last night. briefly, I cloned one of my old drives that had a lower revision of the system, put it in this afternoon, powered up and I now have access to my server again. Over the next few days I will do some testing and come up with some more concrete information so we can all work on this solution. I am waiting eagerly to hear how some of you are imaging the system partition so I can image the system on my drives with the older SnapOS and work with that so we can have a resource online.
In the meantime, I think I am going to start working toward a big file server box just for the heck of it, but that is off topic. I'll do the best I can between the family, studies, and work to stay in touch. |
Norton Ghost and other thought
Quote:
|
it is alright now - i bothered to read all the 12 pages of posts and i downloaded dolly (from download.com - 40mb file) and that worked perfectly. i still can not get a decent transfer speed (1.5MBps) but i think that is the limitation of the snap 1000's hardware and not a fault
|
When i unmounted both devices (ie both hard drives). The server can be browsed normally, but the SnapExtensions disappeared. After a reboot, both drives had been remounted in JBOD. So i have removed the failed raid set. WHOPPPEEE!! Proper Instructions:
On Debug type 'config devices unmount' This unmounts them all. Wait a few seconds and the page will load saying the action has been completed successfully. Then manually reboot the unit. It will reboot with the cracked raid removed. The HD info is now: Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22688 Private Mounted Label:Private Contains system files only Unique Id: 0x1B3E34BA62A5C23D 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): 78124544 Fixed Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 22416 Private Mounted Label:Private Contains system files only Unique Id: 0x70A79B84562ECECC 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): 78150656 Fixed Logical Device: 10000 Position: 1 JBOD Size (KB): 76569392 Free (KB): 76492152 Public Mounted Label:Drive1 Single disk Unique Id: 0x1B3E34BA62A5C23D Mount: /0 Index: 0 Order: 2 Partition: 10000 Physical: 10007 FS Size (KB): 77630984 Starting Blk: 61567 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 78124544 Fixed Logical Device: 10010 Position: 2 JBOD Size (KB): 76595040 Free (KB): 76511200 Public Mounted Label:Drive2 Single disk Unique Id: 0x70A79B84562ECECC Mount: /2 Index: 2 Order: 3 Partition: 10010 Physical: 10017 FS Size (KB): 77656968 Starting Blk: 61583 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 78150656 Fixed Anyone any ideas why i can install OS v4, but not snap extensions with just the new drive in? Even though, looking at the above, the new drive is the primary as it is 0x1B3E34BA62A5C23D. It will however, install it with just the old drive plugged in. command dir /0/os_private (0 =new drive) Inode ATTR Protection Size Created Modified Accessed UID GID Name 768 HS d---rwx--- 1024 09/22/2004 17:37:18 09/25/2004 12:34:21 09/30/2004 18:11:33 3 2 . 2 drwxrwxrwx 1024 09/22/2004 17:35:14 09/25/2004 12:34:21 09/30/2004 18:10:49 3 2 .. 769 HSA ----rwx--- 848 09/22/2004 17:37:18 09/30/2004 17:59:39 09/30/2004 18:10:41 3 2 fdb_blob.dat 770 HSA ----rwx--- 176 09/22/2004 17:37:18 09/30/2004 17:59:39 09/30/2004 18:10:41 3 2 fdb_hid_idx.dat 771 HSA ----rwx--- 168 09/22/2004 17:37:18 09/30/2004 17:59:39 09/30/2004 18:11:33 3 2 fdb_sdb_idx.dat 772 HSA ----rwx--- 136 09/22/2004 17:37:18 09/30/2004 17:59:39 09/30/2004 18:11:10 3 2 fdb_name_idx.dat 773 HSA ----rwx--- 848 09/22/2004 17:43:02 09/30/2004 17:59:39 09/30/2004 17:59:39 3 2 fdb_blob.dat.sdw 774 HSA ----rwx--- 176 09/22/2004 17:43:02 09/30/2004 17:59:39 09/30/2004 17:59:39 3 2 fdb_hid_idx.dat.sdw 775 HSA ----rwx--- 136 09/22/2004 17:43:02 09/30/2004 17:59:39 09/30/2004 17:59:39 3 2 fdb_name_idx.dat.sdw 776 HSA ----rwx--- 168 09/22/2004 17:43:02 09/30/2004 17:59:39 09/30/2004 17:59:39 3 2 fdb_sdb_idx.dat.sdw 1536 d---rwx--- 1024 09/22/2004 17:48:57 09/25/2004 12:34:21 09/30/2004 17:13:28 3 2 Temp command dir /2/os_private (2 =old drive) Inode ATTR Protection Size Created Modified Accessed UID GID Name 768 HS d---rwx--- 1024 09/22/2004 17:31:47 09/25/2004 12:34:34 09/30/2004 18:11:49 3 2 . 2 drwxrwxrwx 1024 09/22/2004 17:28:26 09/25/2004 12:34:34 09/30/2004 17:34:51 3 2 .. 769 HSA ----rwx--- 848 09/22/2004 17:31:47 09/30/2004 18:09:22 09/30/2004 18:10:42 3 2 fdb_blob.dat 770 HSA ----rwx--- 176 09/22/2004 17:31:47 09/30/2004 18:09:22 09/30/2004 18:10:42 3 2 fdb_hid_idx.dat 771 HSA ----rwx--- 168 09/22/2004 17:31:47 09/30/2004 18:09:22 09/30/2004 18:11:40 3 2 fdb_sdb_idx.dat 772 HSA ----rwx--- 136 09/22/2004 17:31:47 09/30/2004 18:09:22 09/30/2004 18:11:10 3 2 fdb_name_idx.dat 1536 d---rwx--- 1024 09/22/2004 17:38:48 09/25/2004 12:34:34 09/25/2004 12:34:35 3 2 Java 773 HSA ----rwx--- 848 09/22/2004 17:43:02 09/30/2004 18:09:22 09/30/2004 18:09:22 3 2 fdb_blob.dat.sdw 774 HSA ----rwx--- 176 09/22/2004 17:43:02 09/30/2004 18:09:22 09/30/2004 18:09:22 3 2 fdb_hid_idx.dat.sdw 775 HSA ----rwx--- 136 09/22/2004 17:43:02 09/30/2004 18:09:22 09/30/2004 18:09:22 3 2 fdb_name_idx.dat.sdw 776 HSA ----rwx--- 168 09/22/2004 17:43:02 09/30/2004 18:09:22 09/30/2004 18:09:22 3 2 fdb_sdb_idx.dat.sdw Command: dir /priv Inode ATTR Protection Size Created Modified Accessed UID GID Name 2 drwxrwxrwx 1024 09/11/2004 9:26:48 09/30/2004 17:13:24 09/30/2004 18:14:19 3 2 . 2 dr-xr-xr-x 0 09/30/2004 18:10:33 09/30/2004 18:14:19 09/30/2004 18:14:19 3 2 .. 3 HS drwxrwxrwx 8704 09/11/2004 9:26:48 09/30/2004 17:13:24 09/30/2004 17:59:55 3 2 rescued 768 HS d---rwx--- 1024 01/30/2002 17:44:09 09/11/2004 12:47:15 09/30/2004 18:10:39 3 2 os_private 1536 drwxrwxrwx 1024 01/30/2002 17:51:21 09/11/2004 12:47:37 09/30/2004 17:59:55 3 2 statmonlist 4 HSA -rwxrwxrwx 524289 01/30/2002 17:51:23 09/30/2004 18:12:29 09/30/2004 18:12:29 3 2 HARD.log 1537 drwxrwxrwx 1024 02/04/2002 17:31:40 09/30/2004 17:13:25 09/30/2004 17:59:56 3 2 resources 2307 drwxrwxrwx 8704 02/04/2002 17:32:07 09/30/2004 17:13:25 09/30/2004 18:10:39 3 2 help 2476 drwxrwxrwx 1024 08/23/2004 14:44:50 09/30/2004 17:13:25 09/30/2004 18:10:42 3 2 Jeode 176 drwxrwxrwx 1024 08/29/2004 18:53:33 09/30/2004 17:13:25 09/30/2004 18:10:42 3 2 osupdate 177 HSA -rwxrwxrwx 6 01/30/2002 17:44:09 09/30/2004 18:12:29 09/30/2004 18:10:39 3 2 tag.dat Command: dir /pri2 Inode ATTR Protection Size Created Modified Accessed UID GID Name 2 drwxrwxrwx 1024 01/30/2002 17:44:08 09/11/2004 12:37:44 09/30/2004 18:14:53 3 2 . 2 dr-xr-xr-x 0 09/30/2004 18:10:33 09/30/2004 18:14:53 09/30/2004 18:14:53 3 2 .. 3 HS drwxrwxrwx 8704 01/30/2002 17:44:08 09/11/2004 12:37:44 09/30/2004 18:10:39 3 2 rescued 768 HS d---rwx--- 1536 01/30/2002 17:44:09 09/11/2004 12:37:44 09/30/2004 18:10:41 3 2 os_private 4 HSA -rwxrwxrwx 6 01/30/2002 17:44:09 09/30/2004 18:09:24 09/30/2004 18:10:41 3 2 tag.dat 1536 drwxrwxrwx 1024 01/30/2002 17:51:21 09/11/2004 12:40:18 09/30/2004 18:10:39 3 2 statmonlist 5 HSA -rwxrwxrwx 524289 01/30/2002 17:51:23 09/30/2004 18:09:24 09/30/2004 18:10:39 3 2 HARD.log 2305 drwxrwxrwx 1024 02/04/2002 17:31:40 09/11/2004 12:08:43 09/30/2004 18:10:39 3 2 resources 1540 drwxrwxrwx 8704 02/04/2002 17:32:07 09/11/2004 12:37:44 09/30/2004 18:10:41 3 2 help 1537 drwxrwxrwx 1024 08/23/2004 14:44:50 09/11/2004 12:37:44 09/30/2004 18:10:41 3 2 Jeode 177 drwxrwxrwx 1024 08/29/2004 18:53:33 09/11/2004 12:37:45 09/30/2004 18:10:41 3 2 osupdate |
hey,
has anyone successfully replaced the blowers/fans in a Dell 705n/Snap 4100? i'm specifically interested in replacing them with units that are QUIETER because all i hear from my closet (where the snap is stored) is a constant loud hum that's really starting to annoy me. ideas? suggestions? help? Aaron |
poogles_uk
Just a guess, but you might want to try and make the Java directory on the new drive and then try installing. I noticed I have the Java directory, but I haven't installed it. In the debug menu, try: md /0/os_private/Java Failing that, you could also try to move the directory using the move command: mv /2/os_private/Java /0/os_private/Java |
Well folks, I've updated a DELL 705N (Snap 4100) to SnapOS 4.x and everything works except for the 48bit LBA issue (which I REALLY need).
Bios stamp 2.4.437 Plat Bytes 2.2.1 Model Byte 2 With "info log T" I'm getting IDE: A 48 bit LBA capable Hard Drive was detected ... IDE: 48 bit LBA is not supported on 4100 and 12000 platforms. IDE: Setting the hard drive size to maximum addressable by 28 bits: 131071 MBytes. Resetting the LBA Counter doesn't help. I've dug up the info on the Promise PDC 20265 IDE chips used in this 4100 and they can/do support 48 bit LBA. 48Bit LBA support came later for them in late 2001/early 2002 so a Promise firmware upgrade is possibly needed. The Promise cards that used these chips are on the FastTrak 100, SuperTrak 100, and other Promise Ultra 100 UDMA cards, and I have found the firmware for them. I've been hunting for a console connection of some sort as it seems somewhat logical to have another way into the board during manufacturing and testing. There are the other 4 lines on the RJ45 (pins 4,5,7,8) and the mysterious J8 connector (which looks like a 5th IDE connector) but apparently isn't. Regardless, it seems even if it were possible to upgrade the onboard promise firmware, the hardcoded check for a 4100 above would still keep me from using it. I've tried various methods to change the bios platform bytes, OEM Level, and Model without success (i.e. I can change them, but the check is either there or other issues came up that prevented the 4100 from working). I'd like to try the UK SnapOS version or find out if it is the same image as the US version. Right now I'm torn between trying to keep hacking this or just replacing the motherboard with an ITX one loaded with Darma or Zetta NAS images. What really bugs me is the fact that the hardware is certainly capable of handling 48bit LBA drives, but there is no interest by Adaptec/SnapAppliance to enable it (and yet they still sell this box today!!). Seems to be more of a marketing issue than a technical one, but that's getting into conspiracy theories. I'd appreciate any more ideas on things to try. Many Thanks! |
Ive downloaded Digital Dolly. When i have some time to take the case of my pc (I have a removable IDE bay attatched to my raid card, but this wont load in Digital Dolly) i will use raw copy and make a backup for people to use. I will also write this onto my secondary drive to see if it will let me install Snap Extensions on it.
|
I just blew the fuse in my snap 2000. Anybody know what kind of fuse it needs? I pulled it out and see that it is ceramic, with 250V, I don't see what the amperage is. Does anybody have any idea what it uses?
|
I know this came across this forum, but I'm still in need of help....
I have 2 SNAP Server 1100s whose hard drives died on the same (what are the friggin' odds) and I couldn't get even the chance to do the hard drive swap. Is there anyone that has done perhaps an image of the drive with DOLLY or Ghost, or what have you... Any help is SOOOOOO greatly appreciated. You can email me at [crivas] at [thegeekstreetjournal] dot [net] with any information. LOS |
Can someone verify if the 4000 will boot with no drives attached?
I know the 4100 will which proves the OS is in the flash (java/help files are on the drive). If I change the platformbytes to 2 0 0 (4000 series), it boots with the error: Pseudoflash partition not found. Return from read -2. Which again leads me to believe the OS for the 4000 is on the drive? There was a quote a long while back in the thread that indicated this was the case for "newer" snapservers with the modified BSD OS. Just curious if I could get the first 64MB of a 4000 drive, then maybe it will boot as a 4000 and get me around the LBA 48 issue. |
I cant see it working without the hard drives. My 2200 wouldn't
I hope to make a hd image at the weekend. I will upload it to the file space in a week or so. |
Very much appreciate it!
|
Well after a lot of time and work I found a Snap 2200 drive with the image on it.
I used it to boot up and initialize my 2200 and it is now operational. I have a drive to make an image from now. I also have one from a snap 1000. Now I just have to figure out how to make the image file. I'll let you all know. |
Diskprobe I think
There is a utility in the MS Win NT4 Resource Kit called Diskprobe that allows you to copy a certain number of clusters from a HDD and save as a file. It is mentioned earlier in the forum. I looked at the docs and it seems like it will do the job. I think there is even a report of success in the forums with the tool.
|
Here is the link to the SnapOS 4.0.
ftp://Purchased:EnTitled@208.0.185.9/SnapStore40/ Also, I couldn't get my raid "uncracked" using Poogles_UK method. But I too am waiting for the image for the 2200..... |
Quote:
__________________________________________________ _______________ 10/16/2004 18:58:54 Command: ide 48bitLBACounter get IDE 48 bit LBA hits: 0 ------------ Command executed without error. __________________________________________________ _______________ :D |
| All times are GMT -5. The time now is 08:21 AM. |
Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk... Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...