From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HoyHF-00051D-Rj for garchives@archives.gentoo.org; Fri, 18 May 2007 08:57:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4I8uGPu022262; Fri, 18 May 2007 08:56:16 GMT Received: from dcnode-02.unlimitedmail.net (139.Red-80-26-111.staticIP.rima-tde.net [80.26.111.139]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4I8puqq017382 for ; Fri, 18 May 2007 08:51:57 GMT Received: from ppp.zz ([137.204.208.98]) (authenticated bits=0) by dcnode-02.unlimitedmail.net (8.14.0/8.14.0) with ESMTP id l4I8prRS027371 for ; Fri, 18 May 2007 10:51:54 +0200 From: Etaoin Shrdlu To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Corrupt USB pen drive Date: Fri, 18 May 2007 11:24:25 +0200 User-Agent: KMail/1.9.5 References: <200705171236.28695.michaelkintzios@gmail.com> <200705180027.03766.shrdlu@unlimitedmail.org> <200705180929.19407.michaelkintzios@gmail.com> In-Reply-To: <200705180929.19407.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705181124.26063.shrdlu@unlimitedmail.org> X-UnlimitedMail-MailScanner-From: shrdlu@unlimitedmail.org X-Spam-Status: No X-Archives-Salt: e32ecdc3-c484-474b-80ba-ce3ec07c232b X-Archives-Hash: 100b3922107d003427714e828dc538e4 On Friday 18 May 2007 10:29, Mick wrote: > On Thursday 17 May 2007 23:27, Etaoin Shrdlu wrote: > > IIRC, that is not the right syntax for mounting a loopback > > filesystem. If /tmp/r1 is the file containing the filesystem, try > > > > mount -o loop /tmp/r1 /mnt/somewhere > > > > and make sure you have support for loopback devices in your kernel. > > Thanks for all the suggestions. I tried the correct mount loopback > command on /dev/loop2 and I'm getting this error that mentions > /dev/loop0 (how does this work?): > ====================================== > # mount -t vfat -o loop /dev/loop2 /tmp/r1 > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > ====================================== You still seem to be missing the correct syntax. (note: this might not solve your problem, and even issuing the right command might be of no help, but since you asked for it, here it is). With every mount command, you have to specify at least two things: *what* to mount, and *where* to mount it, in this order. *Where* is usually a path to some (preferably empty) directory. *what* can be various things, depending on what you're trying to mount. For regular disk partitions, it's usually a device file (eg, /dev/sda1). For NFS, it's a string of the form remote_host:/remote/path. For loopback filesystems (ie, filesystems contained in a single file), it's the name of the container file, like your /tmp/r1. When mounting loopback filesystems, the "-o loop" option must be given. The "-o loop" option accepts some optional parameters. One of these is the specification of the loopback device that should be used. To explicitly specify a loopback device, use "-o loop=/dev/loopX". If no loopback device is specificed, then mount will automatically pick an unused loopback device (probably /dev/loop0). Your command # mount -t vfat -o loop /dev/loop2 /tmp/r1 uses an incorrect syntax for the specification of the loopback device (which is optional anyway), and does not tell where to mount the filesystem. So, what you probably want is # mount -t vfat -o loop=/dev/loop2 /tmp/r1 /mnt/somewhere or just simply # mount -t vfat -o loop /tmp/r1 /mnt/somewhere -- gentoo-user@gentoo.org mailing list