Re: SCSI Shock Advice !
Graham Bentley wrote: Hi All, When I was about to install the new drive which was sitting on top of the system box I tilted the box to move the disc access LED lead onto the SCSI card. My nice new SCSI disc slid off and hit the MDF worktop - Agh ! I reckon the drop height was about 14 ~ do you think this would have exceed the G Force limit and invalidated my warranty / casued any damage ? The reason for asking is that I never really got up close and personal with a SCSI disc before and it does make some odd noises? Currently there is a frequent one every so often - its two freequencies that last about a second or two each. What model is it? A 36LZX or 73LZX? If so they do make an awful screeching noise. When I got mine (off eBay) I thought the bearings were on their way out, but searching Hitachi's website (Hitachi now own IBM's HD division) threw up this http://www.hitachigst.com/hdd/support/qcheck.htm#a4 Mine makes this noise a lot more frequently than once per minute that they state and it's extremely annoying. My Seagate OTOH is almost silent except when it's doing some serious thrashing. HTH Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Mark, Yep, mine makes that 2 tone screech noise much more frequently than i woudl like !!! Its an IC35L The site has a nice util called the drive fitness test :- http://www.hitachigst.com/hdd/support/download.htm Fits on a floppy and tests your SCSI drive. I did this because my supplier told me to ; I was complaining about the noise :) They said - run this thoro - if it doesnt throw up any errors - your fine ! They also put this :- (FYI, you'll normally find ~1% of a disk is actually dead from the factory, but that there's actually 109% of the available disk space there. Over time, the drive will invisibly map bad sectors to unalocated ones (called spanning sectors). when you run out of spanning sectors, (ie, its spanned out) THEN it's time for a new one, as that's normally the point at which the drive packs up) Anyways, mine seems to have survived the minor drop without any probs :) Crazy to think ~ VLSI has come so far yet we are all so dependant on spinning discs motors and magnets :) Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
What is the best / safest way to do a dis clone in this case? I would use the method that is described in the FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Life would be easier if I had the source code. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Sep 2004 09:01, Graham Bentley wrote: Thanks for replies, however I need advise on cloning the IDE to the SCSI disc. G4U did not finish correctly and once I had made changes to fstab and booted the fs I got some pretty severe errors. /usr was inaccessible and I ended up using Freesbie to re-edit fstab to get a booting system. I think the problem is that the SCSI disc is 38GB (only 1.7GB used) and the IDE is 40GB. What is the best / safest way to do a dis clone in this case? Thanks again Graham Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Have a look at the FAQ: file:/usr/share/doc/faq/disks.html#NEW-HUGE-DISK Basically, you just dump each partition, piping dump's output to restore. This will copy everything across, including device files etc. Then edit /etc/fstab to point the partitions to /dev/da??? instead of /dev/ad??? for each partition. Cheers, - -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBT9T3fITqkXhImmIRAkiBAJ9H/bImIliUsytEtM5B1olrcghVLgCeM/rt Gwz5CmIt3I/rD9zHhO6c4ek= =L19a -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Hi, Thanks for replies, however I need advise on cloning the IDE to the SCSI disc. G4U did not finish correctly and once I had made changes to fstab and booted the fs I got some pretty severe errors. /usr was inaccessible and I ended up using Freesbie to re-edit fstab to get a booting system. I think the problem is that the SCSI disc is 38GB (only 1.7GB used) and the IDE is 40GB. What is the best / safest way to do a disk clone in this case? Don't use any of the cloning utilities (not even dd) because you are not trying to make an exact byte for byte clone, but rather a functional copy. That is quite different. The best thing is to create the new file systems eg slice (fdisk) partition (disklabel or bsdlabel in 5.xxx) and build the file system (newfs) and then mount the new file systems to a temporary mount mount and transfer each file system separately by running dump and restore. Note: To make a bootable copy you will need to put in an MBR when you do the fdisk to create the slice and a boot block when you do t the disklabel/bsdlabel when you do the partitioning. Don't leave those out. If you have room, you can run a dump to a file in spare space somewhere and then restore from that file. If you don't have the extra space, you can pipe a dump of the old fs to a restore to the new one. Make sure you cd in to the new file system before doing the restore whichever way you are doing it. This is covered pretty much in the man pages of dump and restore. But, say your SCSI is da0 and you created one slice and did the label/partitioning ok and newfs-ed all the partitions and now you want to put the old root on the new disk. cd / mkdir newroot mount /dev/da0s1a /newroot cd /newroot dump 0af - / | restore rf - Do the similar for each of the file systems you want/need to move over. That probably means all of them. When you are done, the only thing left to do, besides checking things out to make sure they look good is to modify the new copy of /etc/fstab so the devices to mount will now be da0s1.. instead of ad0s1.. You can also get rid of all the 'restoresymtable' files in each new filesystem. Restore uses those to keep track of itself and they are no longer needed once it has successfully completed. You should then be able to shuffle any disks and bios you need to to make the SCSI disk the boot device and then boot and run. jerry Thanks again Graham Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Hi, Thanks for replies, however I need advise on cloning the IDE to the SCSI disc. What is the best / safest way to do a disk clone in this case? Don't use any of the cloning utilities (not even dd) because you are not trying to make an exact byte for byte clone, but rather a functional copy. That is quite different. The best thing is to create the new file systems eg slice (fdisk) partition (disklabel or bsdlabel in 5.xxx) and build the file system (newfs) and then mount the new file systems to a temporary mount mount and transfer each file system separately by running dump and restore. Note: To make a bootable copy you will need to put in an MBR when you do the fdisk to create the slice and a boot block when you do t the disklabel/bsdlabel when you do the partitioning. Don't leave those out. If you have room, you can run a dump to a file in spare space somewhere and then restore from that file. If you don't have the extra space, you can pipe a dump of the old fs to a restore to the new one. Make sure you cd in to the new file system before doing the restore whichever way you are doing it. This is covered pretty much in the man pages of dump and restore. But, say your SCSI is da0 and you created one slice and did the label/partitioning ok and newfs-ed all the partitions and now you want to put the old root on the new disk. cd / mkdir newroot mount /dev/da0s1a /newroot cd /newroot dump 0af - / | restore rf - Do the similar for each of the file systems you want/need to move over. That probably means all of them. By the way, I notice that in the FAQ on moving to a huge disk it uses the 'x' switch on the restore and I think it is more appropriate to use 'r'.So, 'restore rf -' as I indicate in my post instead of 'restore xf -' as in the faq. Actually, it might work either way, but I think 'r' is more correct. jerry When you are done, the only thing left to do, besides checking things out to make sure they look good is to modify the new copy of /etc/fstab so the devices to mount will now be da0s1.. instead of ad0s1.. You can also get rid of all the 'restoresymtable' files in each new filesystem. Restore uses those to keep track of itself and they are no longer needed once it has successfully completed. You should then be able to shuffle any disks and bios you need to to make the SCSI disk the boot device and then boot and run. jerry Thanks again Graham Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Jerry McAllister [EMAIL PROTECTED] writes: By the way, I notice that in the FAQ on moving to a huge disk it uses the 'x' switch on the restore and I think it is more appropriate to use 'r'.So, 'restore rf -' as I indicate in my post instead of 'restore xf -' as in the faq. Actually, it might work either way, but I think 'r' is more correct. It will, indeed, work either way, but the r flag will do a newfs. Because the example had already done a newfs, this is redundant (and wipees out any special parameters you may have used in the original newfs invocation). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Jerry McAllister [EMAIL PROTECTED] writes: By the way, I notice that in the FAQ on moving to a huge disk it uses the 'x' switch on the restore and I think it is more appropriate to use 'r'.So, 'restore rf -' as I indicate in my post instead of 'restore xf -' as in the faq. Actually, it might work either way, but I think 'r' is more correct. It will, indeed, work either way, but the r flag will do a newfs. Because the example had already done a newfs, this is redundant (and wipees out any special parameters you may have used in the original newfs invocation). Hmmm. I have restored lots of dumps using the 'r' switch and never saw it do a newfs. In fact the man page for restore tells you to make sure it is pristine by doing a newfs before the restore. Actually, I do restore -r into directories that are not even the root of a file system and had no problem or seen any newfs occur. -- I do that when merging one system to another and don't want to deal with naming all the files on the restore. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Hi All, Need some quick advice on the following. I recently added an Adaptec 29160N card and an IBM SCSI disc to my server box which previously had just an IDE disc. I cloned the disc using G4U http://www.feyrer.de/g4u/ and set SCSI as the first boot device in the BIOS (disabled 2nd,3rd,4th choices) So, now I can boot the kernel however mounts are still referencing the IDE disc so the system is still using the file system on that. I need to use the file system on the SCSI disc. Is this just a case of changing FSTAB ? Or, are there more edits to make ? I don't know about the rest of your possible problem - eg bouncing it on the bench, but you have to correctly reference the devices for the disk. IDE drivea are ad. and SCSI drives are da. eg the first IDE disk, first slice and partition a would be /dev/ad0s1a and the first SCSI, first slice, partition a would be /dev/da0s1a Make a mount point and then you can hand mount it or make an entry in /etc/fstab for it and do mount -a . If you are FreeBSD 4.xxx or earlier you may need to to a MAKEDEV in the /dev/directory for the device cd /dev ./MAKEDEV da0or da4 or whatever number it is. but, if you only have one SCSI disk, that much should already be there. If you are running 5.xxx, then the dev should be created automagically. If you get it right and the disk is working correctly, then that should be all you need - nothing else to edit. (Odd grinding noises are not normal for SCSI disks) jerry Also, I have to fess up . . . . When I was about to install the new drive which was sitting on top of the system box I tilted the box to move the disc access LED lead onto the SCSI card. My nice new SCSI disc slid off and hit the MDF worktop - Agh ! I reckon the drop height was about 14 ~ do you think this would have exceed the G Force limit and invalidated my warranty / casued any damage ? The reason for asking is that I never really got up close and personal with a SCSI disc before and it does make some odd noises? Currently there is a frequent one every so often - its two freequencies that last about a second or two each. I have heard many an IDE controller go ticky and its nothing like that - sounds more like some kind of self test or something although its fairly frequent. Also, G4U didnt finish nicely as the SCSI is 36GB and the IDE a 40GB - however the system boots ok - guess I havent even used the FS on it yet though . . . Are there any tests I can do like a surface scan etc ? Any comments appreciated ! Graham Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Shock Advice !
Thanks for replies, however I need advise on cloning the IDE to the SCSI disc. G4U did not finish correctly and once I had made changes to fstab and booted the fs I got some pretty severe errors. /usr was inaccessible and I ended up using Freesbie to re-edit fstab to get a booting system. I think the problem is that the SCSI disc is 38GB (only 1.7GB used) and the IDE is 40GB. What is the best / safest way to do a dis clone in this case? Thanks again Graham Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]