Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Richard Hector wrote, on 06/02/10 09:07:

On Sat, 2010-02-06 at 07:39 +1030, Arthur Marsh wrote:

Last question is, what guarantee is there that the device file will have 
been generated (assuming that the USB drive is present) before the 
@reboot cron event is run?


The standard mount script is run in runlevel S, which is entered before
the numbered runlevels which is where cron is started. So I'm guessing
if the device is there in time to be mounted from fstab, it will be
there before cron runs.

Richard


Thanks, that turned out to be the case and appears to work well.

Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Richard Hector]

On Sat, 2010-02-06 at 07:39 +1030, Arthur Marsh wrote:

> Last question is, what guarantee is there that the device file will have 
> been generated (assuming that the USB drive is present) before the 
> @reboot cron event is run?

The standard mount script is run in runlevel S, which is entered before
the numbered runlevels which is where cron is started. So I'm guessing
if the device is there in time to be mounted from fstab, it will be
there before cron runs.

Richard



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Dave Thayer wrote, on 05/02/10 16:01:

On Wed, Feb 03, 2010 at 11:01:00PM +1030, Arthur Marsh wrote:

In my case I have:

UUID=4823-93A9  /mnt/usb8gigvfat
defaults,users,uid=65534,gid=65534,umask=000,shortname=win95
0 2

(all on one line)

If I change that trailing "2" to a zero, no fsck should be performed.

I would like to have automatic mounting with fsck if the drive is
present when the machine is booted, and automatic mounting without
fsck if the drive is plugged in after the machine is booted.

Is this possible with any of the standard Debian tools and config
files, or will it require yet-another-script?



How about if you leave your fstab set up for no automount and no fsck,


Like:

UUID=4823-93A9 /mnt/usb8gig vfat 
defaults,users,uid=65534,gid=65534,umask=000,flush,shortname=win95,noauto 
  0   0


(all on the one line)


and then use a @reboot cronjob to fsck and mount the device if the
device node is present. For instance, in /etc/crontab you could try:

@reboot root test -L /dev/disk/by-uuid/4823-93A9 && fsck.vfat -a
/dev/disk/by-uuid/4823-93A9 && mount /mnt/usb8gig

(all on one line, with terminating newline)


OK, man 5 crontab shows that @reboot can be used instead of the first 5 
fields of /etc/crontab


Last question is, what guarantee is there that the device file will have 
been generated (assuming that the USB drive is present) before the 
@reboot cron event is run?


incron might be able to help, but I haven't yet fully understood how to 
set up incron.


Thanks for your help!

Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Dave Thayer]

On Wed, Feb 03, 2010 at 11:01:00PM +1030, Arthur Marsh wrote:
> 
> In my case I have:
> 
> UUID=4823-93A9  /mnt/usb8gigvfat
> defaults,users,uid=65534,gid=65534,umask=000,shortname=win95
> 0 2
> 
> (all on one line)
> 
> If I change that trailing "2" to a zero, no fsck should be performed.
> 
> I would like to have automatic mounting with fsck if the drive is
> present when the machine is booted, and automatic mounting without
> fsck if the drive is plugged in after the machine is booted.
> 
> Is this possible with any of the standard Debian tools and config
> files, or will it require yet-another-script?
> 

How about if you leave your fstab set up for no automount and no fsck,
and then use a @reboot cronjob to fsck and mount the device if the
device node is present. For instance, in /etc/crontab you could try:

@reboot root test -L /dev/disk/by-uuid/4823-93A9 && fsck.vfat -a
/dev/disk/by-uuid/4823-93A9 && mount /mnt/usb8gig

(all on one line, with terminating newline)

HTH

dt

-- 
Dave Thayer   | Whenever you read a good book, it's like the 
Denver, Colorado USA  | author is right there, in the room talking to 
d...@thayer-boyle.com | you, which is why I don't like to read 
  | good books. - Jack Handey "Deep Thoughts"


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Celejar]

On Thu, 4 Feb 2010 17:42:45 -0600
"Boyd Stephen Smith Jr."  wrote:

...

> If the file system may or may not be there, the information about the file 
> system is not *static* (unchanging).  Because the answer is sometimes 
> "/dev/some/thing/or/other" and sometimes the answer is NULL and errno is set 
> to ENOENT (No such file or directory).

I see your point, but I disagree.  I think that the fact that the fs is
always in the same place when it's there is sufficient to consider its
information static, the fact that it sometimes isn't there at all
notwithstanding.

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

On Thursday 04 February 2010 17:00:49 Celejar wrote:
> On Thu, 4 Feb 2010 10:31:10 -0600
> "Boyd Stephen Smith Jr."  wrote:
> > In any case, /etc/fstab is for *static* file systems.  It is *not* for
> > file systems that may or may not be there when the system is booting (or
> > otherwise in operation).
> 
> Please substantiate this assertion with some documentation.  The
> manpage just mentions "static information about the filesystems" - I see
> nothing that implies that it "is *not* for file systems that may or may
> not be there when the system is booting".

If the file system may or may not be there, the information about the file 
system is not *static* (unchanging).  Because the answer is sometimes 
"/dev/some/thing/or/other" and sometimes the answer is NULL and errno is set 
to ENOENT (No such file or directory).
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Celejar]

On Thu, 4 Feb 2010 10:31:10 -0600
"Boyd Stephen Smith Jr."  wrote:

...

> In any case, /etc/fstab is for *static* file systems.  It is *not* for file 
> systems that may or may not be there when the system is booting (or otherwise 
> in operation).

Please substantiate this assertion with some documentation.  The
manpage just mentions "static information about the filesystems" - I see
nothing that implies that it "is *not* for file systems that may or may
not be there when the system is booting".

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Jochen Schulz]

Boyd Stephen Smith Jr.:
> On Thursday 04 February 2010 10:53:06 Jochen Schulz wrote:
>> Boyd Stephen Smith Jr.:
>>> In any case, /etc/fstab is for *static* file systems.  It is *not* for
>>> file systems that may or may not be there when the system is booting (or
>>> otherwise in operation).
>> 
>> NACK. Or don't you have an entry for your CD/DVD drive?
> 
> That's what "noauto" is for.

Sure. But the existence of that option refutes your statement above. :)

J.
-- 
If you do not move for long enough, you might see a rat.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

On Thursday 04 February 2010 11:44:36 Pier Paolo wrote:
> Yeah! An udev rule seems a good approach to me: i want to rsync my
> backup on an external drive. I'm using rsnapshot/cron stuff, but i'll
> get soon annoyed about to control the log, see if backup is already made
> and all, as there is no way in rsnapshot script (for what i understand)
> to assure the excpected backup frequency (with an EXTERNAL USB DISK i
> mean: no cron/anacron, maybe vfs or kde device mounter... i don't know)
> 
> So, if someone could please tell me how/where to look for this udev rule
> thing...

http://reactivated.net/writing_udev_rules.html

Specifically, http://reactivated.net/writing_udev_rules.html#external-run

Your udev rules will generally reside under /etc/udev/rules.d.

Since a backup/sycn operation can take a while, remember this warning: "This 
program can act on the device, however it must not run for any extended period 
of time, because udev is effectively paused while these programs are running. 
One workaround for this limitation is to make sure your program immediately 
detaches itself."
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Pier Paolo]

Il giorno gio, 04/02/2010 alle 23.57 +1030, Arthur Marsh ha scritto:
> Pier Paolo wrote, on 04/02/10 04:07:
> > Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:
> >> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
> >>
> >>> Camaleón wrote, on 03/02/10 21:52:
>  You should not list your devices in fstab if you want to make use of
>  your DE hotplug capabilities.
> 
> >>> As I just posted in another message in this thread, I'd like the USB
> >>> flash drive to be automatically mounted after fsck if the drive is
> >>> present at boot-up and automatically mounted without fsck if plugged in
> >>> after the machine is booted.
> >> As said, if you list the USB device in fstab, the system will try to 
> >> mount it on every boot, whether is plugged or not.
> >>  
> >>> I would also like the machine to boot fully if it is started without the
> >>> USB flash drive present.
> >> That should not happen at all (if the disk is not present it should log a 
> >> warn, but the system should keep loading). It can be a bug.
> >>
> >>> Any takers for suggestions?
> >> Greetings,
> >>
> >> -- 
> >> Camaleón
> >>
> >>
> > 
> > Maybe OT: what about executing a sh command on specific usb drive
> > mounts, on gnome and kde? As of as i recall from the debian wiki that's
> > not explained. Maybe in gentoo docs, i'll see.
> > 
> > Thanks for any hints.
> 
> Do you mean rather than using an /etc/fstab entry or a package like 
> usbmount, have a udev rule that on detection of the USB device, either 
> does an fsck and mount (at machine boot time) or just a mount of the 
> device (if the device appears after machine boot time)?
> 
> Arthur.
> 
> 
Yeah! An udev rule seems a good approach to me: i want to rsync my
backup on an external drive. I'm using rsnapshot/cron stuff, but i'll
get soon annoyed about to control the log, see if backup is already made
and all, as there is no way in rsnapshot script (for what i understand)
to assure the excpected backup frequency (with an EXTERNAL USB DISK i
mean: no cron/anacron, maybe vfs or kde device mounter... i don't know)

So, if someone could please tell me how/where to look for this udev rule
thing...

thanks.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

On Thursday 04 February 2010 10:53:06 Jochen Schulz wrote:
> Boyd Stephen Smith Jr.:
> > In any case, /etc/fstab is for *static* file systems.  It is *not* for
> > file systems that may or may not be there when the system is booting (or
> > otherwise in operation).
> 
> NACK. Or don't you have an entry for your CD/DVD drive?

That's what "noauto" is for.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Thu, 04 Feb 2010 10:31:10 -0600, Boyd Stephen Smith Jr. wrote:

> On Thursday 04 February 2010 09:04:08 Camaleón wrote:

>> Yes, but the mount point of the OP is not critical for his system, that
>> was what I wanted to say. And the kernel must be aware of that device
>> is trivial and can be skipped without any drawbacks.
> 
> Why must the kernel be aware of that?  That's a human decision, not a
> technical one.

Because (correct me if I am wrong) it is defined by the docs what are the 
minimal requirements for a linux system to boot. It's a hierarquical 
system, and so are services: there are some services you can bypass 
without having penalties at startup (boot process can be delayed, but not 
stopped), but there are other critical services that unless started, the 
system will refuse to boot.

I think that makes sense and the same remains for fstab, at least that is 
my point.
 
> I can certainly see reasons that a device attached via USB might be
> considered to the user to be critical.

Yes, so do I. If "/boot" partition is located there, for instance :-). 
But a standard linux system does not search for "/my_mount_point/
my_device" unless it is explicitly specified by the user.

And you know, you cannot trust what users do so much :-P

> In any case, /etc/fstab is for *static* file systems.  It is *not* for
> file systems that may or may not be there when the system is booting (or
> otherwise in operation).

Yes, I know, and I think so. 

But the OP found a problem with his setup and he's looking for a solution.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Jochen Schulz]

Boyd Stephen Smith Jr.:
> 
> In any case, /etc/fstab is for *static* file systems.  It is *not* for file 
> systems that may or may not be there when the system is booting (or otherwise 
> in operation).

NACK. Or don't you have an entry for your CD/DVD drive?

J.
-- 
If I had to live on a desert island I would take a mobile phone,
preferably a Nokia 8810.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

On Thursday 04 February 2010 09:04:08 Camaleón wrote:
> On Thu, 04 Feb 2010 08:50:58 -0600, Boyd Stephen Smith Jr. wrote:
> > In , Camaleón wrote:
> >>But I still find the point valid: if a mount point defined in "fstab" is
> >>not present at boot time, it should warn the user and log the error but
> >>the boot process should not be stopped at all because the mount point is
> >>not critical (i.e., is not root "/") for the system to properly start.
> >
> > There are filesystems other than '/' that I need to have a fully
> > functional system:
> 
> Yes, but the mount point of the OP is not critical for his system, that
> was what I wanted to say. And the kernel must be aware of that device is
> trivial and can be skipped without any drawbacks.

Why must the kernel be aware of that?  That's a human decision, not a 
technical one.

I can certainly see reasons that a device attached via USB might be considered 
to the user to be critical.

In any case, /etc/fstab is for *static* file systems.  It is *not* for file 
systems that may or may not be there when the system is booting (or otherwise 
in operation).
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Thu, 04 Feb 2010 08:50:58 -0600, Boyd Stephen Smith Jr. wrote:

> In , Camaleón wrote:

>>But I still find the point valid: if a mount point defined in "fstab" is
>>not present at boot time, it should warn the user and log the error but
>>the boot process should not be stopped at all because the mount point is
>>not critical (i.e., is not root "/") for the system to properly start.
> 
> There are filesystems other than '/' that I need to have a fully
> functional system:

Yes, but the mount point of the OP is not critical for his system, that 
was what I wanted to say. And the kernel must be aware of that device is 
trivial and can be skipped without any drawbacks.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

In , Camaleón wrote:
>On Fri, 05 Feb 2010 00:01:17 +1030, Arthur Marsh wrote:
>> The response I received to
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the
>> responder thinks that running fsck on a non-existent device is the
>> proper behaviour /-:.
>
>I've also found some "opposition" from developers while reporting bugs ;-)
>
>But I still find the point valid: if a mount point defined in "fstab" is
>not present at boot time, it should warn the user and log the error but
>the boot process should not be stopped at all because the mount point is
>not critical (i.e., is not root "/") for the system to properly start.

There are filesystems other than '/' that I need to have a fully functional 
system:

$ df -Ph
FilesystemSize  Used Avail Use% Mounted on
/dev/md0  981M  466M  515M  48% /
tmpfs 2.0G  8.0K  2.0G   1% /lib/init/rw
udev   10M  272K  9.8M   3% /dev
tmpfs 2.0G   12K  2.0G   1% /dev/shm
/tmp  2.0G   32M  2.0G   2% /tmp
/dev/mapper/monster-home  1.2T  1.1T  109G  92% /home
/dev/mapper/monster-media  4.3T  4.2T  120G  98% /home/bss/media
/dev/mapper/monster-opt  1.0G   33M  992M   4% /opt
/dev/mapper/monster-srv  1.0G   37M  988M   4% /srv
/dev/mapper/monster-usr  8.0G  5.7G  2.4G  72% /usr
/dev/mapper/monster-usr.local  1.0G   36M  989M   4% /usr/local
/dev/mapper/monster-var  4.0G  1.3G  2.8G  31% /var
/dev/mapper/monster-var.cache  8.0G  4.1G  4.0G  51% /var/cache
/dev/mapper/monster-var.tmp  4.0G  398M  3.7G  10% /var/tmp

-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Fri, 05 Feb 2010 00:01:17 +1030, Arthur Marsh wrote:

> Camaleón wrote, on 04/02/10 03:05:
 
>>> I would also like the machine to boot fully if it is started without
>>> the USB flash drive present.
>> 
>> That should not happen at all (if the disk is not present it should log
>> a warn, but the system should keep loading). It can be a bug.
> 
> The response I received to
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the
> responder thinks that running fsck on a non-existent device is the
> proper behaviour /-:.

I've also found some "opposition" from developers while reporting bugs ;-)

But I still find the point valid: if a mount point defined in "fstab" is 
not present at boot time, it should warn the user and log the error but 
the boot process should not be stopped at all because the mount point is 
not critical (i.e., is not root "/") for the system to properly start.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Boyd Stephen Smith Jr.]

In <5quq37-nql@ppp121-45-136-118.lns11.adl6.internode.on.net>, Arthur 
Marsh wrote:
>Camaleón wrote, on 04/02/10 03:05:
>> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
>>> Camaleón wrote, on 03/02/10 21:52:
 You should not list your devices in fstab if you want to make use of
 your DE hotplug capabilities.
>>>
>>> As I just posted in another message in this thread, I'd like the USB
>>> flash drive to be automatically mounted after fsck if the drive is
>>> present at boot-up and automatically mounted without fsck if plugged in
>>> after the machine is booted.
>>
>> As said, if you list the USB device in fstab, the system will try to
>> mount it on every boot, whether is plugged or not.
>>
>>> I would also like the machine to boot fully if it is started without the
>>> USB flash drive present.
>>
>> That should not happen at all (if the disk is not present it should log a
>> warn, but the system should keep loading). It can be a bug.
>
>The response I received to
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the
>responder thinks that running fsck on a non-existent device is the
>proper behaviour /-:.

I tend to agree.  /etc/fstab is for static file systems, where "static" means 
"always present in always the same location".  I don't want any of my file 
systems in /etc/fstab to simply be "skipped" because their device isn't 
present -- I want a *LOUD* warning.

Exceptions -- file systems I don't want checked get a passno of 0; file 
systems I don't want mounted get noauto flag.

IMHO, you are using /etc/fstab wrong and you'd better suited to using some 
other method of fscking and mounting.  Udev can run a command as soon as the 
device node is available, but be aware that udev blocks until the command is 
complete.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Camaleón wrote, on 04/02/10 03:05:

On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:


Camaleón wrote, on 03/02/10 21:52:



You should not list your devices in fstab if you want to make use of
your DE hotplug capabilities.


As I just posted in another message in this thread, I'd like the USB
flash drive to be automatically mounted after fsck if the drive is
present at boot-up and automatically mounted without fsck if plugged in
after the machine is booted.


As said, if you list the USB device in fstab, the system will try to 
mount it on every boot, whether is plugged or not.
 

I would also like the machine to boot fully if it is started without the
USB flash drive present.


That should not happen at all (if the disk is not present it should log a 
warn, but the system should keep loading). It can be a bug.


The response I received to 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the 
responder thinks that running fsck on a non-existent device is the 
proper behaviour /-:.


Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Pier Paolo wrote, on 04/02/10 04:07:

Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:

On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:


Camaleón wrote, on 03/02/10 21:52:

You should not list your devices in fstab if you want to make use of
your DE hotplug capabilities.


As I just posted in another message in this thread, I'd like the USB
flash drive to be automatically mounted after fsck if the drive is
present at boot-up and automatically mounted without fsck if plugged in
after the machine is booted.
As said, if you list the USB device in fstab, the system will try to 
mount it on every boot, whether is plugged or not.
 

I would also like the machine to boot fully if it is started without the
USB flash drive present.
That should not happen at all (if the disk is not present it should log a 
warn, but the system should keep loading). It can be a bug.



Any takers for suggestions?

Greetings,

--
Camaleón




Maybe OT: what about executing a sh command on specific usb drive
mounts, on gnome and kde? As of as i recall from the debian wiki that's
not explained. Maybe in gentoo docs, i'll see.

Thanks for any hints.


Do you mean rather than using an /etc/fstab entry or a package like 
usbmount, have a udev rule that on detection of the USB device, either 
does an fsck and mount (at machine boot time) or just a mount of the 
device (if the device appears after machine boot time)?


Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Pier Paolo]

Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:
> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
> 
> > Camaleón wrote, on 03/02/10 21:52:
> 
> >> You should not list your devices in fstab if you want to make use of
> >> your DE hotplug capabilities.
> >> 
> > As I just posted in another message in this thread, I'd like the USB
> > flash drive to be automatically mounted after fsck if the drive is
> > present at boot-up and automatically mounted without fsck if plugged in
> > after the machine is booted.
> 
> As said, if you list the USB device in fstab, the system will try to 
> mount it on every boot, whether is plugged or not.
>  
> > I would also like the machine to boot fully if it is started without the
> > USB flash drive present.
> 
> That should not happen at all (if the disk is not present it should log a 
> warn, but the system should keep loading). It can be a bug.
> 
> > Any takers for suggestions?
> 
> Greetings,
> 
> -- 
> Camaleón
> 
> 

Maybe OT: what about executing a sh command on specific usb drive
mounts, on gnome and kde? As of as i recall from the debian wiki that's
not explained. Maybe in gentoo docs, i'll see.

Thanks for any hints.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:

> Camaleón wrote, on 03/02/10 21:52:

>> You should not list your devices in fstab if you want to make use of
>> your DE hotplug capabilities.
>> 
> As I just posted in another message in this thread, I'd like the USB
> flash drive to be automatically mounted after fsck if the drive is
> present at boot-up and automatically mounted without fsck if plugged in
> after the machine is booted.

As said, if you list the USB device in fstab, the system will try to 
mount it on every boot, whether is plugged or not.
 
> I would also like the machine to boot fully if it is started without the
> USB flash drive present.

That should not happen at all (if the disk is not present it should log a 
warn, but the system should keep loading). It can be a bug.

> Any takers for suggestions?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Camaleón wrote, on 03/02/10 21:52:

On Wed, 03 Feb 2010 00:30:47 -0500, Frank McCormick wrote:


Camaleón wrote:



Mmm... I think "LABEL" would take precedence over another mount option

<<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it

should be mounted when plugged under "/media/mylabel".

  Well Label didn't work in my case either - I gave the USB drive a
  label
of Music...then changed fstab to the LABEL=Music from /dev/sda1

The drive did not get mounted and I had to go back to /dev/sda1

But as long as /dev/sda1 is used, there is no fsck of the drive.


You should not list your devices in fstab if you want to make use of your 
DE hotplug capabilities.


Greetings,



As I just posted in another message in this thread, I'd like the USB 
flash drive to be automatically mounted after fsck if the drive is 
present at boot-up and automatically mounted without fsck if plugged in 
after the machine is booted.


I would also like the machine to boot fully if it is started without the 
USB flash drive present.


Any takers for suggestions?

Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Frank McCormick wrote, on 03/02/10 16:00:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

   
The bottom line: There is no problem even if

flashdrives/cameras etc are in fstab but not present- you
simply get the error logged

Well, there is a definite problem in my case (Debian unstable on
i386).

Error code 1 on fsck gets an error logged, but doesn't stop the
boot process.


Definite problem here, too, on my uptodate Sid system, with ext3.
My fstab has lines like this:

LABEL=software  /media/software ext3
defaults,user,exec,noauto   0   0




Camaleón wrote:



Mmm... I think "LABEL" would take precedence over another mount option 
<<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it 

should be mounted when plugged under "/media/mylabel".


  Well Label didn't work in my case either - I gave the USB drive a label
of Music...then changed fstab to the LABEL=Music from /dev/sda1

The drive did not get mounted and I had to go back to /dev/sda1

But as long as /dev/sda1 is used, there is no fsck of the drive.

Cheers


In my case I have:

UUID=4823-93A9  /mnt/usb8gigvfat 
defaults,users,uid=65534,gid=65534,umask=000,shortname=win950 2


(all on one line)

If I change that trailing "2" to a zero, no fsck should be performed.

I would like to have automatic mounting with fsck if the drive is 
present when the machine is booted, and automatic mounting without fsck 
if the drive is plugged in after the machine is booted.


Is this possible with any of the standard Debian tools and config files, 
or will it require yet-another-script?


Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Wed, 03 Feb 2010 00:30:47 -0500, Frank McCormick wrote:

>> Camaleón wrote:
> 
> 
>>>Mmm... I think "LABEL" would take precedence over another mount option
> <<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it
>>>should be mounted when plugged under "/media/mylabel".
> 
>   Well Label didn't work in my case either - I gave the USB drive a
>   label
> of Music...then changed fstab to the LABEL=Music from /dev/sda1
> 
> The drive did not get mounted and I had to go back to /dev/sda1
> 
> But as long as /dev/sda1 is used, there is no fsck of the drive.

You should not list your devices in fstab if you want to make use of your 
DE hotplug capabilities.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> > >
> > > The bottom line: There is no problem even if
> > > flashdrives/cameras etc are in fstab but not present- you
> > > simply get the error logged
> > 
> > Well, there is a definite problem in my case (Debian unstable on
> > i386).
> > 
> > Error code 1 on fsck gets an error logged, but doesn't stop the
> > boot process.
> > 
> 
> Definite problem here, too, on my uptodate Sid system, with ext3.
> My fstab has lines like this:
> 
> LABEL=software  /media/software ext3
> defaults,user,exec,noauto   0   0
> 

> Camaleón wrote:


>>Mmm... I think "LABEL" would take precedence over another mount option 
<<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it 
>>should be mounted when plugged under "/media/mylabel".

  Well Label didn't work in my case either - I gave the USB drive a label
of Music...then changed fstab to the LABEL=Music from /dev/sda1

The drive did not get mounted and I had to go back to /dev/sda1

But as long as /dev/sda1 is used, there is no fsck of the drive.

Cheers

- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaQoHAAoJEMEDyLTvrVhjPzoH+wdfQB1LpTBiran2Rf1A9IRL
SzpIPgXsf0glxaVwT5n1lKnOBUENqInmsnuZe5jNoVrF8aLohdRqFfBwxYX8kFwh
sfz9Rjp8oFr/ASZpgdmyvP2s4tGAeuh/rSNx2hEPJFQiZKpE7mOSmXQ1+6SGMzvq
sIh7yxKcmo8+14+Whc0GdaqCVKej3/aQW+nYkFbmA93Uy2xzkOP8Dox/DFDsFXMJ
NJnbspWbss/XEQTcLn61tKmxwoL3jpxFq5k/ytMFXu1rH7IFDrz5AMYHpG3roxEM
LG9zIEiF0pkflKrfQM1hk+hqdONjO9mtSkBgcyXWLNco3ErmoXyKKp/9Jy4Bvkg=
=bL9P
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Celejar]

On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh  wrote:

> Frank McCormick wrote, on 03/02/10 06:16:
> > 
> > To the OP:
> >
> > The bottom line: There is no problem even if flashdrives/cameras etc
> > are in fstab but not present- you simply get the error logged
> > 
> > 
> > Cheers
> > - -- 
> > Frank
> 
> Well, there is a definite problem in my case (Debian unstable on i386).
> 
> Error code 1 on fsck gets an error logged, but doesn't stop the boot 
> process.
> 
> Upgrading dosfstools past 3.0.1 caused an error code greater than 1, 
> which triggers the stop of the boot process.
> 
> I don't understand why initscripts tries to fsck a non-existent device.

Definite problem here, too, on my uptodate Sid system, with ext3.  My
fstab has lines like this:

LABEL=software  /media/software ext3
defaults,user,exec,noauto   0   0

[The target is a LV within a VG on top of a partition on an external
USB disk.]

When the last field is 2, the boot stops after fsck fails with error
code 8, until I hit -D.  From /var/log/fsck/fsck/checkfs

fsck.ext3: Unable to resolve 'LABEL=software'
fsck died with exit status 8

> Maybe I should file a bug against initscripts.

Probably a good idea.  I just changed the fs_passno field to 0, but a
bug is probably in order.

> I had initially filed a bug against dosfstools but had no response:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562536

Well, it's not really a bug in fsck, but, as you noted earlier, in
initscripts.  Perhaps you can just reassign the bug?

> I would just like to have USB flash drives that may or may not be 
> plugged into machines that aren't switched on all the time, and I would 
> like them to be mounted if they're plugged in when the machine is 
> powered on, and for the machine to boot anyway if the USB flash drive is 
> not present.

Exactly.  But mounting automatically is not the problem.  You can have
them mounted, without the fsck being performed.

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Frank McCormick wrote, on 03/02/10 10:01:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh  wrote:

   
The bottom line: There is no problem even if flashdrives/cameras

etc are in fstab but not present- you simply get the error logged

Well, there is a definite problem in my case (Debian unstable on
i386).

Error code 1 on fsck gets an error logged, but doesn't stop the
boot process.

Upgrading dosfstools past 3.0.1 caused an error code greater than
1, which triggers the stop of the boot process.

I don't understand why initscripts tries to fsck a non-existent
device.

Maybe I should file a bug against initscripts.

I had initially filed a bug against dosfstools but had no response:



  Very strange -
  This is my fstab# 


/etc/fstab: static file system information.
#
#
proc   /proc   procdefaults  0   0
/dev/hda2  /   ext3errors=remount-ro 0   1
/dev/hda1  noneswapsw0   0
/dev/hda5  noneswapsw0   0
/dev/hdc   /media/dvd  udf,iso9660 rw,user,noauto,unhide 0   0
/dev/hdd   /media/dvd-rom   udf,iso9660 rw,user,noauto,unhide 0   0
#/dev/fd0/media/floppy0  autorw,user,noauto  0   0
/dev/hda3  /media/intrepid autorw,user,auto  0   0
/dev/sda1  /media/FlashDrive  vfat  rw,user,auto 0   0
/dev/sdb1  /media/camera   vfat  rw,user,auto0   0


 I'm running testing with dosfstools 3.0.7-1

 sda1 is usually plugged in...but the camera usually is not.
 
- -- 
Frank


This is the /etc/fstab entry I had to comment out:

UUID=4823-93A9  /mnt/usb8gigvfat 
defaults,users,uid=65534,gid=65534,umask=000,shortname=win950 
2


(all on one line)

Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh  wrote:

> >
> > The bottom line: There is no problem even if flashdrives/cameras
> > etc are in fstab but not present- you simply get the error logged
> 
> Well, there is a definite problem in my case (Debian unstable on
> i386).
> 
> Error code 1 on fsck gets an error logged, but doesn't stop the
> boot process.
> 
> Upgrading dosfstools past 3.0.1 caused an error code greater than
> 1, which triggers the stop of the boot process.
> 
> I don't understand why initscripts tries to fsck a non-existent
> device.
> 
> Maybe I should file a bug against initscripts.
> 
> I had initially filed a bug against dosfstools but had no response:
> 

  Very strange -
  This is my fstab# 

/etc/fstab: static file system information.
#
#
proc   /proc   procdefaults  0   0
/dev/hda2  /   ext3errors=remount-ro 0   1
/dev/hda1  noneswapsw0   0
/dev/hda5  noneswapsw0   0
/dev/hdc   /media/dvd  udf,iso9660 rw,user,noauto,unhide 0   0
/dev/hdd   /media/dvd-rom   udf,iso9660 rw,user,noauto,unhide 0   0
#/dev/fd0/media/floppy0  autorw,user,noauto  0   0
/dev/hda3  /media/intrepid autorw,user,auto  0   0
/dev/sda1  /media/FlashDrive  vfat  rw,user,auto 0   0
/dev/sdb1  /media/camera   vfat  rw,user,auto0   0


 I'm running testing with dosfstools 3.0.7-1

 sda1 is usually plugged in...but the camera usually is not.
 
- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaLXLAAoJEMEDyLTvrVhjYMQH/2HnvNIaWZCBnT+1bKBOvxry
dk+iJDaKC4PqJ4ZolFyFDTXU5ZWgcCE8Nsi1iNLLv3uwl8nPhRIyBLjksdMk1ewq
Zgn76x+YBpfpan3cy0ATFFKCzrCYIfooofeGIjBilFYQXi1DvpLOOrfiFMJUDOxh
rJH+4h7hjCN7amZsDpm02wAKZ5lv013X8HClkqDSH3lyePmAwE5NHsRGbjqLjZsV
O/rmvwX5SawcTLVQNmRuQZbKqmJSPIK5k5lHBBFSW/+78PwU/CjheUpYfxs+gZFT
QDpIn7NbosYsX6xXE+Uo2N8NCiQgvzCVDjUzofZMO4gIrcWLczPI+Y6vjOktuzA=
=vppa
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Frank McCormick wrote, on 03/02/10 06:16:


To the OP:
   
The bottom line: There is no problem even if flashdrives/cameras etc

are in fstab but not present- you simply get the error logged


Cheers
- -- 
Frank


Well, there is a definite problem in my case (Debian unstable on i386).

Error code 1 on fsck gets an error logged, but doesn't stop the boot 
process.


Upgrading dosfstools past 3.0.1 caused an error code greater than 1, 
which triggers the stop of the boot process.


I don't understand why initscripts tries to fsck a non-existent device.

Maybe I should file a bug against initscripts.

I had initially filed a bug against dosfstools but had no response:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562536

I would just like to have USB flash drives that may or may not be 
plugged into machines that aren't switched on all the time, and I would 
like them to be mounted if they're plugged in when the machine is 
powered on, and for the machine to boot anyway if the USB flash drive is 
not present.


Regards,

Arthur.

Regards,

Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Frank McCormick wrote, on 03/02/10 02:11:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 15:00:41 + (UTC)
Camaleón  wrote:


On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:


Hi, I found that initscripts seems to attempt to run fsck on
non-existent devices that appear in /etc/fstab, and different fsck
programs for different filesystem types give different error
codes.

What is the easiest way to set up Debian to automatically mount
specific devices if they are present, but not cause a boot
failure when they are absent?

"man fstab" says that if the  digit is other than zero,
"fsck" will try to check that mount point.



   I have devices (usually flashdrives and or digital cameras) that
may or may not be present during boot and they don't cause boot
failure. But I guess you're talking about differnt devices ??


- -- 
Frank


I was just using a USB flashdrive formatted to vfat.

dosfstools 3.0.1 would have error code 1 for a drive entry in /etc/fstab 
 that wasn't plugged in and it would boot fine whether the USB drive 
was present or not.


If fsck returns with error code greater than 1, the boot process stops 
at a prompt to enter root password or control-d.


My argument is that the boot process should not even try to run fsck on 
a non-existent device.


Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 15:08:57 -0500, Frank McCormick wrote:

> On Tue, 02 Feb 2010 19:59:13 + (UTC) Camaleón wrote:

>> Question is, do you really need "those" devices (flash drives and MC/SD
>> memory cards) to be present in "fstab"? That is, do you need static
>> mount points for that kind of devices?
>> 
>> USB hard drives make sense, but for media cards I'd better let hotplug
>> subsystem auto-manages them.
> 
> 
>   In my particular case, yes. I like to know beforehand where they
> are mounted. AFAIK hotplug or its successor mounts them where it wants
> to ?

Mmm... I think "LABEL" would take precedence over another mount option 
(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it 
should be mounted when plugged under "/media/mylabel".

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 19:59:13 + (UTC)
Camaleón  wrote:

> On Tue, 02 Feb 2010 14:46:09 -0500, Frank McCormick wrote:
> 
> > To the OP:
> >
> > The bottom line: There is no problem even if flashdrives/cameras
> > etc are in fstab but not present- you simply get the error logged
> 
> Question is, do you really need "those" devices (flash drives and
> MC/SD memory cards) to be present in "fstab"? That is, do you need
> static mount points for that kind of devices?
> 
> USB hard drives make sense, but for media cards I'd better let
> hotplug subsystem auto-manages them.


  In my particular case, yes. I like to know beforehand where they
are mounted. AFAIK hotplug or its successor mounts them where it
wants to ?

Cheers
- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaIZZAAoJEMEDyLTvrVhjGMsIAI/JRvj7uRODArSlyIbfpYzN
D5dwoMKIpJz/8Q8kJGpz+Pk+gbnB9xFF7+B6ZNpnEtMUk3naL/xb/ReCntfUZ5o9
WkIRHB6yn4HSmUV76RnlLf7d4eRmd1GA59tHIyuMgJkiIufhqPIyGGDAVGBYqLBO
ctoSSA2XK/Bv29Q618gxRoX0FrkLhkJPz9rhdjjzOKpUlDZ+iQTodEym5Y9aaYC3
eLnlyqKn6Tg7ze8XzlCNy242nI8IhLXS13aGDgADHCNirzKD0saft4mGCWhVctVo
HL94eEti/+2kksHTe1yy4+yWepjwMh0UZLoeeK5uciMuadIa86wdvSa3AG/TA9Y=
=J/bJ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 14:46:09 -0500, Frank McCormick wrote:

> To the OP:
>
> The bottom line: There is no problem even if flashdrives/cameras etc are
> in fstab but not present- you simply get the error logged

Question is, do you really need "those" devices (flash drives and MC/SD 
memory cards) to be present in "fstab"? That is, do you need static mount 
points for that kind of devices?

USB hard drives make sense, but for media cards I'd better let hotplug 
subsystem auto-manages them.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 18:45:25 + (UTC)
Camaleón  wrote:

> On Tue, 02 Feb 2010 13:34:40 -0500, Frank McCormick wrote:
> 
> > On Tue, 02 Feb 2010 18:10:29 + (UTC) Camaleón wrote:
> 
> >> Uh? Didn't you say...? :-?
> >> 
> >> ***
> >> I found that initscripts seems to attempt to run fsck on
> >> non-existent devices that appear in /etc/fstab, and different
> >> fsck programs for different filesystem types give different
> >> error codes. ***
> > 
> >   No. I didn't say it.
> 
> Oops, sorry. You're right. That was the OP.

   No problem.

  Earlier you said:
> 
> >> If your USB disk is not always "on" and you want to prevent that
> >> warning, you can use de "noauto" option but you'll have to
> >> manually mount it when you plug it.


   Then I said :

>> No, it mounts automatically when I plug it in...I just want it
>> mounted automatically IF it's present during boot


To the OP:
   
The bottom line: There is no problem even if flashdrives/cameras etc
are in fstab but not present- you simply get the error logged


Cheers
- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaIEBAAoJEMEDyLTvrVhjhlYIAJJDTMlNpzFs48z96TuHOQfH
gWD6r6MoXnN6n0hu05pT8qi55tM7txZMS+6dQbvRf/frSa73mwLOJQ/qruBBmx2P
UHRLQN9b45psZ4o6BY/HVzgYq7px8ULw1dXMNMUOQ1TCTzay56LzSu26ff0OzMI0
8MaaGRdtNUMgOvi8ejIFqFVp5+UcJBa6Hu8N+h6oGUguBkBYobYxhDvBbEc6BjZW
iWQf4BI99zjEl/MRm77s+kgUNs+oOaT7mIAWIGFIJcaYHt6K4hukx5F/lTP5NiVu
c7Dp0DdZbDWHHKz++xd+WVozl1/ApogClUvv04Gjt5+fP/a9XRRHSvRdJZvm0FI=
=Ccni
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 13:34:40 -0500, Frank McCormick wrote:

> On Tue, 02 Feb 2010 18:10:29 + (UTC) Camaleón wrote:

>> Uh? Didn't you say...? :-?
>> 
>> ***
>> I found that initscripts seems to attempt to run fsck on non-existent
>> devices that appear in /etc/fstab, and different fsck programs for
>> different filesystem types give different error codes. ***
> 
>   No. I didn't say it.

Oops, sorry. You're right. That was the OP.

>> Any device or partition listed under fstab are "static" ones. If you
>> have defined a mount point that is not present at boot time, you will
>> get a warning, that is a normal behaviour.
>> 
>> If your USB disk is not always "on" and you want to prevent that
>> warning, you can use de "noauto" option but you'll have to manually
>> mount it when you plug it.
> 
>   No, it mounts automatically when I plug it in...I just want it
> mounted automatically IF it's present during boot

Then, why not just add it to "/etc/fstab"?

- If it's present, it will be mounted.
- If it's not available, it will be ignored and the warning logged.

Nothing wrong with that.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 18:10:29 + (UTC)
Camaleón  wrote:

> On Tue, 02 Feb 2010 12:31:56 -0500, Frank McCormick wrote:
> 
> > On Tue, 02 Feb 2010 16:12:56 + (UTC) Camaleón wrote:
> > 
> >> I.e., if your USB drive is listed there and you have something
> >> like:
> >> 
> >> #   #
> >> # 
> >> /dev/sdb1  /data/backupext3
> >> acl,user_xattr 1   2 ^
> >> 
> >> Then fsck will try to check that mount point, either is present
> >> or not (or at least that is my understanding after reading "man
> >> fstab") :-)
> > 
> > 
> >   That's not what happens in my case. The boot process simply
> > gives an error that the device does not exist. There is no
> > attempt to fsck the non-existant drive. I gather this is because
> > the system attempts to mount the non-existant drive.
> 
> Uh? Didn't you say...? :-?
> 
> ***
> I found that initscripts seems to attempt to run fsck on 
> non-existent devices that appear in /etc/fstab, and different fsck 
> programs for different filesystem types give different error codes.
> ***

  No. I didn't say it. 

  On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:

> Hi, I found that initscripts seems to attempt to run fsck on
> non-existent devices that appear in /etc/fstab, and different fsck
> programs for different filesystem types give different error codes.
> 
> What is the easiest way to set up Debian to automatically mount specific
> devices if they are present, but not cause a boot failure when they are
> absent?

  
> Any device or partition listed under fstab are "static" ones. If
> you have defined a mount point that is not present at boot time,
> you will get a warning, that is a normal behaviour.
> 
> If your USB disk is not always "on" and you want to prevent that
> warning, you can use de "noauto" option but you'll have to manually
> mount it when you plug it.

  No, it mounts automatically when I plug it in...I just want it
mounted automatically IF it's present during boot


- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaHBAAAoJEMEDyLTvrVhjtvEH/0w7WxGgk+oPOz2psIUaPozX
UKLnwtyVHXZWd97yighP2ASW2FzbWMJSWjqOFoiquOSoSs/wXtA2ohy4boSSAHSc
e7S4Z7QShRg8X5yNSMRTd1us1H2tklj57zW/pof/Dd36xGd515oWTdUwCMXJTnW6
hbWKhqutEuePbd+gLNXFJWIg24DbURHYqfsOzQwYOyDGUSXiJY8PFmHJTYHLyE6q
JGQ9KlKUgWbDCld0gRxs4XMjqUY+9Ey9J+LvqrcoLCYq8HVt2mG9fq1au4YX/qsl
fsFZwqTSezKudfVgVrNk8QFy9l4s2FqyBfeWlvLvSPiX2XCnHwhAE11J2pp5fA4=
=U65H
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 12:31:56 -0500, Frank McCormick wrote:

> On Tue, 02 Feb 2010 16:12:56 + (UTC) Camaleón wrote:
> 
>> I.e., if your USB drive is listed there and you have something like:
>> 
>> #   # 
>> /dev/sdb1/data/backupext3
>> acl,user_xattr   1   2 ^
>> 
>> Then fsck will try to check that mount point, either is present or not
>> (or at least that is my understanding after reading "man fstab") :-)
> 
> 
>   That's not what happens in my case. The boot process simply gives
> an error that the device does not exist. There is no attempt to fsck the
> non-existant drive. I gather this is because the system attempts to
> mount the non-existant drive.

Uh? Didn't you say...? :-?

***
I found that initscripts seems to attempt to run fsck on 
non-existent devices that appear in /etc/fstab, and different fsck 
programs for different filesystem types give different error codes.
***

O.k., let's start over.

Any device or partition listed under fstab are "static" ones. If you have 
defined a mount point that is not present at boot time, you will get a 
warning, that is a normal behaviour.

If your USB disk is not always "on" and you want to prevent that warning, 
you can use de "noauto" option but you'll have to manually mount it when 
you plug it.

Another possibility is just deleting (or comment) that entry in fstab and 
use the standard DE hotplug system (that will mount the unit under /media 
as soon as you turn it on).

Additional info:

http://wiki.debian.org/USBDrive

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 16:12:56 + (UTC)
Camaleón  wrote:

> On Tue, 02 Feb 2010 10:41:46 -0500, Frank McCormick wrote:
> 
> > On Tue, 02 Feb 2010 15:00:41 + (UTC) Camaleón wrote:
> > 
> >> > What is the easiest way to set up Debian to automatically mount
> >> > specific devices if they are present, but not cause a boot
> >> > failure when they are absent?
> >> 
> >> "man fstab" says that if the  digit is other than zero,
> >> "fsck" will try to check that mount point.
> > 
> > 
> >I have devices (usually flashdrives and or digital cameras)
> > that may or may not be present during boot and they don't cause
> > boot failure. But I guess you're talking about different devices ??
> 
> I mean devices listed as static mount points in "/etc/fstab".
> Usually, removable media (flash drivers and SD cards) are not
> listed there.
> 
> I.e., if your USB drive is listed there and you have something like:
> 
> #  
> # 
> /dev/sdb1 /data/backupext3
> acl,user_xattr1   2 ^
> 
> Then fsck will try to check that mount point, either is present or
> not (or at least that is my understanding after reading "man
> fstab") :-)


  That's not what happens in my case. The boot process simply gives
an error that the device does not exist. There is no attempt to
fsck the non-existant drive. I gather this is because the system
attempts to mount the non-existant drive.

> 
> If you want to avoid auto-checking at all for that specific mount
> point, you can put a "0" (zero) in the last column). You'll have to
> do the checking manually.


- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaGGMAAoJEMEDyLTvrVhjwBYH/1PcjiHtF24v4gm2dDS534CQ
UJ0H3PjBeIM1Pe2IYSc4s4DCNfCP4qzvign5obVlL/FX64O3CxlhmeZP6NTtDsil
UYn1yz4uThzsbql3/Cip6ZhoO5trG4bv38pvmGwW6RTjBzHysRSy5PYITLerITgv
f3+p1oM/3nhJUOfawAHU7DtOZ1eglJ/kp/N5ZO6W1XYO+JFqKOsuPTnIDq4yg04J
hYAdL+A1ZTgGgRWnZaPLHOJq9c2qu1SdaCfTkuArrYD47EjQcsNciwrcP7lD7cM0
TEtrtFt0L65sFoJkrwoCGML5zc0Ox+0f6kDDA2EBcG5wIJwlnGY/UPORmw0Vxbc=
=bQrr
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 10:41:46 -0500, Frank McCormick wrote:

> On Tue, 02 Feb 2010 15:00:41 + (UTC) Camaleón wrote:
> 
>> > What is the easiest way to set up Debian to automatically mount
>> > specific devices if they are present, but not cause a boot failure
>> > when they are absent?
>> 
>> "man fstab" says that if the  digit is other than zero, "fsck"
>> will try to check that mount point.
> 
> 
>I have devices (usually flashdrives and or digital cameras) that
> may or may not be present during boot and they don't cause boot failure.
> But I guess you're talking about differnt devices ??

I mean devices listed as static mount points in "/etc/fstab". Usually, 
removable media (flash drivers and SD cards) are not listed there.

I.e., if your USB drive is listed there and you have something like:

#
/dev/sdb1   /data/backupext3acl,user_xattr  1   2
^

Then fsck will try to check that mount point, either is present or not 
(or at least that is my understanding after reading "man fstab") :-)

If you want to avoid auto-checking at all for that specific mount point, 
you can put a "0" (zero) in the last column). You'll have to do the 
checking manually.

P.S. I suggest you to use LABEL or ID mount points for hard disk USB 
devices.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Feb 2010 15:00:41 + (UTC)
Camaleón  wrote:

> On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:
> 
> > Hi, I found that initscripts seems to attempt to run fsck on
> > non-existent devices that appear in /etc/fstab, and different fsck
> > programs for different filesystem types give different error
> > codes.
> > 
> > What is the easiest way to set up Debian to automatically mount
> > specific devices if they are present, but not cause a boot
> > failure when they are absent?
> 
> "man fstab" says that if the  digit is other than zero,
> "fsck" will try to check that mount point.


   I have devices (usually flashdrives and or digital cameras) that
may or may not be present during boot and they don't cause boot
failure. But I guess you're talking about differnt devices ??


- -- 
Frank
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLaEe6AAoJEMEDyLTvrVhj7uUH/1MPvgGpIlYep0pyaQIr7gAN
M8yO1cLsIpjBA/43I10TFeBIVxhIbifii+JN0iDvK/FUOn0SUoopXF9fSCkQR357
HbxvCwSGInSshFGxGt5vEf9c2a9agVqlc++6BxY2FaP6JmkiqHRim0i8D8iX7bMy
6pucIOUSnS+dLsD1EKwsaqJP83X8Z99JOuHfMh1fykBGzb0S4uDSX0aAl27k4gHr
T5orATLernss7V/gakPZ8haXTVhOYQJinnlI3quroipjx3Ji1yxIu1ygg4mA1hJQ
3A0gVs2TGKaDC/7mjWP3q54//OoNlUNqZapWMB0vyJYeO0FgRs4H51PJr7yc8FY=
=SBkh
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: auto-mounting disks that might not be present (e.g. usb drives)

[Camaleón]

On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:

> Hi, I found that initscripts seems to attempt to run fsck on
> non-existent devices that appear in /etc/fstab, and different fsck
> programs for different filesystem types give different error codes.
> 
> What is the easiest way to set up Debian to automatically mount specific
> devices if they are present, but not cause a boot failure when they are
> absent?

"man fstab" says that if the  digit is other than zero, "fsck" 
will try to check that mount point.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

auto-mounting disks that might not be present (e.g. usb drives)

[Arthur Marsh]

Hi, I found that initscripts seems to attempt to run fsck on 
non-existent devices that appear in /etc/fstab, and different fsck 
programs for different filesystem types give different error codes.


What is the easiest way to set up Debian to automatically mount specific 
devices if they are present, but not cause a boot failure when they are 
absent?


Arthur.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Changing fstab and re-mounting disks

[Damon L. Chesser]

Here is one I can not explain:  A user wanted to mount a vfat partition 
(/dev/hda4) to /mnt/hda4.  His fstab had this line in it:


/dev/hda4 /mnt/hda4 auto defualts,rw,users,owner,auto,uid=1000 0 0  
(uid=username ID). 

And yet, root:root owned all the files/dirs, that was to be expected, I 
think, and user could not mkdir or files, permission denied.  I had him 
change the fstab line to this:


/dev/hda4 /mnt/hda4 vfat defualts,rw,users,auto,suid=1000,umask=0 0 0  
(umask setting is a test, to test writing)


umount /dev/hda4 as root.  mount /dev/hda4 as user.  ls -l on hda4 
showed root:root owned all the files (drwxr-xr-x  14 root root )


Could not chown -R user:user /mnt/hda4/*  as root, "not allowed".  the 
user ran out of time (life gets in the way), but I found out a few hours 
latter he "fixed" the problem:  From a irc past:


(19:18:13) Dbarracuda: what was it?
(19:18:22) RABraker: the hell if i know  <<(19:18:58) RABraker: i mounted it in /media/hda4 and made arnold the 
owner of both
(19:19:25) RABraker: but it seemed to start working after changing the 
fstab and rebooting


so, here is the question:  What did I advise wrongly and why would not a 
umount, mount /dev/hda4 work?  We only wanted user to be the only one to 
access it.  Keep in mind, I really don't know what was finally changed 
during the above irc session, at this point in time, I only surmise that 
the changes I recommended were used.  I rarely play with vfat anymore, 
and obviously I am rusty.


--
Damon L. Chesser
[EMAIL PROTECTED]
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mounting disks

[Jan-Marek Glogowski]

Hi

When you get "Input/Output" error, there may be a hardware error :-(
Check your /var/log/messages.

You can check the partition layout using gpart.
http://www.stud.uni-hannover.de/user/76201/gpart/, or the deb.

Look at man e2fsck, especially -b, -B and -n.

HTH

Jan-Marek


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mounting disks

[Paul Morgan]

James Hosken wrote:

Quoting Paul Morgan <[EMAIL PROTECTED]>:

 

On Sat, 29 Nov 2003 11:46:13 +, James Hosken wrote:

   

Quoting Carl Fink <[EMAIL PROTECTED]>:

 

On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:

   

mount -t ext2 /dev/hdb5 /mnt/old-disk/

and I get the error

mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
  or too many mounted file systems
I'm pritty sure that it is the right file systems, I was using Mandrake
 

8.1
   

standard setup. I think the disk may be a bit dodgy. Is there any thing
 

that I
   

can do? I know there are several superblocks for this soer of thing.
 

Well, starting from the end:  how many filesystems do you have mounted?

Run fdisk or cfdisk on /dev/hdb and see what partition type /dev/hdb5
really is.
If it's ext2, run e2fsck on it.
   

Thanks for the reply, it is hdb8 that I'm really intrested in rather than
 

hdb5
   

Here's he result from fdisk

Disk /dev/hdb: 41.1 GB, 41174138880 bytes
255 heads, 63 sectors/track, 5005 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
  Device Boot  Start End  Blocks   Id  System
/dev/hdb1   * 117 510 3164805b  W95 FAT32
/dev/hdb2 511500536106087+   f  W95 Ext'd (LBA)
/dev/hdb5 511 573  506016   83  Linux
/dev/hdb6 574 604  248976   82  Linux swap
/dev/hdb7 605 986 3068383+  83  Linux
/dev/hdb8 987500532282586   83  Linux
Here is the result from fsck /dev/hdb8

fsck 1.35-WIP (21-Aug-2003)
e2fsck 1.35-WIP (21-Aug-2003)
fsck.ext2: Attempt to read block from filesystem resulted in short read
 

while tr
   

ying to open /dev/hdb8
Could this be a zero-length partition?


I have run fsck on hdb5 and hdb7 as well and they come back with the same
 

error.
   

Any surgestions?
Thanks
 

James,

What happens if you try to mount any of these without specifying a type? 
And, if mount is successful, what did it mount it as?

Example - what's the output from this?

mount /dev/hdb5 /mnt/old-disk/
mount | grep /mnt/old-disk
   



I have tried  that before, here the output

fork:/etc/apache# mount /dev/hdb5 /mnt/old-disk/
/dev/hdb5: Input/output error
mount: mount point /mnt/old-disk/ does not exist


I know that there are multiple superblock incase one gets knackered, would using
one of these help? How do I do that?
Is there a way of finding the superblocks?
James

 

James,

You must have mistakenly sent this to me rather than the list.

You could run mke2fs -n ... which would tell you where it would put the 
superblocks if it built the filesystem (-n tells it not to actually do 
it).  Then you could try giving one of those superblock values to mount. 
However, as it was built on a different system and we don't know the 
parameters mke2fs used to build it, there are no guarantees, but it's 
worth a try.  See "man mke2fs".

I assume that sfdisk thinks that your partition table is OK.  I mean, I 
assume that you are sure that the issue is the filesystem.

--
paul
"They made us many promises, more than I can remember, but they never
kept but one: they promised to take our land, and they took it."
- Chief Red Cloud (Mahpiua Luta) of the Oglala Sioux



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mounting disks

[Paul Morgan]

On Sat, 29 Nov 2003 11:46:13 +, James Hosken wrote:

> Quoting Carl Fink <[EMAIL PROTECTED]>:
> 
>> On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
>> 
>> > mount -t ext2 /dev/hdb5 /mnt/old-disk/
>> > 
>> > and I get the error
>> > 
>> > mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
>> >or too many mounted file systems
>> > I'm pritty sure that it is the right file systems, I was using Mandrake
>> 8.1
>> > standard setup. I think the disk may be a bit dodgy. Is there any thing
>> that I
>> > can do? I know there are several superblocks for this soer of thing.
>> 
>> Well, starting from the end:  how many filesystems do you have mounted?
>> 
>> Run fdisk or cfdisk on /dev/hdb and see what partition type /dev/hdb5
>> really is.
>> 
>> If it's ext2, run e2fsck on it.
> 
> 
> Thanks for the reply, it is hdb8 that I'm really intrested in rather than hdb5
> Here's he result from fdisk
> 
> Disk /dev/hdb: 41.1 GB, 41174138880 bytes
> 255 heads, 63 sectors/track, 5005 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>  
>Device Boot  Start End  Blocks   Id  System
> /dev/hdb1   * 117 510 3164805b  W95 FAT32
> /dev/hdb2 511500536106087+   f  W95 Ext'd (LBA)
> /dev/hdb5 511 573  506016   83  Linux
> /dev/hdb6 574 604  248976   82  Linux swap
> /dev/hdb7 605 986 3068383+  83  Linux
> /dev/hdb8 987500532282586   83  Linux
> 
> 
> Here is the result from fsck /dev/hdb8
> 
> fsck 1.35-WIP (21-Aug-2003)
> e2fsck 1.35-WIP (21-Aug-2003)
> fsck.ext2: Attempt to read block from filesystem resulted in short read while tr
> ying to open /dev/hdb8
> Could this be a zero-length partition?
> 
> 
> 
> I have run fsck on hdb5 and hdb7 as well and they come back with the same error.
> Any surgestions?
> Thanks

James,

What happens if you try to mount any of these without specifying a type? 
And, if mount is successful, what did it mount it as?

Example - what's the output from this?

mount /dev/hdb5 /mnt/old-disk/
mount | grep /mnt/old-disk

-- 
paul

"The average lifespan of a Web page today is 100 days. This is no way to
run a culture."

Internet Archive Board Chairman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mounting disks

[James Hosken]

Quoting Carl Fink <[EMAIL PROTECTED]>:

> On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
> 
> > mount -t ext2 /dev/hdb5 /mnt/old-disk/
> > 
> > and I get the error
> > 
> > mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
> >or too many mounted file systems
> > I'm pritty sure that it is the right file systems, I was using Mandrake
> 8.1
> > standard setup. I think the disk may be a bit dodgy. Is there any thing
> that I
> > can do? I know there are several superblocks for this soer of thing.
> 
> Well, starting from the end:  how many filesystems do you have mounted?
> 
> Run fdisk or cfdisk on /dev/hdb and see what partition type /dev/hdb5
> really is.
> 
> If it's ext2, run e2fsck on it.


Thanks for the reply, it is hdb8 that I'm really intrested in rather than hdb5
Here's he result from fdisk

Disk /dev/hdb: 41.1 GB, 41174138880 bytes
255 heads, 63 sectors/track, 5005 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device Boot  Start End  Blocks   Id  System
/dev/hdb1   * 117 510 3164805b  W95 FAT32
/dev/hdb2 511500536106087+   f  W95 Ext'd (LBA)
/dev/hdb5 511 573  506016   83  Linux
/dev/hdb6 574 604  248976   82  Linux swap
/dev/hdb7 605 986 3068383+  83  Linux
/dev/hdb8 987500532282586   83  Linux


Here is the result from fsck /dev/hdb8

fsck 1.35-WIP (21-Aug-2003)
e2fsck 1.35-WIP (21-Aug-2003)
fsck.ext2: Attempt to read block from filesystem resulted in short read while tr
ying to open /dev/hdb8
Could this be a zero-length partition?



I have run fsck on hdb5 and hdb7 as well and they come back with the same error.
Any surgestions?
Thanks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mounting disks

[Carl Fink]

On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:

> mount -t ext2 /dev/hdb5 /mnt/old-disk/
> 
> and I get the error
> 
> mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
>or too many mounted file systems
> I'm pritty sure that it is the right file systems, I was using Mandrake 8.1
> standard setup. I think the disk may be a bit dodgy. Is there any thing that I
> can do? I know there are several superblocks for this soer of thing.

Well, starting from the end:  how many filesystems do you have mounted?

Run fdisk or cfdisk on /dev/hdb and see what partition type /dev/hdb5
really is.

If it's ext2, run e2fsck on it.
--  
Carl Fink [EMAIL PROTECTED]
Jabootu's Minister of Proofreading
http://www.jabootu.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Mounting disks

[James Hosken]

I'm trying to mount a old disk with my /home and some other files.
I run the command

mount -t ext2 /dev/hdb5 /mnt/old-disk/

and I get the error

mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
   or too many mounted file systems
I'm pritty sure that it is the right file systems, I was using Mandrake 8.1
standard setup. I think the disk may be a bit dodgy. Is there any thing that I
can do? I know there are several superblocks for this soer of thing.

Help would be most appriciated at this dis does have all my data on it. I do
have a backup on CD, but it at my parents house several hundred miles away.

Thanks
James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]