1 |
On Friday 31 July 2015 13:53:42 Dale wrote: |
2 |
> Peter Humphrey wrote: |
3 |
> > Hello list, |
4 |
> > |
5 |
> > I've created a new btrfs volume on SSDs, complete with a lot of subvolumes |
6 |
> > corresponding to the old lvm2 logical volumes. I took the opportunity of |
7 |
> > removing a couple of old partitions, so I now have this: |
8 |
> > |
9 |
> > /dev/sd[ab]1 form /dev/md1 as /boot, |
10 |
> > /dev/sd[ab]2 are my rescue system: sda2 is its root, sdb2 is its portage |
11 |
> > tree, /dev/sd[ab]3 is the btrfs file system. |
12 |
> > |
13 |
> > I can boot my rescue system with no problems, but not the main system - I |
14 |
> > get a kernel panic with "BTRFS: failed to read the system array on sda3". |
15 |
> > I'm writing this after chroot, su - prh, startx. |
16 |
> > |
17 |
> > Both in the main and rescue systems I have this: |
18 |
> > $ grep -i btrfs /usr/src/linux/.config |
19 |
> > CONFIG_BTRFS_FS=y |
20 |
> > CONFIG_BTRFS_FS_POSIX_ACL=y |
21 |
> > # CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set |
22 |
> > # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set |
23 |
> > # CONFIG_BTRFS_DEBUG is not set |
24 |
> > # CONFIG_BTRFS_ASSERT is not set |
25 |
> > |
26 |
> > The relevant grub.cfg entries (I've moved to grub-2) are: |
27 |
> > |
28 |
> > menuentry 'Gentoo Linux 4.0.5, no network' { |
29 |
> > linux /boot/kernel-x86_64-4.0.5-gentoo root=/dev/sda3 |
30 |
> > softlevel=nonet |
31 |
> > net.ifnames=0 irqpoll |
32 |
> > } |
33 |
> > menuentry 'Rescue System 4.0.5' { |
34 |
> > linux /boot/kernel-x86_64-4.0.5-gentoo-rescue root=/dev/sda2 |
35 |
> > net.ifnames=0 irqpoll |
36 |
> > } |
37 |
> > |
38 |
> > Something seemed to be wrong in the kernel setup, so to test that I |
39 |
> > compiled the main kernel with the .config from the rescue system. Same |
40 |
> > result. |
41 |
> > |
42 |
> > Another test: I wondered whether, somehow, the btrfs volume included the |
43 |
> > name of the mount point where it had been created, and would only allow |
44 |
> > itself to be mounted there. Not so: moving its mount point in the rescue |
45 |
> > system didn't prevent it from being mounted. I didn't expect it would, |
46 |
> > since the kernel panic occurs long before fstab is read. |
47 |
|
48 |
--->8 |
49 |
|
50 |
> This may not be related but thought I would mention. For some reason, |
51 |
> my system will not boot a kernel newer than 3.18.7. I use |
52 |
> gentoo-sources and generally use make oldconfig. I have also tried the |
53 |
> new 4.0 kernels as well. They try to boot but don't make it past the |
54 |
> kernel trying to do its thing. I don't reboot often so I have not had |
55 |
> the chance to figure out exactly why this is happening. Recently I had |
56 |
> to start using that pesky init thingy but I don't think that is causing |
57 |
> the problem. I get a error/panic and then it says it is going to |
58 |
> reboot in 10 seconds. By the time I figure out where the failure might |
59 |
> be, it reboots itself. |
60 |
|
61 |
That could well be it, Dale. I tried both my currently installed kernels, |
62 |
3.18.16 and 4.0.5, but of course they're both later than 3.18.7. I'd still |
63 |
like to get this working, so I'll install an earlier kernel and try that - |
64 |
when I've had a bit of a rest! |
65 |
|
66 |
Thanks for the clue. |
67 |
|
68 |
-- |
69 |
Rgds |
70 |
Peter |