CDROM boot time fsck
Hello - I happened to reboot my server last night without a disk in one of the cdrom drives. It caused the startup process to halt, dropping me to a shell prompt as it tried to fsck the volume. Wasn't happy proceeding until I fed the drive a disk. In my environment this is A Bad Thing; there may be a disk in there or not, I need the freaking server to come up and start running regardless. I checked my fstab, and the cdroms are listed thusly: /dev/acd0c /cdrom cd9660 ro,auto 0 0 /dev/acd1c /cdrom1 cd9660 ro,auto 0 0 Looking at the man page, the last column indicates the fsck type, and 0 is supposed to mean that the device doesn't need to be checked during startup. Am I doing something wrong, or is something broken? 4.6.2-STABLE, BTW. KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CDROM boot time fsck
Hello - I happened to reboot my server last night without a disk in one of the cdrom drives. It caused the startup process to halt, dropping me to a shell prompt as it tried to fsck the volume. Wasn't happy proceeding until I fed the drive a disk. In my environment this is A Bad Thing; there may be a disk in there or not, I need the freaking server to come up and start running regardless. I checked my fstab, and the cdroms are listed thusly: /dev/acd0c /cdrom cd9660 ro,auto 0 0 /dev/acd1c /cdrom1 cd9660 ro,auto 0 0 Looking at the man page, the last column indicates the fsck type, and 0 is supposed to mean that the device doesn't need to be checked during startup. Am I doing something wrong, or is something broken? 4.6.2-STABLE, BTW. I think you also want to make it 'noauto' rather than 'auto'. With the auto, you are telling it to try and mount the device and since there is no disk in, it can't. jerry KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CDROM boot time fsck
On Fri, 11 Oct 2002, Jerry McAllister wrote: I happened to reboot my server last night without a disk in one of the cdrom drives. It caused the startup process to halt, dropping me to a shell prompt as it tried to fsck the volume. Wasn't happy proceeding until I fed the drive a disk. In my environment this is A Bad Thing; there may be a disk in there or not, I need the freaking server to come up and start running regardless. I checked my fstab, and the cdroms are listed thusly: /dev/acd0c /cdrom cd9660 ro,auto 0 0 /dev/acd1c /cdrom1 cd9660 ro,auto 0 0 Looking at the man page, the last column indicates the fsck type, and 0 is supposed to mean that the device doesn't need to be checked during startup. Am I doing something wrong, or is something broken? 4.6.2-STABLE, BTW. I think you also want to make it 'noauto' rather than 'auto'. With the auto, you are telling it to try and mount the device and since there is no disk in, it can't. Hmm. I thought of that, but realistically wouldn't you WANT your cdroms to be automount for just that reason - they're removable media, for pete's sake. I'm coming from a Solaris background, where this is handled completely differently. I guess I'm looking for the best practice method. KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CDROM boot time fsck
On Fri, 11 Oct 2002, Cliff Sarginson wrote: /dev/acd0c /cdrom cd9660 ro,auto 0 0 /dev/acd1c /cdrom1 cd9660 ro,auto 0 0 Looking at the man page, the last column indicates the fsck type, and 0 is supposed to mean that the device doesn't need to be checked during startup. Am I doing something wrong, or is something broken? 4.6.2-STABLE, BTW. I think you also want to make it 'noauto' rather than 'auto'. With the auto, you are telling it to try and mount the device and since there is no disk in, it can't. Hmm. I thought of that, but realistically wouldn't you WANT your cdroms to be automount for just that reason - they're removable media, for pete's sake. I'm coming from a Solaris background, where this is handled completely differently. No,no. Automount makes no sense at all, it means you have to have a CD in there, also what if you are using a CD without a filesystem on it ? E.g. one you have dd'ed something to. Ok, then. Thanks very much for the help, guys! KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CDROM boot time fsck
On Fri, 11 Oct 2002, Cliff Sarginson wrote: /dev/acd0c /cdrom cd9660 ro,auto 0 0 /dev/acd1c /cdrom1 cd9660 ro,auto 0 0 Looking at the man page, the last column indicates the fsck type, and 0 is supposed to mean that the device doesn't need to be checked during startup. Am I doing something wrong, or is something broken? 4.6.2-STABLE, BTW. I think you also want to make it 'noauto' rather than 'auto'. With the auto, you are telling it to try and mount the device and since there is no disk in, it can't. Hmm. I thought of that, but realistically wouldn't you WANT your cdroms to be automount for just that reason - they're removable media, for pete's sake. I'm coming from a Solaris background, where this is handled completely differently. No,no. Automount makes no sense at all, it means you have to have a CD in there, also what if you are using a CD without a filesystem on it ? E.g. one you have dd'ed something to. Ok, then. Thanks very much for the help, guys! CDs aren't necessarily mounted to use. Only if they have a file system are they mounted. Otherwise they are read directly in some fashion (depending on what they are, data file, music, etc). If you have auto there, it means that it will try and mount a file system from that device to whatever mount point you specify whenever a mount -a is done. Since there is often not a Cd with a file system on it in the drive you don't want it to be auto. You or your script or whatever you are using needs to do the mount specifically when you know a Cd with file system is there. It doesn't mean quite the same thing as autostart when you plug in a CD. I seem to remember some sort of similar distinction made in Solaris too though it has been quite a while and they like to have all these GUI things in Solaris to prevent you from knowing what is going on so it may not look like it any more. jerry KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
