On Sonntag, 11. September 2016 11:43:17 PYT Tony Baldwin wrote:
> On 09/11/2016 08:59 AM, Eike Lantzsch wrote:
> > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> On 09
On 09/11/2016 08:59 AM, Eike Lantzsch wrote:
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wro
On Sonntag, 11. September 2016 09:17:41 PYT Anthony Baldwin wrote:
> On 09/11/2016 08:54 AM, Eike Lantzsch wrote:
> > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> On
On 09/11/2016 08:54 AM, Eike Lantzsch wrote:
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wro
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> > On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
> >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote:
> On 09/10/2016 03:07 PM,
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> > On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
> >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote:
> On 09/10/2016 03:07 PM,
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured o
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in its output, etc..
it really just confuses me...
I
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in its output, etc..
it really just confuses me...
I saw this: 15.690807] EXT3-fs (sda1): warning
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
> I apologize, but, I've never quite figured out what to do with dmesg,
> or what to look for in its output, etc..
> it really just confuses me...
> I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running
> e2fsck is
On 09/10/2016 02:26 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
The output of dmesg will tell you more.
perhaps some of this will be useful?
# fdisk -l
It is a little. But much less than the source of information I mentioned in
my first mail and tha
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
> >The output of dmesg will tell you more.
> perhaps some of this will be useful?
> # fdisk -l
It is a little. But much less than the source of information I mentioned in
my first mail and that you utterly ignored.
> /dev/sdb2 * 4
On 09/10/2016 01:53 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
ls: cannot access winhome: Input/output error
ls: cannot access myown: Permission denied
ls: cannot access win7: Input/output error
If you are lucky, fsck (or the windows equivalent) will
On 09/10/2016 01:45 PM, Tony Baldwin wrote:
Suddenly I can't mount my 2nd hdd, it's been fine, but after a reboot
today, I get I/O errors trying to mount the two partitions on it with
this script:
#!/bin/bash
if [ $(whoami) != "root" ]; then
echo "must be root, bitch"
exit
else
mou
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
> ls: cannot access winhome: Input/output error
> ls: cannot access myown: Permission denied
> ls: cannot access win7: Input/output error
If you are lucky, fsck (or the windows equivalent) will fix this.
If you are less lucky, you need t
On Wed, Jan 29, 2003 at 05:57:57PM -0500, harshu wrote:
> Hi,
>
>
> ->>
> ->> I am facing this problem with mounting vfat partitions. I have
> ->> a directory named /cdrive and mount my vfat partions on it. As root
> ->> user
> ->> or as an odinary user the permissons of cdrive always get change
Hi,
->>
->> I am facing this problem with mounting vfat partitions. I have
->> a directory named /cdrive and mount my vfat partions on it. As root
->> user
->> or as an odinary user the permissons of cdrive always get changed to
->> 744. I have tried changing the permisions to 777 as root use
On Tue, Jan 28, 2003 at 05:58:17AM -0800, Harshu wrote:
> Hi Folks,
>
> I am facing this problem with mounting vfat partitions. I have
> a directory named /cdrive and mount my vfat partions on it. As root
> user
> or as an odinary user the permissons of cdrive always get changed to
> 744. I have
Find out that removing /etc/mtab forced mount to report
everything correctly. Removing /etc/mtab and restarting
coursed the problem to be fixed (Hope that really fixed)
But still can't understand the reason.
"E.L. Meijer \(Eric\)" <[EMAIL PROTECTED]> writes:
> >
> > Thanks to all. However this problem is not solved:
> >
> > /rex is an empty directory created as a mount point.
> >
> > "sudo fuser /rex" and "sudo fuser /rex" return nothing.
> >
> > There is no /dev/rex
>
>
> But in
>
> Thanks to all. However this problem is not solved:
>
> /rex is an empty directory created as a mount point.
>
> "sudo fuser /rex" and "sudo fuser /rex" return nothing.
>
> There is no /dev/rex
But in a previous post you wrote (if I got the quoting right):
> sudo moun
Thanks to all. However this problem is not solved:
/rex is an empty directory created as a mount point.
"sudo fuser /rex" and "sudo fuser /rex" return nothing.
There is no /dev/rex
Bob
--
_
|_) _ |_ Robert D. Hilliard<[EMAIL PROTECTED]>
|_) (_) |_) Palm
On Tue, Jan 19, 1999 at 05:55:11PM -0500, Bob Hilliard wrote (in part):
> sudo mount /dev/hda4 or sudo mount /dev/rex
> I get the response mount: /dev/hda4 already mounted or /rex busy.
> However, df, mount and /mtab all show that /dev/hda4 is not mounted.
Try "fuser -v /rex". I can reproduc
>
> Bob Hilliard <[EMAIL PROTECTED]> writes:
>
> > sudo mount /dev/hda4 or sudo mount /dev/rex
> >
> > I get the response mount: /dev/hda4 already mounted or /rex busy.
> > However, df, mount and /mtab all show that /dev/hda4 is not mounted.
>
> Are you sure that you have an *empty* /rex d
Bob Hilliard <[EMAIL PROTECTED]> writes:
> sudo mount /dev/hda4 or sudo mount /dev/rex
>
> I get the response mount: /dev/hda4 already mounted or /rex busy.
> However, df, mount and /mtab all show that /dev/hda4 is not mounted.
Are you sure that you have an *empty* /rex directory before you
27 matches
Mail list logo
