[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#641167: base: Any call to mount returns /dev/<device name> : No such device (fwd)



[Oops, I sent this to the wrong bug address. Resending to the correct one, for the record.]

Hi John-Charles,

I'm reassigning this bug to kfreebsd-8 on the basis that that's where the following similar bug report was filed:
  http://bugs.debian.org/593733
I don't think it's the same bug, though. But hopefully this should get it visible by a kFreeBSD user or developer, who can reassign it elsewhere (the mount command, perhaps?) if this is incorrect.

--
Geoffrey Thomas
http://ldpreload.com
geofft@ldpreload.com

On Sat, 10 Sep 2011, John-Charles D. Sokolow wrote:

Package: base
Severity: grave

Dear Maintainer,


  * What led up to the situation?
    While attempting to mount a second hard disk which contains some
    data I recieved "No such device" error.
  * What exactly did you do (or not do) that was effective (or
    ineffective)?
    I confirmed both that the device exists and had not been acidently erased
    through installing gparted I confirmed that the device /dev/ad1s2 was
    present on the disk and valid. I called the stat command stat /dev/ad1s2
    to validate that the device file existed. stat printed out valid
    information about the file. I attempted to validate that I had permission
    to mount. both using sudo, and running mount as root after using su root.

  * What was the outcome of this action?
    There was no specific outcome of this action. The problem persists the
    only file system that was able to be mounted was root. No other file
    system can be mounted on the system anywhere my any user with any
    level of permission.

  * What outcome did you expect instead?
    To successfully mount the file system on my second partition.

    Further notes. I have not changed this file system during the os install
    it is on a seperate hard disk. Not that the disk also as a fat file
    system, and a btrfs file system on it. Neither were able to mount either.
    Furthermore, the file system I was attempting to mount is an active root
    partition for a debian instance which can successfully boot if I rebot
    the system.


-- System Information:
Debian Release: wheezy/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 8.2-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash







Reply to: