[Bug 292963] New: boot process interrupted when external ieee1394 disk is not connected
https://bugzilla.novell.com/show_bug.cgi?id=292963 Summary: boot process interrupted when external ieee1394 disk is not connected Product: openSUSE 10.3 Version: Alpha 5plus Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: qa@suse.de Found By: Beta-Customer Created an attachment (id=151816) --> (https://bugzilla.novell.com/attachment.cgi?id=151816) /var/log/boot.msg On an FSC Amilo Si1520 running openSuSE 10.3 alpha5plus after connecting an external disk on the firewire port works fine. Only when the system is started without the drive being connected, the boot process terminates prematurely, even if the drive has been unmounted before shutting down the system. The display shows: 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 / ) Alas no information on this is found in boot.log ( empty file) or boot.msg ( contains a lot of shell script source information, maybe a bug in its own right, see attachment ) -- 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 <casualprogrammer@yahoo.com> 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#c1 --- Comment #1 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-07-19 09:16:11 MST --- Created an attachment (id=151929) --> (https://bugzilla.novell.com/attachment.cgi?id=151929) the xorg.conf generated by sax2 when I first reported this bug -- 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 <casualprogrammer@yahoo.com> 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#c3 Matej Horvath <mhorvath@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #3 from Matej Horvath <mhorvath@novell.com> 2007-07-20 07:04:55 MST --- Could you please explain the two xorg.conf files? I don't see any connection to the ieee1394 disk issue. -- 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 <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #4 from Casual J. Programmer <casualprogrammer@yahoo.com> 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 <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #151929|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 Casual J. Programmer <casualprogrammer@yahoo.com> 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#c5 --- Comment #5 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-07-20 07:50:41 MST --- Likewise comments #1 and #2 -- 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 <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |casualprogrammer@yahoo.com --- Comment #6 from Casual J. Programmer <casualprogrammer@yahoo.com> 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#c7 --- Comment #7 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-07-21 07:16:15 MST --- OK, bugzilla doesn't like "Description" rather Comment #0 -- 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 <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #8 from Andreas Jaeger <aj@novell.com> 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#c9 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #9 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-03 07:11:39 MST --- Created an attachment (id=155473) --> (https://bugzilla.novell.com/attachment.cgi?id=155473) /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 <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |hare@novell.com |screening@forge.provo.novell| |.com | --- Comment #10 from Andreas Jaeger <aj@novell.com> 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 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #155473|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#c11 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #11 from Hannes Reinecke <hare@novell.com> 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#c12 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #12 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-06 05:14:17 MST --- Not sure where we stand here, I only have _one_ fstab. The disk is an external drive which was formatted NTFS initially, I reformatted it to ext3 and mount point /external. As it was inaccessible for users, I created some directories as root for several users. This was the state of affairs when it would not boot without the drive. After unmounting it and removing it while system up, it would then automount on plug in and the initial effect did not occur anymore, as I didn't have to mount the drive manually. -- 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 <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #13 from Hannes Reinecke <hare@novell.com> 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#c14 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #14 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-06 05:44:21 MST --- /sbin/yast2 disk -- 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 <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |kasievers@novell.com --- Comment #15 from Hannes Reinecke <hare@novell.com> 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#c16 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #16 from Kay Sievers <kasievers@novell.com> 2007-08-06 08:54:55 MST --- Nothing in udev mounts devices without an fstab entry marked as "hotplug", even that feature is removed from the 10.3 betas. HAL doesn't touch anything which is in fstab, nor does it mount anything outside of /media. The bug description looks like a completely broken initramfs. Please run mkinitrd without the disk attached and reboot. -- 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 <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #17 from Casual J. Programmer <casualprogrammer@yahoo.com> 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#c18 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #18 from Kay Sievers <kasievers@novell.com> 2007-08-12 06:17:56 MST --- Again, please provide the requested information from #16, and run mkinitrd while the drive is disconnected and try again. -- 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 <casualprogrammer@yahoo.com> 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#c20 --- Comment #20 from Kay Sievers <kasievers@novell.com> 2007-08-12 06:26:22 MST --- Oh, I don't need the output, I need to know if it still looks for the firewire disk at bootup. So please reboot. :) -- 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 <casualprogrammer@yahoo.com> 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#c22 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #22 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 06:40:29 MST --- Created an attachment (id=156948) --> (https://bugzilla.novell.com/attachment.cgi?id=156948) Screenshot of situation -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #23 from Kay Sievers <kasievers@novell.com> 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#c24 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #24 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 07:11:37 MST --- grep /by-id/ /etc/* /etc/fstab:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 / ext3 acl,user_xattr 1 1 /etc/fstab:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 /windows/C ntfs-3g users,gid=users,umask=0002,nls=utf8,locale=en_US.UTF-8 0 0 /etc/fstab:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 /windows/D ntfs-3g users,gid=users,umask=0002,nls=utf8,locale=en_US.UTF-8 0 0 /etc/fstab:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part3 swap swap defaults 0 0 /etc/fstab.bak:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 / ext3 acl,user_xattr 1 1 /etc/fstab.bak:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 /windows/C ntfs-3g users,gid=users,umask=0002,nls=utf8,locale=en_US.UTF-8 0 0 /etc/fstab.bak:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 /windows/D ntfs-3g users,gid=users,umask=0002,nls=utf8,locale=en_US.UTF-8 0 0 /etc/fstab.bak:/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part3 swap swap defaults 0 0 -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #25 from Kay Sievers <kasievers@novell.com> 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#c26 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #26 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 08:53:49 MST --- OK, mount -afnv tells me twice ntfs-3g 1.710 . . . unknown option -f then proc on /proc type devpts /dev/disk/by-id/ieee1394-0001a30000000393:000428:0000-part1 grep -r /by-id/ieee /etc /etc/fstab:/dev/disk/by-id/ieee1394-0001a30000000393:000428:0000-part1 /media/WS6L/Extern1 ext3 defaults 1 2 repeating mount -afnv after booting results in mount -afnv mount: /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 already mounted on /windows/C mount: /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 already mounted on /windows/D mount: proc already mounted on /proc mount: devpts already mounted on /dev/pts mount: /dev/disk/by-id/ieee1394-0001a30000000393:000428:0000-part1 already mounted on /media/WS6L/Extern1 -- 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 <kasievers@novell.com> 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#c28 --- Comment #28 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 11:54:22 MST --- Actually I am doing nothing with fstab. Not sure what is going on here. Anyway, a device available thru plugging in or network connection should never be taken as mandatory for boot. 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 ? -- 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 <kasievers@novell.com> 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#c30 --- Comment #30 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 14:43:52 MST --- Created an attachment (id=156976) --> (https://bugzilla.novell.com/attachment.cgi?id=156976) output of ps afx -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #31 from Kay Sievers <kasievers@novell.com> 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#c32 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #32 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 16:11:23 MST --- As explained in comment #12 this drive was NTFS, I then formatted it to ext3 with yast2 disk and gave it a mount point. Come to think of it, it happens every time I set the mount point manually with yast2 disk. As I currently don't see another way to format and mount a fresh firewire disk, this should _not_ behave as described. Since this is a hotplug/hotunplug device it should _never_ be made mandatory for boot. As far as the research goes, this is my only candidate for this weird behaviour. I can actually cure it by manually removing the fstab entry as well as the mount point, I think this is well beyond a normal users capacities. -- 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 <kasievers@novell.com> 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#c34 --- Comment #34 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-08-12 22:38:29 MST --- Thanks for taking the time to explain :-) Maybe you could at least arrange for the boot process not being stopped prematurely in such cases. I think most users coming from Windows will find it more than frustrating being asked for the root password at a CLI before they see any graphical desktop. -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |fehr@novell.com --- Comment #35 from Kay Sievers <kasievers@novell.com> 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#c36 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|fehr@novell.com | --- Comment #36 from Thomas Fehr <fehr@novell.com> 2007-08-16 07:44:02 MST --- Seems like the same problem like in bug #250667 for iscsi volumes. Solution there was to add the "hotplug" option to fstab options by YaST2. This at least prevents boot process from being halted. I have no idea which instance in the system is responsible for mounting such a disk when it gets available later. There is no problem to have such options like "noauto" and "hotplug" automatically set by YaST2 but of course someone needs to tell me when exactly this needs to be done. -- 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 <kasievers@novell.com> 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 <kasievers@novell.com> 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 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digiplan.pt@gmail.com --- Comment #38 from Kay Sievers <kasievers@novell.com> 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 eike.welk@post.rwth-aachen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=292963#c39 eike welk <eike.welk@post.rwth-aachen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eike.welk@post.rwth-aachen.de --- Comment #39 from eike welk <eike.welk@post.rwth-aachen.de> 2008-08-14 12:16:12 MDT --- I vote for this bug! I think the boot scripts should be modified so that booting continues when disks are missing. I had a similar problem where removing a SATA disk would prevent the system from booting completely. It booted into some maintenance mode. The removed drive did not contain any files necessary for bringing the system up. Real world use cases: - A data disk is moved to an other server. - A data disk fails. The system might now not boot although the system disk works. -- Additionally Yast should be able to remove partitions from the fstab without damaging the partitions themselves. -- 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 <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #40 from Kay Sievers <kasievers@novell.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com