Jc García wrote: > > 2014-03-16 8:24 GMT-06:00 Dale <rdalek1...@gmail.com > <mailto:rdalek1...@gmail.com>>: > > Howdy, > > I got this when rebooting after we had a power outage. I have a > UPS so > I was able to perform a regular shutdown. > > > [ 2.567061] hub 8-1:1.0: state 7 ports 4 chg 0000 evt 0000 > [ 2.567069] hub 8-1:1.0: hub_suspend > [ 2.579644] usb 8-1: usb auto-suspend, wakeup 1 > [ 2.591677] hub 8-0:1.0: hub_suspend > [ 2.591682] usb usb8: bus auto-suspend, wakeup 1 > [ 3.362374] dracut: root has been mounted 29 times without being > checked, check forced. > [ 3.363014] dracut: root: 28323/1525920 files (0.4% > non-contiguous), > 580665/6102684 blocks > [ 3.364957] dracut: Mounting > /dev/disk/by-uuid/888352dd-9c91-4a9f-9595-cd0e74b74ee7 with -o > defaults,ro > [ 3.474224] EXT4-fs (sda6): mounted filesystem with ordered data > mode. Opts: (null) > [ 3.522894] dracut: Mounted root filesystem /dev/sda6 > [ 3.568630] dracut: Mounting /usr with -o defaults,ro > [ 3.600028] dracut: mount: special device > /dev/disk/by-label/usr does > not exist > > > Seems like the block device for /usr couldn't be found by it's label, > root partition seems fine after check and properly mounted, so I'd say > it has nothing to do. > > > [ 3.601749] dracut Warning: Mounting /usr to /sysroot/usr failed > [ 3.602452] dracut Warning: *** Dropping you to a shell; the system > will continue > [ 3.603419] dracut Warning: *** when you leave the shell. > [ 3.604892] dracut Warning: > [ 3.849621] blkid (2070) used greatest stack depth: 4576 bytes left > + '[' -f /run/initramfs/init.log ']' > root@fireball / # > > > It seems to me that the / file system needed to be checked. For that > reason, it couldn't mount /usr after the check was performed. > That's my > thinking on this. Anyone think otherwise? Is this a one off event or > should I be concerned about this? > > > Is the block device corresponding to /usr available under another > directory in /dev? if not something wrong might be going on with that > block device. > I personally prefer using UUIDs for finding partitions at boot, they > are more fail-proof.
Well, after that, it booted fine. I forgot to mention that it did boot without me doing anything but letting it proceed. I *think* I typed exit or something to get it to keep going. > > Is there some way to avoid this in the future without disabling file > system check for /? > > > Again, maybe UUIDs. I tried that once and grub didn't like it. May need to see if things have improved in that area since. > > Another related LVM question. I have some partitions on LVM. If I > moved the drives to another system, would the new LVMs be found on the > new system or is there some magic involved to find and get them > mounted? Example. My /home is on its own LVM partition. If I moved > the drive that has that on it, would the new system see it or would I > have to do something to make it see it? I suspect and wouldn't > want it > to mount automatically. I'd just want to be able to see it and > mount it > if needed. Sort of a question I have always wondered about. > > > > On my experience as long, as udev and lvm are running on the receiving > system, they should be found and placed for access under /dev, not > mounted automatically. > if for some reason it doesnt happen, its easy to do a 'pvscan' to see > if the physical volume is recognized, and if it is, 'vgchange -ay > volume_group_name ' activates all LVs. > > > Thanks much. > > Dale > > :-) :-) > That's my thinking to but I have never had the chance to test it. I figured the info is stored on the drive and moves wherever the drives goes as long as LVM is running. Thanks much. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
