Re: Camera SD card mounting problems (defined by systemd)
On Lu, 03 nov 14, 22:20:51, Charles Kroeger wrote: Thanks Eric, you can learn a lot of useful stuff on this list if you just keep poking it. Say something wrong get a clarification. That's good. https://xkcd.com/386/ Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Camera SD card mounting problems (defined by systemd)
On Sat, 01 Nov 2014 11:50:01 +0100 Andrei POPESCU andreimpope...@gmail.com wrote: Why reboot, you can just use 'mount -a'? By the way, 'auto' and 'rw' are default, no need to set them explicitly. Thanks for this information -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cbpm22fa65...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On 03/11/14 07:13, Charles Kroeger wrote: On Sat, 01 Nov 2014 20:10:01 +0100 Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com wrote: I see from other messages in this thread that I'm not the only person to think it equally ludicrous to have a workflow that involves rebooting the entire machine just to mount and unmount a removable block device. Indeed, even editing /etc/fstab doesn't need to be part of such a workflow. Just mark the entry as non-automatic (also correcting your spelling mistake that is the root of your problem here, of course) That was only to mount not unmount. For one thing I don't use this removable block device AKA the SD card enough to have it interfere with my precious workflow. As far as the 'incorrect' spelling of the device, that was only misspelled after systemd came into the picture. That line was read in /etc/fstab with no problems (for years) before it became misspelled. I've already corrected the offending spelling of the device and used the NON systemd methodology as recommended by The Wanderer and Martin Read, preempting your delicate sensibilities. So all is well. Strange that no one has mentioned autofs in this thread, as far as I can see... p. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m38969$ccc$1...@ger.gmane.org
Re: Camera SD card mounting problems (defined by systemd)
On Mon, 03 Nov 2014 17:30:02 +0100 Peter Nieman gmane-a...@t-online.de wrote: no one has mentioned autofs in this thread No, but I will put it in my list of options for /etc/fstab entry. I assume entries like 'autofs' and 'nofail' will soon be obsolete when 'systemd-fstab-generator' becomes de regueur, eh, Jonathan? -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cbq02nfa65...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On Mon, Nov 3, 2014 at 1:32 PM, Charles Kroeger ckro...@frankensteinface.com wrote: On Mon, 03 Nov 2014 17:30:02 +0100 Peter Nieman gmane-a...@t-online.de wrote: no one has mentioned autofs in this thread No, but I will put it in my list of options for /etc/fstab entry. autofs isn't an option for /etc/fstab, it's a completely separate way to specify mounts. For something like an sd card, you would add it to something like /etc/auto.misc instead of /etc/fstab. autofs filesystems are not mounted at boot time, but dynamically, when an application tries to access the contents of the mount point. For example, I have this in /etc/autofs.misc: sdcard -fstype=vfat,gid=video,umask=002 :/dev/disk/by-id/usb-Generic-_SD_MMC_2006041309210-0\:2-part1 and my sdcards are automatically mounted by attempting to read the contents of /var/autofs/misc/sdcard/. Eric -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAC73aR25cvUia7r52Uyq5Z11r3gfhTkHfCpBu_r4sF=qfpf...@mail.gmail.com
Re: Camera SD card mounting problems (defined by systemd)
On Mon, 03 Nov 2014 21:00:02 +0100 Eric Sharkey e...@lisaneric.org wrote: autofs isn't an option for /etc/fstab, it's a completely separate way to specify mounts. For something like an sd card, you would add it to something like /etc/auto.misc instead of /etc/fstab. autofs filesystems are not mounted at boot time, but dynamically, when an application tries to access the contents of the mount point. For example, I have this in /etc/autofs.misc: sdcard -fstype=vfat,gid=video,umask=002 :/dev/disk/by-id/usb-Generic-_SD_MMC_2006041309210-0\:2-part1 and my sdcards are automatically mounted by attempting to read the contents of /var/autofs/misc/sdcard/. Eric Thanks Eric, you can learn a lot of useful stuff on this list if you just keep poking it. Say something wrong get a clarification. That's good. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cbqv0jfa65...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On Sat, 01 Nov 2014 20:10:01 +0100 Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com wrote: I see from other messages in this thread that I'm not the only person to think it equally ludicrous to have a workflow that involves rebooting the entire machine just to mount and unmount a removable block device. Indeed, even editing /etc/fstab doesn't need to be part of such a workflow. Just mark the entry as non-automatic (also correcting your spelling mistake that is the root of your problem here, of course) That was only to mount not unmount. For one thing I don't use this removable block device AKA the SD card enough to have it interfere with my precious workflow. As far as the 'incorrect' spelling of the device, that was only misspelled after systemd came into the picture. That line was read in /etc/fstab with no problems (for years) before it became misspelled. I've already corrected the offending spelling of the device and used the NON systemd methodology as recommended by The Wanderer and Martin Read, preempting your delicate sensibilities. So all is well. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cboknlf7e...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On Sat, 01 Nov 2014 00:30:02 +0100 The Wanderer wande...@fastmail.fm wrote: I suspect that /dev/sde1 exists, but /dev/sde1/ (with the trailing slash) does not - i.e., /dev/sde1 is a device node, not a directory. Yes, the extra forward slash was there (indicating a directory)..interesting. Anyway. I removed the now offending symbol. Thanks for this information. Martin Read zen75...@zen.co.uk wrote: Use the well-documented fstab(5) option nofail, which predates the creation of systemd. I replaced 'auto' in the fstab line with 'nofail.' Thanks for this reminder. I will test out the new configuration tomorrow. If you don't hear from me again it worked. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cbjc24f9sj...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On Vi, 31 oct 14, 14:10:20, Charles Kroeger wrote: I have a line in my /etc/fstab file: #/dev/sde1/ /media/lumix-photos vfat users,rw,auto,iocharset=utf8,umask=000 0 Anytime I want to add photos off the SD card in my camera, I comment out the hashmark add the SD card to the reader, and reboot the computer. Why reboot, you can just use 'mount -a'? By the way, 'auto' and 'rw' are default, no need to set them explicitly. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Camera SD card mounting problems (defined by systemd)
On 11/01/2014 06:26 AM, Andrei POPESCU wrote: On Vi, 31 oct 14, 14:10:20, Charles Kroeger wrote: I have a line in my /etc/fstab file: #/dev/sde1/ /media/lumix-photos vfat users,rw,auto,iocharset=utf8,umask=000 0 Anytime I want to add photos off the SD card in my camera, I comment out the hashmark add the SD card to the reader, and reboot the computer. Why reboot, you can just use 'mount -a'? By the way, 'auto' and 'rw' are default, no need to set them explicitly. Kind regards, Andrei I've seen a number of folks posting about manual mounting with and without use of a file manager with something like gvfs-backends, problems with entries in /etc/fstab, etc. Apropos of no particular knowledge on my part, but of a desire to ask a question that might be a useful -- would pmount be of use to at least some people with problems of this sort? I don't have any of my removable drives / storage devices in /etc/fstab (or I comment them out). I just plug them in and use pmount to mount them. $ ls -l /dev/disks/by-label to see them $ pmount /dev/sdwhatever /media/whatever to mount them. HTH someone. Jape -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5454e480.4040...@comcast.net
Re: Camera SD card mounting problems (defined by systemd)
Charles Kroeger: I think it's ludicrous that adding an SD card that even has its own line in /etc/fstab, throws the whole system into 'emergency' mode. I see from other messages in this thread that I'm not the only person to think it equally ludicrous to have a workflow that involves rebooting the entire machine just to mount and unmount a removable block device. Indeed, even editing /etc/fstab doesn't need to be part of such a workflow. Just mark the entry as non-automatic (also correcting your spelling mistake that is the root of your problem here, of course), so that it has to be explicitly mounted by hand, and then mount and unmount it with the mount and umount commands, or whatever GUI equivalent you may enjoy. And that's just the widespread NON-systemd way of doing things that applies even when one is not using systemd; I'll come to the raw systemd way in my next message. It's the usual way that one handles removable block devices, be they SD cards, CD-ROMs, floppy discs, or something else. Look at http://home.ubalt.edu/abento/linux/terminal/mount.html (to pick an example off the WWW at random) and you'll see this workflow documented 14 years ago. http://codecoffee.com./tipsforlinux/articles/035.html is from 13 years ago and shows the same noauto and mount/umount workflow. There are loads more like these. No rebooting the entire machine, or even editing /etc/fstab, is required. Charles Kroeger: What is meant by media-lumix(back slash!)x2dphotos.mount(?) It's the name of a systemd mount unit. The manual page for systemd.mount(5) tells you about mount units. It refers you to the manual page for systemd.unit(5) for the naming convention. Applying the explanation found on that latter manual page, one can easily see that media-lumix\x2dphotos decodes to the filesystem pathname /media/lumix-photos. So this is the name of the systemd mount unit that has been automatically generated for the /media/lumix-photos directory. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54552bdb.7090...@ntlworld.com
Re: Re: Camera SD card mounting problems (defined by systemd)
The Wanderer: If the mount failing isn't that critical, then the right way to fix the problem under systemd's apparent design would probably be to add the noauto label to the fstab, so that the device will not mount automatically on boot. Actually, that's just the widespread NON-systemd way of doing things, for which systemd has such compatibility mechanisms as systemd-fstab-generator, a program that reads /etc/fstab at bootstrap and that generates a whole load of nonce units that translate fstab records to the systemd way of doing things. Adding noauto and fixing the erroneous device name so that it is correctly spelled is the way to fix things even if one isn't using systemd at all. The raw systemd way of doing things is mount and device units, per the systemd.mount(5) and systemd.device(5) manual pages. In the raw systemd way of doing things, there's a device unit named dev-sde1.device which is a base requirement for a mount unit named media-lumix\x2dphotos.mount. If made by hand, they would look something like: # /etc/systemd/system/dev-sde1.device [Unit] Description=Device unit for %N # /etc/systemd/system/media-lumix\x2dphotos.mount [Unit] Description=Mount unit for %N # For exposition: BindsTo=dev-sde1.device [Install] RequiredBy=local-fs.target [Mount] What=/dev/sde1 Where=%N Type=vfat Options=users,iocharset=utf8,umask=000 And these are, in essence, what systemd-fstab-generator and systemd-udevd generate on the fly. There will be an auto-generated /run/systemd/generator/media-lumix\x2dphotos.mount similar to the above. If the fstab record is auto there will also be a symbolic link in /run/systemd/generator/local-fs.target.requires pointing to the mount unit. When the /dev/sde1 device appears, dev-sde1.device is auto-generated and started by systemd-udevd. Mounting and unmounting are thus start and stop actions on this unit: * systemctl start media-lumix\x2dphotos.mount * systemctl stop media-lumix\x2dphotos.mount Turning bootstrap-time automatic startup on and off is simply a matter of enabling and disabling the specified requires relationship from local-fs.target: * systemctl enable media-lumix\x2dphotos.mount * systemctl disable media-lumix\x2dphotos.mount One could even make an automount unit (which systemd-fstab-generator auto-generates when it sees x-systemd.automount in an /etc/fstab record): # /etc/systemd/system/media-lumix\x2dphotos.automount [Unit] Description=Automount unit for %N [Automount] Where=%N [Install] RequiredBy=local-fs.target -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54552be2.7090...@ntlworld.com
Camera SD card mounting problems (defined by systemd)
I have a line in my /etc/fstab file: #/dev/sde1/ /media/lumix-photos vfat users,rw,auto,iocharset=utf8,umask=000 0 Anytime I want to add photos off the SD card in my camera, I comment out the hashmark add the SD card to the reader, and reboot the computer. The SD card is mounted (/dev/sde1/) inside the folder lumix-photos. I then use shotwell to add the new photos that can then be worked over in GIMP. This solution has worked flawlessly for years, until now: log: mount: special device /dev/sde1/ does not exist log: media-lumix\x2dphotos.mount has failed dependency has failed for local file system log: defined-by: systemd Since /dev/sde1 is listed and described from the fdisk -l command how can it 'not' exits? What is meant by media-lumix(back slash!)x2dphotos.mount(?) Adding the SD card into the card reader after editing /etc/fstab then rebooting, causes the computer to go into emergency (? WTF) mode. Ctrl+d doesn't fix it. Going to the command prompt with the root password is the only solution. (i.e. editing the /etc/fstab file back like it was, removing the SD card, and rebooting.) I think it's ludicrous that adding an SD card that even has its own line in /etc/fstab, throws the whole system into 'emergency' mode. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cbi1kcf9sj...@mid.individual.net
Re: Camera SD card mounting problems (defined by systemd)
On 10/31/2014 at 02:10 PM, Charles Kroeger wrote: I have a line in my /etc/fstab file: #/dev/sde1/ /media/lumix-photos vfat users,rw,auto,iocharset=utf8,umask=000 0 Anytime I want to add photos off the SD card in my camera, I comment out the hashmark add the SD card to the reader, and reboot the computer. The SD card is mounted (/dev/sde1/) inside the folder lumix-photos. I then use shotwell to add the new photos that can then be worked over in GIMP. This solution has worked flawlessly for years, until now: log: mount: special device /dev/sde1/ does not exist log: media-lumix\x2dphotos.mount has failed dependency has failed for local file system log: defined-by: systemd Since /dev/sde1 is listed and described from the fdisk -l command how can it 'not' exits? I suspect that /dev/sde1 exists, but /dev/sde1/ (with the trailing slash) does not - i.e., /dev/sde1 is a device node, not a directory. Assuming that trailing slash really is there in the fstab, I would honestly not expect that fstab entry to work, just on that basis. It's possible that older mount methods figured it out and accepted things anyway (be permissive in what you accept and rigid in what you emit), but that systemd is being more rigid and is not trying to do any such gymnastics. Try dropping the trailing slash from the fstab and see whether that fixes anything. What is meant by media-lumix(back slash!)x2dphotos.mount(?) I imagine that \x2 or \x2d is an escape code for some special character, which is not being represented directly here for some reason. I don't recognize the syntax or the context offhand, however. Adding the SD card into the card reader after editing /etc/fstab then rebooting, causes the computer to go into emergency (? WTF) mode. Ctrl+d doesn't fix it. Going to the command prompt with the root password is the only solution. (i.e. editing the /etc/fstab file back like it was, removing the SD card, and rebooting.) I think it's ludicrous that adding an SD card that even has its own line in /etc/fstab, throws the whole system into 'emergency' mode. As I understand matters, systemd's logic is that it can't tell which fstab entries are required for a successful boot unless the ones which aren't are all labeled with noauto, so whenever a boot-time mount of a fstab entry fails systemd assumes that something might have gone wrong and drops into emergency mode so that you can fix the problem. I believe this is a side effect of systemd's dependency-based design. If the mount failing isn't that critical, then the right way to fix the problem under systemd's apparent design would probably be to add the noauto label to the fstab, so that the device will not mount automatically on boot. If there's a way to configure a mount to be attempted at boot time, but not fail the boot if the device is not present, I don't know what it is. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Camera SD card mounting problems (defined by systemd)
On 31/10/14 21:31, The Wanderer wrote: If the mount failing isn't that critical, then the right way to fix the problem under systemd's apparent design would probably be to add the noauto label to the fstab, so that the device will not mount automatically on boot. If there's a way to configure a mount to be attempted at boot time, but not fail the boot if the device is not present, I don't know what it is. Use the well-documented fstab(5) option nofail, which predates the creation of systemd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54540e2b.7020...@zen.co.uk
Re: Camera SD card mounting problems (defined by systemd)
On 10/31/2014 at 06:33 PM, Martin Read wrote: On 31/10/14 21:31, The Wanderer wrote: If the mount failing isn't that critical, then the right way to fix the problem under systemd's apparent design would probably be to add the noauto label to the fstab, so that the device will not mount automatically on boot. If there's a way to configure a mount to be attempted at boot time, but not fail the boot if the device is not present, I don't know what it is. Use the well-documented fstab(5) option nofail, which predates the creation of systemd. Thanks. I don't recall having been aware of that, but it would be exactly what I was looking for on that note. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: LVM mounting problems
On Mon, May 13, 2013 at 02:14:58PM -0700, Gary Roach wrote: Hi all, I needed to expand my Debian Wheezy system by adding a 1 TB drive and decided to switch over to LVM2 in the process. I rolled up my old 160 GB drive into the 1 TB drive and called the whole thing bigdisk and chopped the drive into 3 logical volumes. Everything seemed to work until I started to try mounting the logical volumes. On boot up with the fstab file shown below, the system gets a whole bunch of mod-probe errors and finally drops into the maintenance mode. If I go in and # out the 3 lines shown the boot goes as normal. My setup is: -- fdisk -l = .. clippage ... Thanks in advance Gary R. I don't know. Buti, I have a second hdd with fedora18, LVM, on it, and I'm finding it won't mount on boot in Wheezy (perhaps my /etc/fstab entry is wrong? /dev/fedora/home /media/fedora ext3 auto,noatime 0 2), but I find I can mount it manually, anyway, sudo mount /dev/fedora/home /media/fedora I swear it was auto-mounting with Squeeze. I use Debian like 99% of the time anyway, so once it's mounted, I'm good for a good while. I rsync my Debian /home to a dir in my Fedora /home, daily, with cron. If I really want to play with Fedora, I generally use VirtualBox. Had installed it on the other hdd, because I might be going to work for an RH/CentOS shop (and also have centos server on a VBox, now, so one must question the usefulness of the fedora installation on that other hdd, but it ain't hurting nothing, and I'd been meaning to install something on it, and it's convenient to no longer plugin my external hdd for backups, although I'll still do that about monthly, now). But I digress... ./tony -- http://www.tonybaldwin.me art, music, software by me, tony 3F330C6E signature.asc Description: Digital signature
LVM mounting problems
Hi all, I needed to expand my Debian Wheezy system by adding a 1 TB drive and decided to switch over to LVM2 in the process. I rolled up my old 160 GB drive into the 1 TB drive and called the whole thing bigdisk and chopped the drive into 3 logical volumes. Everything seemed to work until I started to try mounting the logical volumes. On boot up with the fstab file shown below, the system gets a whole bunch of mod-probe errors and finally drops into the maintenance mode. If I go in and # out the 3 lines shown the boot goes as normal. My setup is: -- fdisk -l = Disk /dev/sda: 60.0 GB, 60022480896 bytes 255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009aac6 Device Boot Start End Blocks Id System /dev/sda1 *2048 11319500756596480 83 Linux /dev/sda2 113197054 117229567 20162575 Extended /dev/sda5 113197056 117229567 2016256 82 Linux swap / Solaris Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000264c7 Device Boot Start End Blocks Id System /dev/sdc1 1 1953525167 976762583+ 8e Linux LVM Partition 1 does not start on physical sector boundary. Disk /dev/sdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sdb1 1 312581807 156290903+ 8e Linux LVM Disk /dev/mapper/bigdisk-backuppc: 499.3 GB, 499289948160 bytes 255 heads, 63 sectors/track, 60701 cylinders, total 975175680 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x Disk /dev/mapper/bigdisk-backuppc doesn't contain a valid partition table Disk /dev/mapper/bigdisk-general: 499.3 GB, 499289948160 bytes 255 heads, 63 sectors/track, 60701 cylinders, total 975175680 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x Disk /dev/mapper/bigdisk-general doesn't contain a valid partition table Disk /dev/mapper/bigdisk-extra: 161.7 GB, 161661059072 bytes 255 heads, 63 sectors/track, 19654 cylinders, total 315744256 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x Disk /dev/mapper/bigdisk-extra doesn't contain a valid partition table lvdisplay = --- Logical volume --- LV Path/dev/bigdisk/backuppc LV Namebackuppc VG Namebigdisk LV UUIDqzE56E-Jc8B-BEG9-Tmbe-HfKQ-OvfW-iVqfdw LV Write Accessread/write LV Creation host, time ctech, 2013-05-11 16:21:37 -0700 LV Status available # open 0 LV Size465.00 GiB Current LE 119040 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:0 --- Logical volume --- LV Path/dev/bigdisk/general LV Namegeneral VG Namebigdisk LV UUIDSdc7Oe-2pQk-3Lcr-gtCr-qKab-5iFw-SV0XQ3 LV Write Accessread/write LV Creation host, time ctech, 2013-05-11 16:22:09 -0700 LV Status available # open 0 LV Size465.00 GiB Current LE 119040 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:1 --- Logical volume --- LV Path/dev/bigdisk/extra LV Nameextra VG Namebigdisk LV UUID6iXc1l-DObr-3TyI-Mdc0-3Rk1-vO4Q-OaNMxs LV Write Accessread/write LV Creation host, time ctech, 2013-05-11 16:30:31 -0700 LV Status available # open 0 LV Size150.56 GiB Current LE 38543 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2
Re: External hard drive with mounting problems
2011/3/19 Jason Hsu jhsu802...@jasonhsu.com: I have a 250 GB Seagate Expansion Portable Hard Drive that sometimes won't mount. I end up having to use TestDisk to recover my files from it, and then I have to reformat the drive. The drive works for a while, and then it becomes unmountable sometime later. I've had this happen with the drive formatted as NTFS (original) and ext2. The messages I get in the dialog box when I use the GUI to mount are Unable to mount device and Erroriorg.freedesktop.Hal.Device.Volume.UnknownFailure/i. Did your USB cable moved even by mm? I have similar problems with my external hdd, it is always losing connection when cable is moved even by 1mm. What you have in your /dev/sd* after lost connection ? ( in my case sdbX is still mounted, but there is no such thing as sdb* in /dev/, instead I have sdc which I can mount in exact same place as sdb, but it just repeating of process ) The drive is listed in GParted as /dev/sdc, and the partition is /dev/sdc1. When I try to mount the drive in a shell, I get an error message telling me that it's not listed in /etc/fstab or /etc/mtab. This is the case whether I try to mount the drive as /dev/sdc, /dev/sdc1, /mnt/sdc, or /mnt/sdc1. Try mounting sdd1 ( if you don't have any other sdd in /dev/ ) or whatever it will be I did once try using the shred command to get rid of deleted files and to see if there were any problems. Shred had no difficulty writing to any part of the disk. What exactly is going on here? Does my drive have a hardware problem? What tools can I use to evaluate the condition of this drive? Just strange behavior of mount/kernel/usb external drives/whatever. I never got to WHAT exactly is happening there. darkestkhan -- jid: darkestk...@gmail.com May The Source be with You. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim4z2o5vnmddyt4tb2szibkh_n6lcgh+hk1k...@mail.gmail.com
Re: External hard drive with mounting problems
Jason Hsu wrote: I have a 250 GB Seagate Expansion Portable Hard Drive that sometimes won't mount. I end up having to use TestDisk to recover my files from it, and then I have to reformat the drive. The drive works for a while, and then it becomes unmountable sometime later. I've had this happen with the drive formatted as NTFS (original) and ext2. It could be a flaky power source, that can cause these problems too. Doesn't matter if the drive is bus powered or external; if the power supply is not good enough, then mounting can fail and the drive won't be detected consistently. So, first make sure that the drive is visible -- if it isn't visible, then it won't ever mount. -- Kind Regards AndrewM Andrew McGlashan Broadband Solutions now including VoIP -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86ac04.20...@affinityvision.com.au
External hard drive with mounting problems
I have a 250 GB Seagate Expansion Portable Hard Drive that sometimes won't mount. I end up having to use TestDisk to recover my files from it, and then I have to reformat the drive. The drive works for a while, and then it becomes unmountable sometime later. I've had this happen with the drive formatted as NTFS (original) and ext2. The messages I get in the dialog box when I use the GUI to mount are Unable to mount device and Erroriorg.freedesktop.Hal.Device.Volume.UnknownFailure/i. The drive is listed in GParted as /dev/sdc, and the partition is /dev/sdc1. When I try to mount the drive in a shell, I get an error message telling me that it's not listed in /etc/fstab or /etc/mtab. This is the case whether I try to mount the drive as /dev/sdc, /dev/sdc1, /mnt/sdc, or /mnt/sdc1. I did once try using the shred command to get rid of deleted files and to see if there were any problems. Shred had no difficulty writing to any part of the disk. What exactly is going on here? Does my drive have a hardware problem? What tools can I use to evaluate the condition of this drive? -- Jason Hsu jhsu802...@jasonhsu.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319130533.c36f405b.jhsu802...@jasonhsu.com
usb HD mounting problems
Hi List, still got problems mounting and accessing an external HD (MacPower Icecube FW800) through USB. Note that this is on a Powerpc, but it might not be a platform specific problem, hence the post. I am here on Debian Testing with an 2.6.11.5 kernel. I think i got all required modules loaded: vfat 13888 0 msdos 8928 0 usb_storage36512 0 ntfs 130256 0 fat43772 2 vfat,msdos sd_mod 16400 0 ohci1394 38404 0 evdev 9984 0 ohci_hcd 24648 0 uhci_hcd 42128 0 ehci_hcd 34952 0 sbp2 26064 0 scsi_mod 101308 3 usb_storage,sd_mod,sbp2 ieee1394 115688 2 ohci1394,sbp2 udf94020 0 binfmt_misc11656 0 usbhid 41536 0 usbcore 131024 6 usb_storage,ohci_hcd,uhci_hcd,ehci_hcd,usbhid At power on, the HD gets listed in /proc/partitions: 8 0 195360984 sda 8 1 32764536 sda1- FAT32 8 2 32764567 sda2- FAT32 8 3 32764567 sda3- FAT32 8 4 97064730 sda4- ntfs The partitions were made on a win2k box. /var/log/messages shows the device: Jun 12 17:59:12 gonzo kernel: usb 2-1: new full speed USB device using ohci_hcd and address 38 Jun 12 17:59:12 gonzo kernel: scsi10 : SCSI emulation for USB Mass Storage devices Jun 12 17:59:13 gonzo usb.agent[19676]: usb-storage: already loaded Jun 12 17:59:17 gonzo kernel: Vendor: SAMSUNG Model: SP2014N Rev: VC10 Jun 12 17:59:17 gonzo kernel: Type: Direct-Access ANSI SCSI revision: 04 Jun 12 17:59:17 gonzo kernel: SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) Jun 12 17:59:17 gonzo kernel: SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) Jun 12 17:59:18 gonzo kernel: /dev/scsi/host10/bus0/target0/lun0: p1 p2 p3 p4 Jun 12 17:59:18 gonzo kernel: Attached scsi disk sda at scsi10, channel 0, id 0, lun 0 Jun 12 17:59:18 gonzo scsi.agent[19712]: sd_mod: loaded sucessfully (for disk) As i try to mount the first partition: gonzo:~# mount -v -t msdos /dev/sda1 /fw/ mount: /dev/sda1 is not a valid block device And /var/log/messages gives: Jun 12 18:00:24 gonzo kernel: usb 2-1: reset full speed USB device using ohci_hcd and address 38 Jun 12 18:00:25 gonzo kernel: usb 2-1: scsi_eh_10 timed out on ep0in Jun 12 18:00:30 gonzo kernel: usb 2-1: scsi_eh_10 timed out on ep0in Jun 12 18:00:30 gonzo kernel: usb 2-1: reset full speed USB device using ohci_hcd and address 38 Jun 12 18:00:31 gonzo kernel: usb 2-1: scsi_eh_10 timed out on ep0in Jun 12 18:00:36 gonzo kernel: usb 2-1: scsi_eh_10 timed out on ep0in Jun 12 18:00:37 gonzo kernel: scsi: Device offlined - not ready after error recovery: host 10 channel 0 id 0 lun 0 Jun 12 18:00:37 gonzo kernel: usb 2-1: USB disconnect, address 38 The same is with the other partitions (fat and ntfs(readonly))... I am stuck here... A little surfing got me the info to disable CONFIG_EFI_PARTION in the kernel conf, but it was always off... Any ideas what to try next would be very appreciated! regards, Peter P. (Please CC me as i read this list in digest-mode) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sound and Audio CD mounting problems
Does anyone know why I cannot get Debian to mount an audio cd? It will mount cd's normally and it will play mp3's from a cd. When I try to mount an audio disk though with:- mount /dev/hdc /mnt/cdrom it first requests a file type - so I amend the command to:- mount -t iso9660 /dev/hdc /mnt/cdrom Whereupon it says that it is unable to mount this ... ! Any clues? Also can anyone advise on why the volume is VERY low - I tried turning up xmms's volume but its still very quiet. Is this a card issue? Thank :) _ Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and Audio CD mounting problems
Hello max von seibold ([EMAIL PROTECTED]) wrote: Does anyone know why I cannot get Debian to mount an audio cd? It will mount cd's normally and it will play mp3's from a cd. When I try to mount an audio disk though with:- mount /dev/hdc /mnt/cdrom it first requests a file type - so I amend the command to:- mount -t iso9660 /dev/hdc /mnt/cdrom Whereupon it says that it is unable to mount this ... ! Any clues? *sigh* (you really could have taken a look at the list archive) Audio CDs are not mounted because they don't have a file system. Especially they don't have an iso9660 file system. Use the player or ripping tool to play or read them. Note: If you use konqueror, you can configure the audiocd plugin to be able to access CD tracks from within the file manager. However you probably have to switch on ide-scsi emulation for IDE drives and change permissions on /dev/sg* first (changing ownership to root.cdrom and make them group-rw should work). And if you really, really want to mount audio CDs, you can install the cdfs driver (I think it is already included in Debian). It was designed to make sessions or audio tracks on CDs visible as if they were files. Also can anyone advise on why the volume is VERY low - I tried turning up xmms's volume but its still very quiet. Is this a card issue? Try some mixer program (kmix, aumix,...) to see what the channels are set to. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DevFS mounting problems (was: Re: Think I need ttyN where N8)
On Tuesday 28 October 2003 17:30, Kjetil Kjernsmo wrote: Yes, it's there! :-) [EMAIL PROTECTED]:~ grep devfs /proc/mounts none /dev devfs rw 0 0 If devfs is in /proc/filesystems, Yes, it is there too. Just to let you all know I have solved this problem... Usually, I'm thinking don't go further unless you're sure the stuff you're doing right now works when I'm following HOWTOs. In this case, it was obviously not a good approach: This part worked once I added dumbcon=2 to my kernel parameters. It did in fact create the devices, allthough mount is unaware of it... Now, I can start two different X servers at the same time and have them respond to two different keyboards and mice. Still to do is to get kdm to do that for me... That doesn't work yet. Thanks to all who responded! Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DevFS mounting problems (was: Re: Think I need ttyN where N8)
Hi and thanks for the response! On Tuesday 28 October 2003 04:23, Jerome R. Acks wrote: Since you have devfs mounted on /dev, you ought to be able to use devices in /dev/tts directly rather than compatibility symlinks to ttyX. Yes. I thought so too. Anyway, you're giving me another idea, that it may really be devfs itself I have problems with. If the devices are not being created, you probably need to load a kernel module for the hardware or specify module options. Check /var/log/messages, /var/log/kern.log, and /var/log/syslog to see what is reported about the second graphic card during boot or when the kernel module is loaded. The second card is a Matrox MGA 1064SG [Mystique] (and the primary is a G450), so the driver is for both cards is mga, and that's compiled into the kernel. I've got Xinerama running on the second card right now. So I don't see quite how I could lack anything for the hardware... (But obviously, I'm open to anything!) Upon rereading the docs (another time), I found that there are known conflicts between devfs and devpty, so I've now disabled the latter in the kernel. Reading http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/dev_files.html (which is basically the howto I'm following) I get the impression that mount should know about it if devfs is used. It says that mount | grep devfs should report something, but for me it doesn't. Which is weird. It does seem like devfs is not mounted. This is what can be found about devfs in my kern.log: Oct 28 10:17:13 owl kernel: Kernel command line: BOOT_IMAGE=Linux ro root=301 devfs=mount Oct 28 10:17:14 owl kernel: devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) Oct 28 10:17:14 owl kernel: devfs: boot_options: 0x1 Oct 28 10:17:14 owl kernel: usb.c: registered new driver usbdevfs Oct 28 10:17:14 owl kernel: Mounted devfs on /dev ...so it says very clearly here, devfs is mounted, but apparently mount doesn't agree... I don't know if this means anything, but clearly, it must be a Bad Sign[tm]? The Good Thing[tm] about Bad Signs[tm] is that they often lead the way forward... :-) Do you think there is something here...? I haven't put anything about devfs in my /etc/fstab, should I? Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DevFS mounting problems (was: Re: Think I need ttyN where N8)
On Tue, Oct 28, 2003 at 11:21:50AM +0100, Kjetil Kjernsmo wrote: Reading http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/dev_files.html (which is basically the howto I'm following) I get the impression that mount should know about it if devfs is used. It says that mount | grep devfs should report something, but for me it doesn't. Which is weird. It does seem like devfs is not mounted. Maybe it's mounted on boot, and init somehow unmounts it? The definite answer to see what is mounted is to cat /proc/mounts. No devfs there? If devfs is in /proc/filesystems, you can perhaps add an entry in /etc/fstab. (See your /proc entry for an example). If that still doesn't help, you can try more advanced things, such as booting with the additional parameter init=/bin/sh. That will skip all of the normal initialization, and just give you a prompt after the kernel is ready. Your rootfilesystem will be read-only, and you'll have to mount /proc to see what's mounted. mount -n /proc should do that trick. If devfs is mounted at that point, the next step is to find out why or how it's unmounted. I haven't put anything about devfs in my /etc/fstab, should I? You could try it. Won't hurt much since it's not working now. :) Good luck! Chris Niekel -- I've been down so long, if I'd cheer up, I'd still be depressed. - Lisa Simpson, Moanin' Lisa Blues. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DevFS mounting problems (was: Re: Think I need ttyN where N8)
On Tuesday 28 October 2003 17:22, Chris Niekel wrote: On Tue, Oct 28, 2003 at 11:21:50AM +0100, Kjetil Kjernsmo wrote: Reading http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/dev_files.html (which is basically the howto I'm following) I get the impression that mount should know about it if devfs is used. It says that mount | grep devfs should report something, but for me it doesn't. Which is weird. It does seem like devfs is not mounted. Maybe it's mounted on boot, and init somehow unmounts it? The definite answer to see what is mounted is to cat /proc/mounts. No devfs there? Yes, it's there! :-) [EMAIL PROTECTED]:~ grep devfs /proc/mounts none /dev devfs rw 0 0 If devfs is in /proc/filesystems, Yes, it is there too. you can perhaps add an entry in /etc/fstab. (See your /proc entry for an example). If that still doesn't help, you can try more advanced things, such as booting with the additional parameter init=/bin/sh. That will skip all of the normal initialization, and just give you a prompt after the kernel is ready. Your rootfilesystem will be read-only, and you'll have to mount /proc to see what's mounted. mount -n /proc should do that trick. If devfs is mounted at that point, the next step is to find out why or how it's unmounted. OK. By going through /etc/rc2.d/ and run the scripts manually? I haven't put anything about devfs in my /etc/fstab, should I? You could try it. Won't hurt much since it's not working now. :) Hehe, ok! :-) But apparently, it _is_ mounted, now... At least some parts of the system thinks it is... BTW, I posted a message to the devfs mailing list too, but I don't know if it is alive, their archives are 404. Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
nfs mounting problems
I posted this on comp.linux.os.networking and didn't get any responses. I'm hoping somebody here might be able to help. I want to backup my laptop (thinkpad-wireless) to the tape drive in my server (bear). On my laptop, in /etc/exports: [EMAIL PROTECTED] /root]# cat /etc/exports / bear(ro,no_root_squash) /home bear(ro,no_root_squash) /home/E bear(ro,no_root_squash) /varbear(ro,no_root_squash) /home is the problem. It is the mount point for /dev/hda8: [EMAIL PROTECTED] /root]# mount /dev/hda3 on / type ext2 (rw) none on /proc type proc (rw) /dev/hda8 on /home type ext2 (rw) /dev/hda7 on /usr type ext2 (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hda9 on /usr/local type ext2 (rw) /dev/hda11 on /var type ext2 (rw) /dev/hda10 on /home/E type vfat (rw) [EMAIL PROTECTED] /root]# nfs is running and I've exportfs'd. Moving on to the server: bear:/home/rskoss# mount -t nfs thinkpad-wireless:/home /mnt/thinkpad/home mount: thinkpad-wireless:/home failed, reason given by server: Permission denied bear:/home/rskoss# Other exported file systems mount (eventually): bear:/home/rskoss# mount -t nfs thinkpad-wireless:/ /mnt/thinkpad/slash bear:/home/rskoss# ls /mnt/thinkpad/slash bin dev home lost+found opt root tmpusr win boot etc lib mnt proc sbin ttys0 var So, there are two problems. 1. Why can't I mount thinkpad-wireless:/home on bear, and 2. Why does it take so long to mount? FWIW, these two computers are on the same desk connected through a hub. Bear is running Debian Woody with kernel 2.4.7. Thinkpad is running RedHat 6.2 kernel 2.2.14-5.0. -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: nfs mounting problems
On Mon, 2001-09-24 at 06:25, Bob Koss wrote: I posted this on comp.linux.os.networking and didn't get any responses. I'm hoping somebody here might be able to help. I want to backup my laptop (thinkpad-wireless) to the tape drive in my server (bear). Not sure why your nfs isn't working but I'd suggest trying dump and rdump over ssh for network backups. I've been using it quite succesfully on several networks I run. --mike
RE: nfs mounting problems
I posted this on comp.linux.os.networking and didn't get any responses. I'm hoping somebody here might be able to help. I want to backup my laptop (thinkpad-wireless) to the tape drive in my server (bear). Not sure why your nfs isn't working but I'd suggest trying dump and rdump over ssh for network backups. I've been using it quite succesfully on several networks I run. I would love to use dump. But my understanding is that dump doesn't work on vfat file systems and I would like to backup my dos E drive, which is smbfs mounted to also be backed up to my server. Robert S. Koss, Ph.D. | Training and Mentoring Senior Consultant | Object Oriented Design Object Mentor, Inc. | C++, Java www.objectmentor.com| Extreme Programming
Mounting problems
This is confusing the hell out of me: I want to allow a user, AND ONLY THAT USER, to mount CD's and floppys. We'll call him 'bob'. I added 'bob' to the groups floppy and cdrom. adduser bob floppy adduser bob cdrom my mount points are: /dev/fd0/mnt/fd0 vfat defaults,user,noauto 0 0 /dev/fd1/mnt/fd1 vfat defaults,user,noauto 0 0 /dev/cdrom /mnt/cdromiso9660 defaults,user,noauto 0 0 /dev/cdrw /mnt/cdrw iso9660 defaults,user,noauto 0 0 /dev/mcd/mnt/mcd iso9660 defaults,user,noauto 0 0 /dev/zip/mnt/zip vfat defaults,user,noauto 0 0 and an ls -l of my /mnt directory shows: dr-xr-x--- 2 root cdrom1024 May 18 21:51 cdrom/ dr-xr-x--- 2 root cdrom1024 May 18 21:51 cdrw/ dr-xr-x--- 2 root floppy 1024 May 18 21:51 fd0/ dr-xr-x--- 2 root floppy 1024 May 18 21:51 fd1/ dr-xr-x--- 2 root cdrom1024 Aug 16 21:07 mcd/ dr-xr-x--- 2 root floppy 1024 May 18 21:51 zip/ Now, if 'bob' mounts the cdrom, /mnt/cdrom becomes: dr-xr-xr-w 2 root root 1024 May 18 21:51 cdrom/ And now ANY user can see the contents of the CD!!! Why did the group and permissions change? How do I prevent other users from changing into that directory (/mnt/cdrom)? Thanks, Bryan
Re: Mounting problems
On Sun, 17 Oct 1999, Bryan Scaringe wrote: : This is confusing the hell out of me: : : I want to allow a user, AND ONLY THAT USER, to mount CD's and floppys. : We'll call him 'bob'. I added 'bob' to the groups floppy and cdrom. : adduser bob floppy : adduser bob cdrom : : my mount points are: : /dev/fd0/mnt/fd0 vfat defaults,user,noauto 0 0 : /dev/fd1/mnt/fd1 vfat defaults,user,noauto 0 0 : /dev/cdrom /mnt/cdromiso9660 defaults,user,noauto 0 0 : /dev/cdrw /mnt/cdrw iso9660 defaults,user,noauto 0 0 : /dev/mcd/mnt/mcd iso9660 defaults,user,noauto 0 0 : /dev/zip/mnt/zip vfat defaults,user,noauto 0 0 This allows any user to mount the media. You might want add bob to /etc/sudoers so he can use `sudo mount' to mount the media instead. : and an ls -l of my /mnt directory shows: : dr-xr-x--- 2 root cdrom1024 May 18 21:51 cdrom/ : dr-xr-x--- 2 root cdrom1024 May 18 21:51 cdrw/ : dr-xr-x--- 2 root floppy 1024 May 18 21:51 fd0/ : dr-xr-x--- 2 root floppy 1024 May 18 21:51 fd1/ : dr-xr-x--- 2 root cdrom1024 Aug 16 21:07 mcd/ : dr-xr-x--- 2 root floppy 1024 May 18 21:51 zip/ : : Now, if 'bob' mounts the cdrom, /mnt/cdrom becomes: : dr-xr-xr-w 2 root root 1024 May 18 21:51 cdrom/ : : And now ANY user can see the contents of the CD!!! : : Why did the group and permissions change? The permissions of the mount point do not determine the permissions of the mounted media - in fact, the permissions of the mounted media root will supercede the permissions of the mount point. : How do I prevent other users from changing into that directory (/mnt/cdrom)? RTFM `man mount', pay close attention to the uid, gid, and umask options. Example: I mount a VFAT partition readable by only one user on my home machine: /dev/sdc3 /win vfat uid=1000,gid=1000,umask=027 This mount is automounted ... in your case you'd want something like this: /dev/cdrom /mnt/cdrom iso9660 noauto,uid=1000,gid=1000,umask=027 HTH, -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
mounting problems
Hi all, Been recompiling my 2.2.10 kernel to be able to use hp 8100+ CDRW. I think I got it all right but some strange things did happen. I can't mount my ordinary cd anymore! mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems Where do I start looking? Here is some information. in fstab: /dev/hdc/cdrom iso9660 ro,user,noauto 0 0 cdrecord -scanbus Cdrecord release 1.8a23 Copyright (C) 1995-1999 Jörg Schilling scsibus0: cdrecord: Warning: controller returns wrong size for CD capabilities page. 0) 'SONY' 'CD-ROM CDU4011 ' 'UY04' Removable CD-ROM 1) 'HP ' 'CD-Writer+ 8100 ' '1.0g' Removable CD-ROM 2) * 3) * 4) * 5) * 6) * 7) * Can anyone help me ? Best regards Joakim Svensson
Re: mounting problems
On Thu, Aug 26, 1999 at 04:43:31PM +0200, Jocke wrote: Hi all, Been recompiling my 2.2.10 kernel to be able to use hp 8100+ CDRW. I think I got it all right but some strange things did happen. I can't mount my ordinary cd anymore! mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems Where do I start looking? Here is some information. in fstab: /dev/hdc/cdrom iso9660 ro,user,noauto 0 0 cdrecord -scanbus Cdrecord release 1.8a23 Copyright (C) 1995-1999 Jörg Schilling scsibus0: cdrecord: Warning: controller returns wrong size for CD capabilities page. 0) 'SONY' 'CD-ROM CDU4011 ' 'UY04' Removable CD-ROM 1) 'HP ' 'CD-Writer+ 8100 ' '1.0g' Removable CD-ROM 2) * 3) * 4) * 5) * 6) * 7) * Can anyone help me ? You compiled in SCSI emulation for IDE devices, right? That means that, to user-level programs, your CDROMs are /dev/scd0 and /dev/scd1. You'll have to 'modprobe ide-scsi' before using the CD-ROM devices, or add its name to /etc/modules so that it is autoloaded on startup. -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: mounting problems
Hi, On Thu, 26 Aug, 1999 à 04:43:31PM +0200, Jocke wrote: Hi all, Been recompiling my 2.2.10 kernel to be able to use hp 8100+ CDRW. I think I got it all right but some strange things did happen. I can't mount my ordinary cd anymore! mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems Are you sure you've included iso9660 fs during your kernel compile ? -- ( - Laurent PICOULEAU - ) /~\ [EMAIL PROTECTED] /~\ | \)Linux : mettez un pingouin dans votre ordinateur !(/ | \_|_Seuls ceux qui ne l'utilisent pas en disent du mal. _|_/
Floppy Mounting Problems
I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it says mount: /dev/fd0 already mounted or /floppy busy. I can mount a floppy to other directories, so it must be /floppy that's busy, even though /etc/mtab and /proc/mounts both show it as not mounted. Further, i can't remove the floppy module from the kernel. Eventually i run out of directories to mount to and have to reboot. This is unacceptable. Any ideas? -- Eric Gillespie, Jr. * [EMAIL PROTECTED] Don't you try to out-weird me! I get stranger things than you free with my breakfast cereal! --Zaphod Beeblebrox
Re: Floppy Mounting Problems
On Mon, 31 May 1999, Eric Gillespie, Jr. wrote: I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it says mount: /dev/fd0 already mounted or /floppy busy. I can mount a floppy to other directories, so it must be /floppy that's busy, even though /etc/mtab and /proc/mounts both show it as not mounted. Further, i can't remove the floppy module from the kernel. Eventually i run out of directories to mount to and have to reboot. This is unacceptable. Any ideas? Did you try umounting /floppy? i had this problem when i was playing around with smbmount (stupid !@)#' $(%^* characters in the sharenames) (literally those characters, especially , ', and space) and it would fail and leave the directory wedged... IIRC umount fixed it.
Re: Floppy Mounting Problems
Hi! Eric Gillespie, Jr. [EMAIL PROTECTED] wrote: I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it says mount: /dev/fd0 already mounted or /floppy busy. It isn't the best solution, but, did you already try umount /mnt/floppy/? Hope this helps. -- Daniel González Gasull (`-/)_.-'``-._ The hottest places in [EMAIL PROTECTED] . . `; -._)-;-,_`) Hell are reserved for PGP RSA key 1024/EEA93A69(v_,)' _ )`-.\ ``-' those who, in times of _.- _..-_/ / ((.'fL moral crisis, preserved ((,.-' ((,/ their neutrality. -- Dante __ | Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/ | ~~
Re: Floppy Mounting Problems
Hi! Brad [EMAIL PROTECTED] wrote: On Mon, 31 May 1999, Eric Gillespie, Jr. wrote: I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it says mount: /dev/fd0 already mounted or /floppy busy. I can mount a floppy to other directories, so it must be /floppy that's busy, even though /etc/mtab and /proc/mounts both show it as not mounted. Further, i can't remove the floppy module from the kernel. Eventually i run out of directories to mount to and have to reboot. This is unacceptable. Any ideas? Did you try umounting /floppy? i had this problem when i was playing around with smbmount (stupid !@)#' $(%^* characters in the sharenames) (literally those characters, especially , ', and space) and it would fail and leave the directory wedged... IIRC umount fixed it. Maybe help: Look at the Codepages your kernel is supporting. You may need some of them for name of the files in the disk. Windows 95 uses some of this Codepages. Look at cd /usr/src/linux make menuconfig In Filesystems I have Codepages 437 and 850 as modules. I don't know if you, or even me, will need the other codepages. Hope this helps. -- Daniel González Gasull (`-/)_.-'``-._ The hottest places in [EMAIL PROTECTED] . . `; -._)-;-,_`) Hell are reserved for PGP RSA key 1024/EEA93A69(v_,)' _ )`-.\ ``-' those who, in times of _.- _..-_/ / ((.'fL moral crisis, preserved ((,.-' ((,/ their neutrality. -- Dante __ | Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/ | ~~
Re: Floppy Mounting Problems
On Tue, 1 Jun 1999, Brad wrote: On Mon, 31 May 1999, Eric Gillespie, Jr. wrote: I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it says mount: /dev/fd0 already mounted or /floppy busy. I can mount a floppy to other directories, so it must be /floppy that's busy, even though /etc/mtab and /proc/mounts both show it as not mounted. Further, i can't remove the floppy module from the kernel. Eventually i run out of directories to mount to and have to reboot. This is unacceptable. Any ideas? Did you try umounting /floppy? I had a similar proble. But with a corrupted floppies. Trying to access a file that happens to be too long produces and error (something like: VFS: trying to access outside the filesystem), and after that there is no way to unmount the floppy. Had to reboot. Does anyone know a way to force unmounting in such a case ? Sergey.
Re: Floppy Mounting Problems
* Eric Gillespie, [EMAIL PROTECTED] writes: I have a stack of floppies that i'm sorting through, and i need to know what's on them. Some of them, however, aren't formatted. I have know way to know which ones aren't until i mount them. Every time i try to mount an unformatted floppy, mount segfaults. Afterwards, if i try to mount another floppy it Have you tried the mtools? These allow you to access the drive with the DOS commands (with a prefix-m). Thjey don´t use mount internally, so just try mdir. HTH, Colin -- Colin Marquardt [EMAIL PROTECTED]
Re: Floppy Mounting Problems
On Tue, 1 Jun 1999, [iso-8859-1] Daniel Gonz?lez Gasull wrote: Brad [EMAIL PROTECTED] wrote: Did you try umounting /floppy? i had this problem when i was playing around with smbmount (stupid !@)#' $(%^* characters in the sharenames) (literally those characters, especially , ', and space) and it would fail and leave the directory wedged... IIRC umount fixed it. Maybe help: Look at the Codepages your kernel is supporting. You may need some of them for name of the files in the disk. Windows 95 uses some of this Codepages. Look at The problem is that characters like and ' have special meaning to the shell, and no matter how they're quoted smbmount has a tendancy to pass them unquoted when trying to mount.
Re: Floppy Mounting Problems
On Tue, Jun 01, 1999 at 02:45:21AM -0500, Brad [EMAIL PROTECTED] wrote: Did you try umounting /floppy? i had this problem when i was playing around with smbmount (stupid !@)#' $(%^* characters in the sharenames) (literally those characters, especially , ', and space) and it would fail and leave the directory wedged... IIRC umount fixed it. Nope, it says /floppy is not mounted according to mtab, which is correct, /floppy is not mounted. Someone else suggested checking the codepage modules, but this is not the problem. I have no problems mounting/umounting floppies until I (try to) mount a non-formatted one. Just in case, however, I loaded the modules manually anyway. No luck. Like I said, I can still mount the floppy to other directories, but that doesn't solve the problem. The floppy module never gets unloaded and /floppy can't be mounted to. This is unacceptable. I would think this is a bug in the kernel (the mount() call) or in the mount program, since mount segfaults before its done. I'm guessing it isn't unlocking the directory or something. -- Eric Gillespie, Jr. * [EMAIL PROTECTED] Don't you try to out-weird me! I get stranger things than you free with my breakfast cereal! --Zaphod Beeblebrox
Re: Network mounting problems
Hello All:
I have been running into a vexing problem with a cluster of 8 Debian
machines I am using for a Course in Computational Physics.
All of the machines are running Debian 1.2 as installed in December 1996.
I have not wanted to do much upgrading during the course of the semester.
so students can log into any one of the machines and find their data
files.
The problem is that if the systems are left to run for an extended period
of time (over a week usually but as little as a few days even!) the /home
directory becomes inaccessible at login even though the df command shows
it to be mounted. This causes a great deal of problems and means that I
have to reboot the machines regularly. It also means that if I am not
around people start to complain. As a side note, the server is usually
quite stable and stays up for many weeks at a time. Just the other
machines need to be rebooted because of this problem. The kernel version
is 2.0.27.
So, I assume the clients mount their /home from a (the?) server via NFS?
If so, I used to have a lot of problems with the old nfsd, that used
to die on my every so often (escpecially if two clients mount and read
from the nfs disks at the same time). This was solved by upgrading to
a more recent nfsd. But alas, you don't indicate that any nfsd dies,
so you may be running into another problem. Still, upgrading the
server's nfsd (from the netstd package) may improve matters.
Currently installed on my system (without problems):
$ /usr/sbin/rpc.nfsd -v
Universal NFS Server 2.2beta25
$ dpkg -l netstd
ii netstd 2.13-1 Networking binaries and daemons for Linux
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Network mounting problems
Hello All: I have been running into a vexing problem with a cluster of 8 Debian machines I am using for a Course in Computational Physics. All of the machines are running Debian 1.2 as installed in December 1996. I have not wanted to do much upgrading during the course of the semester. so students can log into any one of the machines and find their data files. The problem is that if the systems are left to run for an extended period of time (over a week usually but as little as a few days even!) the /home directory becomes inaccessible at login even though the df command shows it to be mounted. This causes a great deal of problems and means that I have to reboot the machines regularly. It also means that if I am not around people start to complain. As a side note, the server is usually quite stable and stays up for many weeks at a time. Just the other machines need to be rebooted because of this problem. The kernel version is 2.0.27. Any help would be appreciated! Carlo *** *Carlo U. Segre * * Department of Biological, Chemical and Physical Sciences * *Illinois Institute of Technology, Chicago, IL 60616 * * Voice: (312) 567-3498 FAX: (312) 567-3494* *[EMAIL PROTECTED]* *** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom mounting problems
On Wed, 23 Apr 1997, Igor Grobman wrote: I am trying to help my friend install debian. He is getting the following error when dselect tries to mount his cdrom: mount: /dev/hdd has wrong major or minor number unable to mount /dev/hdd on /var/lib/dpkg/methods/mnt type iso9660 Anyone know what major/minor number mean? This numbers are used to identify a device in the system. Every device has its own major and minor numbers. Check if your /dev/hdd has the following major and minor numbers (ls -l): brw-rw 1 root disk 22, 64 May 8 1995 /dev/hdd ^^ ^^ major minor If not, you can use the MAKEDEV command do correct this (see the man page). Thanks. -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] Felix Almeida [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
cdrom mounting problems
I am trying to help my friend install debian. He is getting the following error when dselect tries to mount his cdrom: mount: /dev/hdd has wrong major or minor number unable to mount /dev/hdd on /var/lib/dpkg/methods/mnt type iso9660 Anyone know what major/minor number mean? By the way, his cdrom is recognized by the kernel on boot. Thanks. -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Mouse and mounting problems
Daniel Karlsson wrote: Hello! Now I've almost got the mouse to work in X. It's only the middle button that doesn't want to work. How do I make it work? I've also tried to mount my floppy drive. I wrote the following at the command line: mount -t msdos /dev/fd0 /floppy and I got the message: mount: /dev/fd0 is not a valid block device How do I cure this one? Hi, to access a MSDOS floppy, I prefer the mtools. This allows you to use nearly the same commands (mdir, mcopy, mcd, ...) like under DOS and without mounting the floppy. Check for the mtools package ... CU. -- Karlheinz Nolte, VS/ETB5, ALCATEL SEL AG D-70430 Stuttgart, Germany Tel.: +49-711-821-41834 mailto:[EMAIL PROTECTED]
Re: Mouse and mounting problems
On Sun, 9 Mar 1997 23:14:03 +0100, you wrote: Hello! Now I've almost got the mouse to work in X. It's only the middle button that doesn't want to work. How do I make it work? There's a nice mini howto on this topic; maybe it is even included in the standard /usr/doc/..., can't check it now. It may not be easy with cheap microsoft compatible mouses. I've still not found a good solution yet (I'm pluggig out and in the mouse on startup with mouse button pressed to switch it to mouseman mode), so I guess I'll buy a Logitech mouse soon... I've also tried to mount my floppy drive. I wrote the following at the command line: mount -t msdos /dev/fd0 /floppy and I got the message: mount: /dev/fd0 is not a valid block device How do I cure this one? This *should* work. Maybe the disk was not ok, or you have two drives? -- Falk Hueffner [EMAIL PROTECTED]
Re: Mouse and mounting problems
in your XF86Config, there will be a mouse section, in mine, I have a microsoft mouse on /dev/ttyS0 I need the line from my XF86Config ... # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Emulate3Buttons Emulate3Timeout50 # ChordMiddle is an option for some 3-button Logitech mice #ChordMiddle ... the Emulate3Buttons is what does it for me, as you can see just below that you may need to use ChordMiddle, for your three(??) button mouse. Hope this points you a little closer.. Richard Morin [EMAIL PROTECTED] On Sun, 9 Mar 1997, Alexander Koch wrote: Quoting Daniel Karlsson ([EMAIL PROTECTED]): Now I've almost got the mouse to work in X. It's only the middle button that doesn't want to work. How do I make it work? Somewhere when configuring X you have to choose a protocol for your mouse that is somewhat like those for gpm (try gpm -t help). If you cannot use the middlebutton you may have selected the usual m$ mouse instead of mman (Mouseman) or MouseSystems. Just play around with the mouse selections in xf86config (I do not yet know where this is to be done in debian). Alexander
Re: Mouse and mounting problems
Falk == Falk Hueffner [EMAIL PROTECTED] writes: Falk It may not be easy with cheap microsoft compatible Falk mouses. I've still not found a good solution yet (I'm Falk pluggig out and in the mouse on startup with mouse button Falk pressed to switch it to mouseman mode), so I guess I'll buy Falk a Logitech mouse soon... I had a Logitech, and didn't like it because the middle button was wired for MS Windows. It does a 'double-click', rather than being its own button. So when you try and drag something with it, like a menu or a file from TkDesk, the button's signal stutters up and down, and the menu flashes on an off. It was almost useless; I hade to hack a Tk togglebutton that would swap my mouse buttons around. The best mice for X are the 'mousesystems' kind, with the switch on the bottom for 'pc-3key' or 'ms-2key'. Precision Instruments (Taiwan) makes a pretty good one; that's the kind I have now. Karl M. Hegbloom [EMAIL PROTECTED] http://www.inetarena.com/~karlheg Portland, OR USA Debian GNU 1.2 Linux 2.0.29t
Mouse and mounting problems
Hello! Now I've almost got the mouse to work in X. It's only the middle button that doesn't want to work. How do I make it work? I've also tried to mount my floppy drive. I wrote the following at the command line: mount -t msdos /dev/fd0 /floppy and I got the message: mount: /dev/fd0 is not a valid block device How do I cure this one? _ __ __ | _ \ | |/ / | E-post: [EMAIL PROTECTED] | | | | | | ' / | WWW : http://www-und.ida.liu.se/~c95danka/ | | | | | | | Tel : 013 - 17 82 76 | | |_| | | . \ | Adress: Rydsvägen 246 C:21 584 34 LINKÖPING | |/ aniel |_|\_\ arlsson |__|
