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
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
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 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
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
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
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
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
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
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...
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):
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
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 *
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
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
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
mount /media/win7
mount
I need some advice in troubleshooting mount problems. I've got al ls120
superdisk that I'm trying to mount. I've installed it as the secondary
device on my main ide channel, behind the boot hard drive.
Here's what I've got in my fstab:
/dev/hdb /media/ls120 vfatrw,user,noauto 0
ChadDavis wrote:
I need some advice in troubleshooting mount problems. I've got al ls120
superdisk that I'm trying to mount. I've installed it as the secondary
device on my main ide channel, behind the boot hard drive.
Here's what I've got in my fstab:
/dev/hdb /media/ls120 vfat
Redirecting to list
ChadDavis wrote:
/dev/hdb is the whole disk I doubt you want to mount it like this.
#dmesg | grep hdb should give you some idea whether its seen
dmesg gives me :
sudo dmesg | grep hdb
[17179574.996000] ide0: BM-DMA at 0xf000-0xf007, BIOS settings:
After the recent update in testing, mount is behaving differently (for
me). My /etc/fstab has the following lines:
# /etc/fstab: static file system information.
#
/dev/hda3 / ext3defaults,errors=remount-ro 0 1
/dev/hda8 noneswapsw
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 changed to
- 744. I
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 tried
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 user but I am
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 tried changing the permisions to 777 as root user but I am
unable to
* Jeffrey W. Baker ([EMAIL PROTECTED]) spake thusly:
Try: rm /dev/scd0 mknod /dev/scd0 b 11 0
Optionally, chgrp cdrom /dev/scd0
excellent! that did the trick.
thanks to everyone for their assistance.
--
) ,_),_)
(-(__ |_ _ _ |/
) | |(_)(_ |\
( \_,
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor CD-RW. When I mount any CD,
I get the following:
# mount /cdrom
mount: /dev/cdrom is not a block device
/cdrom, through /etc/fstab, points to /dev/cdrom:
# cat /etc/fstab | grep cdrom
On Sat, 29 Dec 2001, shock wrote:
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor CD-RW. When I mount any CD,
I get the following:
# mount /cdrom
mount: /dev/cdrom is not a block device
/cdrom, through /etc/fstab, points to
shock wrote:
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor CD-RW. When I mount any CD,
I get the following:
# mount /cdrom
mount: /dev/cdrom is not a block device
/cdrom, through /etc/fstab, points to /dev/cdrom:
# cat /etc/fstab
* Jeffrey W. Baker ([EMAIL PROTECTED]) spake thusly:
On Sat, 29 Dec 2001, shock wrote:
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor CD-RW. When I mount any CD,
I get the following:
# mount /cdrom
mount: /dev/cdrom
On Sat, Dec 29, 2001 at 07:02:13PM -0600, shock wrote:
| * Jeffrey W. Baker ([EMAIL PROTECTED]) spake thusly:
| # ls -al /dev/sr0
|
| lrwxrwxrwx 1 root root 4 Dec 13 19:32 /dev/sr0 - scd0
|
| how do i know what its numbers are? do i need to delete it and recreate
| it?
/dev/sr0 is a symlink
* David Gardi ([EMAIL PROTECTED]) spake thusly:
shock wrote:
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor CD-RW. When I mount any CD,
I get the following:
# mount /cdrom
mount: /dev/cdrom is not a block device
Try linking
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
shock wrote:
* David Gardi ([EMAIL PROTECTED]) spake thusly:
shock wrote:
I've recently trashed a RH6.2 machine in favor of Debian Woody.
This is an all SCSI machine, with a Plextor
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
# ls -al /dev/cdrom
lrwxrwxrwx1 root root 3 Dec 29 20:53 /dev/cdrom - sr0
# ls -al /dev/sr0
lrwxrwxrwx1 root root 4 Dec 13 19:32
On Sat, 29 Dec 2001, shock wrote:
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
# ls -al /dev/cdrom
lrwxrwxrwx1 root root 3 Dec 29 20:53 /dev/cdrom - sr0
# ls -al /dev/sr0
shock wrote:
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
# ls -al /dev/cdrom
lrwxrwxrwx1 root root 3 Dec 29 20:53 /dev/cdrom - sr0
# ls -al /dev/sr0
lrwxrwxrwx1
Jeffrey W. Baker wrote:
On Sat, 29 Dec 2001, shock wrote:
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
# ls -al /dev/cdrom
lrwxrwxrwx1 root root 3 Dec 29 20:53
On Sat, Dec 29, 2001 at 09:10:39PM -0600, shock wrote:
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
Does the required device exist?
man MAKEDEV
cd dev; ./MAKEDEV [ -n ] [ -v ] update
# ls -al /dev/cdrom
lrwxrwxrwx1 root root 3 Dec 29 20:53 /dev/cdrom - sr0
Hello,
I am having difficulty getting a sony PCGA-CD51/A(PCMIA) to mount.
Currently, I am running SID(unstable) on a Sony PCG-SR5K.
I am running linux ide1=0x180,0x386 for CD.
I have added the following lines to my pcmcia setup:
/etc/pcmcia/config
ard SONY PCGA-CD5 CD-ROM
version ,
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.
Hi All,
I've got the following problem:
My debian system use one local fs (/dev/hda2 on / (rw))
But time to time I've to mount some other (network) fs
This works fine, so simple asking mount I receive list
of all mounted fs.
Now when i do umount that network fs this clear ALL
information about
I sometimes get this problem on my CDROM and I am not sure whether it is
hardware related.
At moment my kernel is configured with scsi-emulation because I use a
CD-RW also.
Sometimes when I mount my regular CDROM I get error messages and
segmentation faults. Sometimes it just hangs like this:
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 City,
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 mount /dev/hda4
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 a previous post you wrote
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 try
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
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 reproduce
I have a spare machine that I am trying to set up for backups
using an ethernet net.
One partition (a bo system) has root mounted on /dev/hda3. If I
login to this machine, and try to mount another partition, using:
sudo mount /dev/hda4 or sudo mount /dev/rex
I get the response
Hi,
I had two bo Linux box with 2.0.30, and a directory exported from
one to other. This used to work until I put 2.0.33. Now, with all the same
configuration, I get the message:
mount clntudp_create: RPC: Program not registered
Both boxes have NFS properly compiled, installed
On Tue, 10 Dec 1996, Alexander Gieg wrote:
The only boot disk that I have is the one of Debian Installation.
Do you believe that its root disk hasn't the e2fsck program?
It's reasons like this that I keep a Slackware boot/'rescue' root disk set
in the disk box. I heard that there is now a
Hello again.
I'm new to the Linux Wonderfull World, and surfing the Web,
I found the Debian page. I downloaded the Debian Linux, installed
it, and used (+/-) since October, but I've not much experience, and
an energy problem caused the system to display this message when the
computer
On Mon, 09 Dec 1996 16:38:05 -0200 Alexander Gieg
([EMAIL PROTECTED]) wrote:
Hello!
I'm new to the Linux Wonderfull World, and surfing the Web,
I found the Debian page. I downloaded the Debian Linux, installed
it, and used (+/-) since October, but I've not much experience, and
an energy
On Tue, 10 Dec 1996 00:39:00 -0200 Alexander Gieg
([EMAIL PROTECTED]) wrote:
I've attempted to boot with a diskette, and tried to manually mount
the fs, because I know that there is another tables on the partition,
but I don't know the 'mount' program, as the ext2-fs, *so* well.
Ok, to mount an ext2 filesystem:
mount -t ext2 /dev/partition mountpoint
From what I see above, your partition should be /dev/hdb1. A typical
mountpoint is /mnt.
I tried this, but its results was an error message. :-(
Looks like it's verty f**cked'up then...
You linux root
Hello!
I'm new to the Linux Wonderfull World, and surfing the Web,
I found the Debian page. I downloaded the Debian Linux, installed
it, and used (+/-) since October, but I've not much experience, and
an energy problem caused the system to display this message when the
computer rebooted:
57 matches
Mail list logo
