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

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

Your message dated Mon, 02 Sep 2013 21:16:43 +0000
with message-id <E1VGbUJ-00033e-A2@franck.debian.org>
and subject line Bug#721540: Removed package(s) from unstable
has caused the Debian Bug report #641167,
regarding base: Any call to mount returns /dev/<device name> : No such device
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
641167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641167
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Version: 8.3-7+rm

Dear submitter,

as the package kfreebsd-8 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/721540

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

--- End Message ---
Reply to: