Re: [opensuse] fstab Drives Listed by id

At 03:46 PM 5/22/2008, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



El 2008-05-22 a las 14:35 -0700, William Hammond escribió:

You forgot to email to the list.

Sorry bout that....



> I can't create a Bare Metal Disaster Recovery CD.
> > fstab records the Drives listed by ID > "/dev/disk/by-id/SCSI-SSEAGATE_ST........"
> > So if a new drive is encountered it can't be mounted.
Why not?


I didn't quite follow this comment. Is it or is it not okay to edit the fstab manually.

Of course it is ok, I do it all the time. I meant that I don't understand why you say a new drive can not be mounted manually.

Not manually, the Disaster Recovery Software fails, I assume because the drive id for the new drive doesn't match fstab..
I'm working with them on that issue. I thought that if I could modify the fstab to match 10.2 the process would be less
complicated. The list by id seems to be new in 10.3, I'm not sure if that is better or just complicates.


I can imagine a scenario where booting up is no longer possible without further repair.

I also wonder why you would want to list by id in first place... Seems like replacing a hard drive becomes quite difficult...?

Because the names like hda, sda... can change, some even on the boot order. They are no longer stable, unfortunately, so they switched to that scheme. I prefer mounting "by-label". You have several choices:

cer@nimrodel:~> ls /dev/disk/
by-id by-label by-path by-uuid

and all of them are symlinks to the physical devices (sda, etc).

- -- Saludos
Carlos E.R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFINffgtTMYHG2NR9URAimjAJ4mEWIEhrICGiE6U80+lBaP1LqsPACfd7AU
tk/nVeOF6zoQxP290y4Tgqg=
=bkX7
-----END PGP SIGNATURE-----

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: [opensuse] umount automounted media
    ... Thanks Carlos, for the moment this a good solution. ... I think the problem is in the umount facility, it do's some checks for uid and fstab first, this is not relevant for usermounted devices. ... The automounter does not use the traditional method with fstab, so umount does not work. ...
    (SuSE)
  • Re: [opensuse] ReiserFS partitions recognized as Ext3. How to recover? - Definitely a bug
    ... On Sun, Feb 7, 2010 at 4:48 PM, Carlos E. R. ... And indeed all other computers I was using were reiserfs. ... Then I filled the fstab from ... Ie, it is and was a reiserfs partition, but mount wrongly reported that it was ext3. ...
    (SuSE)
  • Re: [opensuse] Mounting drives at boot
    ... On 07/03/11 23:29, Carlos E. R. wrote: ... the problem is the partition that they're located on isn't mounting at boot, even though nothing has changed in fstab etc. ... I installed/reinstalled Dropbox the other day, and have only just realised that it has edited my fstab file, remarking out the original line for the loading of my home directory, and sticking it at the VERY BOTTOM of the file, with an extra user_xattr setting. ...
    (SuSE)
  • Re: [opensuse] Mounting cdrecorder
    ... Carlos E. R. wrote: ... but how could subfs in my fstab when I upgrade 10.0 to 10.1? ... I was wondering how it's possible that 'subfs' could appear in the file fstab during upgrading from 10.0 to 10.1 when it does not exist in 10.1 ...
    (SuSE)
  • Re: [opensuse] Bugs? in SuSE11 or fundamental linux flaws? file bug(s)
    ... script, so perhaps the query is doable. ... Thanx Carlos ... I haven't tried, one only remembers these things when the system fails to boot because a partition is not there, and I have to edit the fstab right there. ...
    (SuSE)