https://bugzilla.novell.com/show_bug.cgi?id=292963 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #151816|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c2 --- Comment #2 from Casual J. Programmer 2007-07-19 09:17:38 MST --- Created an attachment (id=151930) --> (https://bugzilla.novell.com/attachment.cgi?id=151930) the xorg.conf using driver=intel saved previously This same file I am using now, only with driver=i810 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c4 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #4 from Casual J. Programmer 2007-07-20 07:48:33 MST --- No, they simply don't belong here. This happens sometimes, when I don't realize, that bugzilla selects another bug in sequence when I activate commit. Sorry for causing confusion :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #151930|0 |1 is obsolete| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c6 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |casualprogrammer@yahoo.com --- Comment #6 from Casual J. Programmer 2007-07-21 07:14:59 MST --- How about last paragraph in Description, is this the same issue as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163461 ?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c8 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #8 from Andreas Jaeger 2007-08-03 05:27:49 MST --- Is the ieee1394 filesystem entered in /etc/fstab? Please show us /etc/fstab -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c10 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |hare@novell.com |screening@forge.provo.novell| |.com | --- Comment #10 from Andreas Jaeger 2007-08-03 08:02:19 MST --- You might have some udev rule waiting for it - Hannes, any ideas? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c11 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #11 from Hannes Reinecke 2007-08-06 00:49:12 MST --- Well, I wouldn't know. The fstab in comment #9 does not contain an entry for /var, whereas in the initial description it said: waiting for /dev/disk/by-id/ieee1394... blogd: no message logging because /var filesystem is not accessible fsck failed for at least one file system ( not / ) Please attach the correct fstab. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c13 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #13 from Hannes Reinecke 2007-08-06 05:38:12 MST ---

and mount point /external

Where did you configure this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c15 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |kasievers@novell.com --- Comment #15 from Hannes Reinecke 2007-08-06 08:40:58 MST --- Ah. Looks like a bug in the hal / udev setup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c17 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #17 from Casual J. Programmer 2007-08-12 01:24:46 MST --- Took a while till it happened again. Actually the root file system is not mounted because the ieee1394 drive isn't up, which sounds peculiar as it is removable and might not be available at boot time. So I am looking at the init ram disk _only_ here when typing ls /. This time it was obviously triggered by power loss to the system. After reconnecting the ieee1394 drive boot is normal again. Not sure how the boot process would know about a missing drive if the root file system is not mounted, but there should be a way to ignore that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c19 --- Comment #19 from Casual J. Programmer 2007-08-12 06:23:51 MST --- workstation6l:/home/antonyarendt # mkinitrd Kernel image: /boot/vmlinuz-2.6.22.1-16-default Initrd image: /boot/initrd-2.6.22.1-16-default Root device: /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 (/dev/sda4) (mounted on / as ext3) Resume device: /dev/sda3 Kernel Modules: processor thermal scsi_mod libata ata_piix ahci fan jbd mbcache ext3 edd sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid Features: block usb resume.userspace resume.kernel Bootsplash: SuSE (1024x768) 18305 blocks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c21 --- Comment #21 from Casual J. Programmer 2007-08-12 06:38:03 MST --- You are too quick :-) I just put the output here to save it, I did not remove NEEDINFO, though. After rebooting it still looks for the firewire drive, see screenshot. Alas a bit distorted, but readable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c23 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #23 from Kay Sievers 2007-08-12 06:47:42 MST --- Ah, ok. :) Weird, but seems it is the real root filesystem and boot.localfs is running. What does: grep /by-id/ /etc/* print? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c25 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #25 from Kay Sievers 2007-08-12 08:09:23 MST --- What does: mount -afnv print when you type it in the console when the boot fails? Does it print anything with the *by-id/* disk, which it seems to wait for? And also please provide: grep -r /by-id/ieee /etc That string must be stored somewhere. :) Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c27 --- Comment #27 from Kay Sievers 2007-08-12 08:59:02 MST --- So you added that disk in /etc/fstab.(In reply to comment #26 from Casual J. Programmer)

grep -r /by-id/ieee /etc /etc/fstab:/dev/disk/by-id/ieee1394-0001a30000000393:000428:0000-part1 /media/WS6L/Extern1 ext3 defaults 1 2

So, you added the device to /etc/fstab, and mark it as mandatory to exist on bootup. No wonder, that it fails. :) Or do you run software that edits fstab automatically? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c29 --- Comment #29 from Kay Sievers 2007-08-12 12:04:00 MST --- (In reply to comment #28 from Casual J. Programmer)

Actually I am doing nothing with fstab. Not sure what is going on here.

So you can confirm that adding and removing the disk changes your /etc/fstab? Can attach the output of: ps afx so we can see if there is a daemon running doing this?

Anyway, a device available thru plugging in or network connection should never be taken as mandatory for boot.

Sure, and nothing should ever touch fstab.

As far as I am concerned, only built in peripherals should be allowed to be mnadatory. The boot disk ( this got to be there, otherwise you wouldn't be booting - cogito, ergo sum - ), the keyboard and a monitor. The rest should not allow to stop the boot process, or else you won't be able to do much about the situation.

"Or do you run software that edits fstab automatically?" What would that be except for openSUSE ?

Nothing I know of, and if, it should be stopped doing that nonsense. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c31 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #31 from Kay Sievers 2007-08-12 15:40:13 MST --- Hmm, nothing suspicious. Can you confirm that repeated connect and disconnect of the disk changes /etc/fstab every time? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c33 --- Comment #33 from Kay Sievers 2007-08-12 16:35:40 MST --- You should specify: [Fstab options] -> [x] do not mount at system startup Unfortunately, there is no real support for setups like this. Usually hotpluggable drives are "user drives", mounted automatically to /media/, or you have "system drives" in fstab, which are automatically mounted, but required to be available at bootup time. You add an entry to fstab and mark it as "noauto", but then you have to mount it manually every time you want to use it. There is today no proper common solution for hotpluggable "system volumes" in Linux. We may solve that in the future, but not in the 10.3 timeframe. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c35 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |fehr@novell.com --- Comment #35 from Kay Sievers 2007-08-16 07:13:00 MST --- Adding a mountpoint for a disk with yast will by default create an entry in fstab, which makes the volume mandatory to exist at bootup. Users who add volumes here, will not be able to bootup if the drive doesn't exist. Yast could warn if the device is removable, or suggest a "noauto" setup. Not sure what's appropriate here. We also have a "nofail" option added to our mount, which will ignore missing volumes. But that patch is pending upstream, so can't be sure if that option will not be renamed for future releases, if upstream disagrees with the name. Thomas, what do you think? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c37 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Component|Basesystem |Hotplug Platform|x86 |All Summary|boot process interrupted |/etc/fstab hotpluggable device support - on- |when external ieee1394 disk |demand mounting, fstab option, yast setup |is not connected | --- Comment #37 from Kay Sievers 2007-08-16 08:46:32 MST --- It will probably be udev, but it's not implemented now. The "hotplug" option is gone from our mount (renamed to "nofail"), because "nofail" is expected to be available from upstream after the next util-linux release. I'll rename that bug, keep it open until we get that sorted out, and have the needed infrastructure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963#c38 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digiplan.pt@gmail.com --- Comment #38 from Kay Sievers 2007-11-08 00:33:25 MST --- *** Bug 338413 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=338413 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=292963 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=292963#c40 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #40 from Kay Sievers 2008-10-09 00:49:24 MDT --- We have: FSTAB_NAME=/dev/disk/by-id/scsi-SATA_ST910021AS_3450Y3KF-part6 FSTAB_DIR=/home/test/work FSTAB_TYPE=ext3 FSTAB_OPTS=acl,user_xattr,noatime,nodiratime in the event for a block device, which is listed in /etc/fstab. Current mount, supports a "nofail" option, in /etc/fstab, which will ignore non-existing volumes. Udev provides the infrastructure notify about new devices, and the matching entry from fstab comes with the event. Udev will not do such policy decisions, like, which volumes to automount, or how to fsck. Thats up to some other system configuration, service. Consider this as fixed from my side, everything else is a feature request, and should not be handled in bugzilla. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.