Re: Broken Disk
Hi, Through a combination of this list's suggestions, I managed to get fdisk to successfully operate on my disk. Thanks. However, the step about 'editing my label' as given in the handbook: # disklabel -e da1s1 # Edit the disklabel just created. is not something I really understand. Where is some nice documentation on this? -- -- Jason Dusek (`-''-/).___..--''`-._ -- | `6_ 6 ) `-. ( ).`-.__.`) -- | (_Y_.)' ._ ) `._ `. ``-..-' -- | _..`--'_..-_/ /--'_.' ,' -- | (il),-'' (li),' ((!.-' -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken Disk
Jason Dusek wrote: Hi, Through a combination of this list's suggestions, I managed to get fdisk to successfully operate on my disk. Thanks. However, the step about 'editing my label' as given in the handbook: # disklabel -e da1s1 # Edit the disklabel just created. is not something I really understand. Where is some nice documentation on this? man disklabel is pretty comprehensive. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken Disk
Jason Dusek wrote: Hi, Through a combination of this list's suggestions, I managed to get fdisk to successfully operate on my disk. Thanks. However, the step about 'editing my label' as given in the handbook: # disklabel -e da1s1 # Edit the disklabel just created. is not something I really understand. Where is some nice documentation on this? man disklabel is pretty comprehensive. Yes. But, you have to read it together with man fdisk to make any sense of it and even then the writing is rather convoluted and confusing. They could both use a complete systematic rewrite. I don't think I know enough of the extra stuff (the stuff I don't usually use) to do it or I would try it. So, anyway, user questions should not be surprising. (But please ask reasonably specific questions or it is hard to give a relevant answer) jerry -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [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: Broken Disk
On Mon, May 24, 2004 at 03:24:33PM -0400, Jerry McAllister wrote: man disklabel is pretty comprehensive. Yes. But, you have to read it together with man fdisk to make any sense of it and even then the writing is rather convoluted and confusing. They could both use a complete systematic rewrite. I don't think I know enough of the extra stuff (the stuff I don't usually use) to do it or I would try it. Actually, the disklabel application and man page got a complete rewrite and a change of name for 5.x. Compare and contrast: http://www.freebsd.org/cgi/man.cgi?query=disklabelapropos=0sektion=0manpath=FreeBSD+4.9-stableformat=html http://www.freebsd.org/cgi/man.cgi?query=bsdlabelapropos=0sektion=0manpath=FreeBSD+5.2-RELEASE+and+Portsformat=html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp1wOXOLnOH7.pgp Description: PGP signature
Re: Broken Disk
On Mon, May 24, 2004 at 03:24:33PM -0400, Jerry McAllister wrote: man disklabel is pretty comprehensive. =20 Yes. But, you have to read it together with man fdisk to make any sense of it and even then the writing is rather convoluted and confusing.= =20 They could both use a complete systematic rewrite. I don't think I know enough of the extra stuff (the stuff I don't usually use) to do=20 it or I would try it. Actually, the disklabel application and man page got a complete rewrite and a change of name for 5.x. Compare and contrast: Oh, good. I will have to check it out. Except for a little tinkering to check out device support, I haven't had time (or a free machine) to look at 5.xxx yet. jerry http://www.freebsd.org/cgi/man.cgi?query=3Ddisklabelapropos=3D0sektio= n=3D0manpath=3DFreeBSD+4.9-stableformat=3Dhtml http://www.freebsd.org/cgi/man.cgi?query=3Dbsdlabelapropos=3D0sektion= =3D0manpath=3DFreeBSD+5.2-RELEASE+and+Portsformat=3Dhtml Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAslO5iD657aJF7eIRArmzAJ4rddf407grBOg6jKr6XM5i67hEtQCgl1Qc v/DC0VZU1gxkoiJHEYoI2Fw= =Wehq -END PGP SIGNATURE- --YiEDa0DAkWCtVeE4-- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken Disk
So, anyway, user questions should not be surprising. (But please ask reasonably specific questions or it is hard to give a relevant answer) jerry Fair Enough, My question is 'how do I edit a disklabel?' I assume that I am supposed to add an 'e' partition, but it seems that the c partition has eaten my disk. The partition file looks like this: ...stuff in the front omitted... 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 7816403704.2BSD 2048 1638489 # (Cyl.0 - 12406*) Does this mean that my disk is 'dangerously dedicated'? Isn't the fstype supposed to be 'ufs'? How do I toggle soft updates? I want to use this disk as backup media, so is one undifferentiated partition a good idea? -- -- Jason Dusek (`-''-/).___..--''`-._ -- | `6_ 6 ) `-. ( ).`-.__.`) -- | (_Y_.)' ._ ) `._ `. ``-..-' -- | _..`--'_..-_/ /--'_.' ,' -- | (il),-'' (li),' ((!.-' -- Jerry McAllister wrote: Jason Dusek wrote: Hi, Through a combination of this list's suggestions, I managed to get fdisk to successfully operate on my disk. Thanks. However, the step about 'editing my label' as given in the handbook: # disklabel -e da1s1 # Edit the disklabel just created. is not something I really understand. Where is some nice documentation on this? man disklabel is pretty comprehensive. Yes. But, you have to read it together with man fdisk to make any sense of it and even then the writing is rather convoluted and confusing. They could both use a complete systematic rewrite. I don't think I know enough of the extra stuff (the stuff I don't usually use) to do it or I would try it. So, anyway, user questions should not be surprising. (But please ask reasonably specific questions or it is hard to give a relevant answer) jerry -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [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: Broken Disk
So, anyway, user questions should not be surprising. (But please ask reasonably specific questions or it is hard to give a relevant answer) jerry Fair Enough, My question is 'how do I edit a disklabel?' I assume that I am supposed to add an 'e' partition, but it seems that the c partition has eaten my disk. The partition file looks like this: Ah, I think that is mentioned in some part of the documentation, but the 'c' partition is special and actually refers to the whole slice. Generally it should say 'unused' in the fstype column for partition c. Then you just use it as a reference number and do not consider it in the partitions you create. Here is a disk on a machine I am logged in to right now for example. 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 251494404.2BSD 2048 1638489 # (Cyl.0 - 156*) b: 4618240 2514944 swap# (Cyl. 156*- 444*) c: 355517820unused0 0 # (Cyl.0 - 2212*) e: 2514944 71331844.2BSD 2048 1638489 # (Cyl. 444*- 600*) f: 25903654 96481284.2BSD 2048 1638489 # (Cyl. 600*- 2212*) Note that the a,b,e and f partitions add up to the c partition and that the fstype for c is unused. jerry ...stuff in the front omitted... 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 7816403704.2BSD 2048 1638489 # (Cyl.0 - 12406*) Does this mean that my disk is 'dangerously dedicated'? Isn't the fstype supposed to be 'ufs'? How do I toggle soft updates? I want to use this disk as backup media, so is one undifferentiated partition a good idea? -- -- Jason Dusek (`-''-/).___..--''`-._ -- | `6_ 6 ) `-. ( ).`-.__.`) -- | (_Y_.)' ._ ) `._ `. ``-..-' -- | _..`--'_..-_/ /--'_.' ,' -- | (il),-'' (li),' ((!.-' -- Jerry McAllister wrote: Jason Dusek wrote: Hi, Through a combination of this list's suggestions, I managed to get fdisk to successfully operate on my disk. Thanks. However, the step about 'editing my label' as given in the handbook: # disklabel -e da1s1 # Edit the disklabel just created. is not something I really understand. Where is some nice documentation on this? man disklabel is pretty comprehensive. Yes. But, you have to read it together with man fdisk to make any sense of it and even then the writing is rather convoluted and confusing. They could both use a complete systematic rewrite. I don't think I know enough of the extra stuff (the stuff I don't usually use) to do it or I would try it. So, anyway, user questions should not be surprising. (But please ask reasonably specific questions or it is hard to give a relevant answer) jerry -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [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] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken Disk
On Fri, May 21, 2004 at 07:36:11AM -0500, Jason Dusek wrote: I am trying to put a new disk on my system. I read the description of the process in FreeBSD Unleashed and apparently I misunderstood it, because I ended up installing a boot manager on the new disk. Now I can not mount it - I get error messages like: Presence of absence of a boot manager on the drive should make any difference at all once the system is up and running. # mount /dev/ad1e /mnt/backup operation not permitted /dev/ad1e is a very odd device name to be using. As far as I remember that's a backwards compatability thing from changes that were made somewhere around the FreeBSD-3.x timeframe. You probably want /dev/ad1s1e How do I 'start over'? I have tried to add this disk many times with /stand/sysinstall. Eventually I gave up and went to the command line utilities as outlined in the handbook. The error I got was interesting, but I have no idea what it means: # fdisk -BI ad1 *** Working on device /dev/ad1 *** fdisk: invalid fdisk partition table found You're going about this the right way, but you've run into a disk with a label so scrambled it's confusing fdisk(8). Old hacky trick is to zero out the first few blocks of the drive, so that fdisk(8) thinks the disk is completely virgin: # dd if=/dev/zero of=/dev/ad1 bs=512 count=10 Note that this will completely trash anything already on the drive. Then use fdisk(8), disklabel(8)/bsdlabel(8), newfs(8) to create filesystems. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgppHSkUH9F9Z.pgp Description: PGP signature
Re: Broken Disk
On Friday 21 May 2004 22:26, Matthew Seaman wrote: On Fri, May 21, 2004 at 07:36:11AM -0500, Jason Dusek wrote: I am trying to put a new disk on my system. I read the description of the process in FreeBSD Unleashed and apparently I misunderstood it, because I ended up installing a boot manager on the new disk. Now I can not mount it - I get error messages like: Presence of absence of a boot manager on the drive should make any difference at all once the system is up and running. # mount /dev/ad1e /mnt/backup operation not permitted /dev/ad1e is a very odd device name to be using. As far as I remember that's a backwards compatability thing from changes that were made somewhere around the FreeBSD-3.x timeframe. You probably want /dev/ad1s1e Yes, but at least upto FreeBSD-4.9 /dev/ad1e is understood and likely to be present. I believe it is the e-partition on the first BSD slice on the disk whatever slice that might be. The error message is not the one usually reported for a non-existant device; but when the operator has insufficient privilege. For the OP you (normally) need to be root to mount disks. Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
