Re: Moved drives ...
On 03/15/12 01:11, ill...@gmail.com wrote: On 14 March 2012 17:39, David Walkerdavidianwal...@gmail.com wrote: Hey. I had installed 9.0 to a SATA drive (ada1 I think) and went to install Windows on a higher numbered drive but Windows doesn't like that or so I gathered. Anyway, I moved drives around and installed Windows - FreeBSD is now ada2 I think. I'm used to OpenBSD where fixing this is a vi fstab ... What's the procedure on FreeBSD? Yes, you can change the fstab (if you can get in via mountroot: at the boot prompt, I believe) from single user mode. If you'd've used labels (either glabel or tunefs -L) you'd not have to change your /etc/fstab at all. I'll second that remark on labelling filesystems. My life has become much easier since I did all mine - the 8.2-9.0 disk naming switch from /dev/adi to /dev/adaj had absolutely no effect. Take a look at Warren Block's excellent page on the subject: http://www.wonkity.com/~wblock/docs/html/labels.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
Arthur Chance writes: I'll second that remark on labelling filesystems. My life has become much easier since I did all mine - the 8.2-9.0 disk naming switch from /dev/adi to /dev/adaj had absolutely no effect. Take a look at Warren Block's excellent page on the subject: http://www.wonkity.com/~wblock/docs/html/labels.html /Caveat emptor/: following these instructions, I have been unable to get this to work on FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012 amd64 Specificelly, the drives get labeled, but the infrastructure necessary to mount using those labels does not happen. After talking with Warren, all we can figure out is it isn't just me. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
On Thu, 15 Mar 2012, Robert Huff wrote: Arthur Chance writes: I'll second that remark on labelling filesystems. My life has become much easier since I did all mine - the 8.2-9.0 disk naming switch from /dev/adi to /dev/adaj had absolutely no effect. Take a look at Warren Block's excellent page on the subject: http://www.wonkity.com/~wblock/docs/html/labels.html /Caveat emptor/: following these instructions, I have been unable to get this to work on FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012 amd64 Specificelly, the drives get labeled, but the infrastructure necessary to mount using those labels does not happen. After talking with Warren, all we can figure out is it isn't just me. These are two different types of label. Filesystem labels have always worked for me. Those are the ones shown in that article. The recent problems have been with GPT labels, which recently don't want to appear in /dev/gpt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
Hey. On 15/03/2012, ill...@gmail.com ill...@gmail.com wrote: Yes, you can change the fstab (if you can get in via mountroot: at the boot prompt, I believe) from single user mode. I've read boot(8) to some degree and tried interrupting boot and so on. At some point I get a ... mountroot ... prompt which I guess is what you refer to. I'm not sure how to influence this - there seems to be no keyboard control at any rate ... I've decided to re-install FreeBSD rather than try to learn about this - lazy. During install, although FreeBSD correctly recognizes all the drives and allows me to select one as a target and use whole, when it gets to slicing up the drive and presents the list of all drives, it incorrectly shows the first drive (the Windows drive) as having UFS partitions and so on - that drive is a single NTFS slice ... Needless to say there's no way I'm proceeding with install. So I leave the cabling order (which is what I originally changed prompting me to email the list) but unplug the Windows drive and install FreeBSD. Reboot and ... same situation. Sort of expected. Presumably, this is an understood situation with a simple workaround (failed drives etcetera). Please let me know (man pages accompanied by cluesticks are fine - I'm new here). If you'd've used labels (either glabel or tunefs -L) you'd not have to change your /etc/fstab at all. I'd have no problem with that ... except it's not given as an option during install as far as I can see. -- -- Best wishes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
On Fri, 16 Mar 2012 02:13:40 +1030, David Walker wrote: I've read boot(8) to some degree and tried interrupting boot and so on. At some point I get a ... mountroot ... prompt which I guess is what you refer to. I'm not sure how to influence this - there seems to be no keyboard control at any rate ... I think you need a regular keyboard here (AT or PS/2), unless your BIOS offers a USB keyboard legacy support. I've decided to re-install FreeBSD rather than try to learn about this - lazy. You could have used UFSIDs (unique file system identifiers) as described in the handbook - it's an alternative to using GPT labels (currently looks problematic) or UFS labels (should work). 20.7 Labeling Disk Devices http://www.freebsd.org/doc/handbook/geom-glabel.html (bottom of page) During install, although FreeBSD correctly recognizes all the drives and allows me to select one as a target and use whole, when it gets to slicing up the drive and presents the list of all drives, it incorrectly shows the first drive (the Windows drive) as having UFS partitions and so on - that drive is a single NTFS slice ... Needless to say there's no way I'm proceeding with install. Maybe misinterpretation of some remains of GPT partitioning? So I leave the cabling order (which is what I originally changed prompting me to email the list) but unplug the Windows drive and install FreeBSD. Reboot and ... same situation. Sort of expected. Have you considered performing a manual installation per shell commands? It's not that difficult and allows you to walk around problems that may reside inside the installer. In worst case, make sure to remove all remains of a previous partitioning (clean install). If you'd've used labels (either glabel or tunefs -L) you'd not have to change your /etc/fstab at all. I'd have no problem with that ... except it's not given as an option during install as far as I can see. Is is _indirectly_ given: Start a shell, mount the drive and edit the file manually. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
On 03/15/12 15:25, Warren Block wrote: On Thu, 15 Mar 2012, Robert Huff wrote: Arthur Chance writes: I'll second that remark on labelling filesystems. My life has become much easier since I did all mine - the 8.2-9.0 disk naming switch from /dev/adi to /dev/adaj had absolutely no effect. Take a look at Warren Block's excellent page on the subject: http://www.wonkity.com/~wblock/docs/html/labels.html /Caveat emptor/: following these instructions, I have been unable to get this to work on FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012 amd64 Specificelly, the drives get labeled, but the infrastructure necessary to mount using those labels does not happen. After talking with Warren, all we can figure out is it isn't just me. These are two different types of label. Filesystem labels have always worked for me. Those are the ones shown in that article. The recent problems have been with GPT labels, which recently don't want to appear in /dev/gpt. Ouch. I've converted completely to GPT disks and labels. Fortunately I stick to RELEASE so I'm not affected. I presume this is some sort of regression in HEAD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Moved drives ...
Hey. I had installed 9.0 to a SATA drive (ada1 I think) and went to install Windows on a higher numbered drive but Windows doesn't like that or so I gathered. Anyway, I moved drives around and installed Windows - FreeBSD is now ada2 I think. I'm used to OpenBSD where fixing this is a vi fstab ... What's the procedure on FreeBSD? Best wishes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Moved drives ...
On 14 March 2012 17:39, David Walker davidianwal...@gmail.com wrote: Hey. I had installed 9.0 to a SATA drive (ada1 I think) and went to install Windows on a higher numbered drive but Windows doesn't like that or so I gathered. Anyway, I moved drives around and installed Windows - FreeBSD is now ada2 I think. I'm used to OpenBSD where fixing this is a vi fstab ... What's the procedure on FreeBSD? Yes, you can change the fstab (if you can get in via mountroot: at the boot prompt, I believe) from single user mode. If you'd've used labels (either glabel or tunefs -L) you'd not have to change your /etc/fstab at all. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
