1 |
Jc García wrote: |
2 |
> |
3 |
> 2014-03-16 8:24 GMT-06:00 Dale <rdalek1967@×××××.com |
4 |
> <mailto:rdalek1967@×××××.com>>: |
5 |
> |
6 |
> Howdy, |
7 |
> |
8 |
> I got this when rebooting after we had a power outage. I have a |
9 |
> UPS so |
10 |
> I was able to perform a regular shutdown. |
11 |
> |
12 |
> |
13 |
> [ 2.567061] hub 8-1:1.0: state 7 ports 4 chg 0000 evt 0000 |
14 |
> [ 2.567069] hub 8-1:1.0: hub_suspend |
15 |
> [ 2.579644] usb 8-1: usb auto-suspend, wakeup 1 |
16 |
> [ 2.591677] hub 8-0:1.0: hub_suspend |
17 |
> [ 2.591682] usb usb8: bus auto-suspend, wakeup 1 |
18 |
> [ 3.362374] dracut: root has been mounted 29 times without being |
19 |
> checked, check forced. |
20 |
> [ 3.363014] dracut: root: 28323/1525920 files (0.4% |
21 |
> non-contiguous), |
22 |
> 580665/6102684 blocks |
23 |
> [ 3.364957] dracut: Mounting |
24 |
> /dev/disk/by-uuid/888352dd-9c91-4a9f-9595-cd0e74b74ee7 with -o |
25 |
> defaults,ro |
26 |
> [ 3.474224] EXT4-fs (sda6): mounted filesystem with ordered data |
27 |
> mode. Opts: (null) |
28 |
> [ 3.522894] dracut: Mounted root filesystem /dev/sda6 |
29 |
> [ 3.568630] dracut: Mounting /usr with -o defaults,ro |
30 |
> [ 3.600028] dracut: mount: special device |
31 |
> /dev/disk/by-label/usr does |
32 |
> not exist |
33 |
> |
34 |
> |
35 |
> Seems like the block device for /usr couldn't be found by it's label, |
36 |
> root partition seems fine after check and properly mounted, so I'd say |
37 |
> it has nothing to do. |
38 |
> |
39 |
> |
40 |
> [ 3.601749] dracut Warning: Mounting /usr to /sysroot/usr failed |
41 |
> [ 3.602452] dracut Warning: *** Dropping you to a shell; the system |
42 |
> will continue |
43 |
> [ 3.603419] dracut Warning: *** when you leave the shell. |
44 |
> [ 3.604892] dracut Warning: |
45 |
> [ 3.849621] blkid (2070) used greatest stack depth: 4576 bytes left |
46 |
> + '[' -f /run/initramfs/init.log ']' |
47 |
> root@fireball / # |
48 |
> |
49 |
> |
50 |
> It seems to me that the / file system needed to be checked. For that |
51 |
> reason, it couldn't mount /usr after the check was performed. |
52 |
> That's my |
53 |
> thinking on this. Anyone think otherwise? Is this a one off event or |
54 |
> should I be concerned about this? |
55 |
> |
56 |
> |
57 |
> Is the block device corresponding to /usr available under another |
58 |
> directory in /dev? if not something wrong might be going on with that |
59 |
> block device. |
60 |
> I personally prefer using UUIDs for finding partitions at boot, they |
61 |
> are more fail-proof. |
62 |
|
63 |
Well, after that, it booted fine. I forgot to mention that it did boot |
64 |
without me doing anything but letting it proceed. I *think* I typed |
65 |
exit or something to get it to keep going. |
66 |
|
67 |
|
68 |
> |
69 |
> Is there some way to avoid this in the future without disabling file |
70 |
> system check for /? |
71 |
> |
72 |
> |
73 |
> Again, maybe UUIDs. |
74 |
|
75 |
I tried that once and grub didn't like it. May need to see if things |
76 |
have improved in that area since. |
77 |
|
78 |
|
79 |
> |
80 |
> Another related LVM question. I have some partitions on LVM. If I |
81 |
> moved the drives to another system, would the new LVMs be found on the |
82 |
> new system or is there some magic involved to find and get them |
83 |
> mounted? Example. My /home is on its own LVM partition. If I moved |
84 |
> the drive that has that on it, would the new system see it or would I |
85 |
> have to do something to make it see it? I suspect and wouldn't |
86 |
> want it |
87 |
> to mount automatically. I'd just want to be able to see it and |
88 |
> mount it |
89 |
> if needed. Sort of a question I have always wondered about. |
90 |
> |
91 |
> |
92 |
> |
93 |
> On my experience as long, as udev and lvm are running on the receiving |
94 |
> system, they should be found and placed for access under /dev, not |
95 |
> mounted automatically. |
96 |
> if for some reason it doesnt happen, its easy to do a 'pvscan' to see |
97 |
> if the physical volume is recognized, and if it is, 'vgchange -ay |
98 |
> volume_group_name ' activates all LVs. |
99 |
> |
100 |
> |
101 |
> Thanks much. |
102 |
> |
103 |
> Dale |
104 |
> |
105 |
> :-) :-) |
106 |
> |
107 |
|
108 |
That's my thinking to but I have never had the chance to test it. I |
109 |
figured the info is stored on the drive and moves wherever the drives |
110 |
goes as long as LVM is running. |
111 |
|
112 |
Thanks much. |
113 |
|
114 |
Dale |
115 |
|
116 |
:-) :-) |
117 |
|
118 |
-- |
119 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |