Re: Larger Hard Drive
Brian Astill [EMAIL PROTECTED] writes: root@BAPhD ~ #fdisk -BI ad2 *** Working on device /dev/ad2 *** root@BAPhD ~ #Jan 18 15:21:19 BAPhD /kernel: ad2: cannot find label (no disk label) Jan 18 15:21:19 BAPhD /kernel: ad2s1: cannot find label (no disk label) I was playing with fdisk/disklabel yesterday, and there's some strange stuff going on there, like maybe the disk driver gets confused. Anyway, there's a good chance you can solve you problem by following the steps which have been (mis) placed in the disklabel(8) manpage near the words Completely wipe any prior information on the disk. Beware that fdisk -BI doesn't necessarily write boot blocks, that fdisk -I might write them, and both sometimes ignore answers to their prompts about whether to write them. Go figure. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Larger Hard Drive (2)
Brian Astill [EMAIL PROTECTED] writes: BUT, when I create a directory in which to mount ad2 I get: root@BAPhD ~ #ls -R /usr/local/new opt usr var /usr/local/new/opt: /usr/local/new/usr: local /usr/local/new/usr/local: /usr/local/new/var: Note that /usr/local is not shown as a separate entity. Similarly, there is no root partition. Obviously, I am doing something wrong, or incompletely - but what? It's unclear to me (1) what you did and (2) what you're trying to accomplish. I'll try to guess on (2). Typically, when trying to transfer an OS to a new disk, you'd mount one of the new partitions, say a (for /), on some directory, say dir, and then xfr the data with something like: cd dir; dump -f - / | restore -rf - Rinse and repeat, then, with a mounted on dir, prepare dir/etc/fstab for rebooting and swap disks or reconfigure your boot managers, etc. (Theoretically, the stuff you dump should be mounted read-only or not mounted, probably in single-user mode.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Larger Hard Drive
I want to move my FBSD partitions to one larger HD. Shouldn't be hard. ;-) The system recognises my new HD at ad2 ad0: 8063MB WDC WD84AA [16383/16/63] at ata0-master UDMA66 ad1: 8056MB ST38421A [16368/16/63] at ata0-slave UDMA66 ad2: 19470MB QUANTUM FIREBALLlct20 20 [39560/16/63] at ata1-master UDMA100 acd0: CD-RW SONY CD-RW CRX140E at ata1-slave PIO4 BUT when I try to initialise ad2 ... :-( root@BAPhD ~ #fdisk -BI ad2 *** Working on device /dev/ad2 *** root@BAPhD ~ #Jan 18 15:21:19 BAPhD /kernel: ad2: cannot find label (no disk label) Jan 18 15:21:19 BAPhD /kernel: ad2s1: cannot find label (no disk label) root@BAPhD ~ #disklabel -w ad2 auto disklabel: No space left on device root@BAPhD ~ #Jan 18 15:21:52 BAPhD /kernel: ad2: cannot find label (no disk label) Jan 18 15:21:52 BAPhD /kernel: ad2s1: cannot find label (no disk label) Jan 18 15:21:52 BAPhD /kernel: ad2: cannot find label (no disk label) Jan 18 15:21:52 BAPhD /kernel: ad2s1: cannot find label (no disk label) I looked at the drive using Partition Magic v7 (using Windoze - ouch!) which recognised the drive as FBSD/386. Thought I would change this to unformatted in the hope this might help, then rebooted. Same result as above. :-( At this point I thought I had better ask for help! :-) -- Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Larger Hard Drive (2)
My sincere apologies, fellow followers of the Beastie! I managed to slice ad2 using /stand/sysinstall. However disklabel -r shows: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 819200 0 4.2BSD 2048 16384 93 # (Cyl. 0 - 812*) b: 2017089 37859328 swap # (Cyl. 37558*- 39559*) c: 39876417 0 unused 0 0 # (Cyl. 0 - 39559*) e: 512000 819200 4.2BSD 0 0 0 # (Cyl. 812*- 1320*) f: 14680064 1331200 4.2BSD 0 0 0 # (Cyl. 1320*- 15884*) g: 14680064 16011264 4.2BSD 0 0 0 # (Cyl. 15884*- 30447*) h: 7168000 30691328 4.2BSD 0 0 0 # (Cyl. 30447*- 37558*) which is fine - what I expected AND what I asked for! :-) The two larger partitions are for /usr and /usr/local. The other partitions are for / /var and /opt. BUT, when I create a directory in which to mount ad2 I get: root@BAPhD ~ #ls -R /usr/local/new opt usr var /usr/local/new/opt: /usr/local/new/usr: local /usr/local/new/usr/local: /usr/local/new/var: Note that /usr/local is not shown as a separate entity. Similarly, there is no root partition. Obviously, I am doing something wrong, or incompletely - but what? Thanks for you anticipated help. -- Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
