After # zpool import kirkwood, I could mount /sysroot and edit fstab. And
redsleeve came up just fine afterwords. Many thanks for your help. Can I ask
you another favour? Please help with uboot settings for multiboot I have Debian
8 on internal microsd and I want to boot first from sdb (1:1 Redsleeve). I’ll
send you the current uboot settings if you can help.
>
root@dreamplug ~]# uname -a
Linux dreamplug 3.10.92-4.el7.armv5tel #1 Thu Oct 29 10:26:32 GMT 2015 armv5tel
armv5tel armv5tel GNU/Linux
[root@dreamplug ~]#
> On Nov 3, 2015, at 10:56 PM, Gordan Bobic <[email protected]> wrote:
>
> Is zfs-fuse running? What do you get from:
>
> # zpool status
>
> and
>
> # zfs list
>
> If zpool status isn't showing any pools and zfs-fuse is running,
> do:
> # zpool import kirkwood
>
> then try again.
>
> Gordan
>
> On 2015-11-03 13:12, ioan stan wrote:
>> Please confirm this is the correct syntax. I cannot mount.
>> pre-mount:/# mount -t zfs kirkwood/ROOT /sysroot
>> filesystem 'kirkwood/ROOT' cannot be mounted, unable to open the
>> dataset
>>> On Nov 3, 2015, at 9:13 PM, Gordan Bobic <[email protected]>
>>> wrote:
>>> On 2015-11-03 11:57, ioan stan wrote:
>>>> Sysroot is empty
>>>> pre-mount:/# cd /sysroot
>>>> pre-mount:/sysroot# ls
>>>> zfs not there, I started it
>>>> pre-mount:/# ps auxw | grep zfs
>>>> root 168 0.0 0.1 2568 688 ttyS0 S+ 00:22 0:00 grep zfs
>>>> pre-mount:/# /sbin/zfs-fuse
>>>> @sbin/zfs-fuse: Warning: enabling xattr support should only be
>>>> done
>>>> when really required; perfod
>>>> pre-mount:/# zpool import
>>>> pool: kirkwood
>>>> id: 17312563881381185588
>>>> state: ONLINE
>>>> action: The pool can be imported using its name or numeric
>>>> identifier.
>>>> config:
>>>> kirkwood ONLINE
>>>> disk/by-id/usb-Generic_STORAGE_DEVICE_000000009910-0:1-part1
>>>> ONLINE
>>>> pre-mount:/#
>>> Hang on - is this what happens when you add "rd.break=pre-mount" to
>>> your boot parameters? If so, then that is normal, that will break
>>> out of the boot process before anything related to mounting the
>>> rootfs happens.
>>> Now that zfs-fuse is running, do:
>>> # mount -t zfs kirkwood/ROOT /sysroot
>>> # vi /sysroot/etc/fstab
>>> (edit it as discussed to fix the /boot device, in your case
>>> /dev/sdb4,
>>> or just comment it out to allow you to boot, you can edit fstab
>>> properly later)
>>> # reboot
>>> Remove rd.break=pre-mount from your boot parameters
>>>> saveenv
>>>> reset
>>> And you should be good to go.
>>> Gordan
>>> On Nov 3, 2015, at 8:37 PM, Gordan Bobic <[email protected]>
>>> wrote:
>>> On 2015-11-03 11:28, ioan stan wrote:
>>> Yes, get the “pre-mount” prompt, but fstab is empty as seen
>>> below.
>>> [ 9.635227] sd 1:0:0:1: [sdb] Write Protect is off
>>> [ 9.645244] sd 1:0:0:1: [sdb] No Caching mode page found
>>> [ 9.650639] sd 1:0:0:1: [sdb] Assuming drive cache: write through
>>> [ 9.659845] sd 1:0:0:0: [sda] No Caching mode page found
>>> [ 9.665206] sd 1:0:0:0: [sda] Assuming drive cache: write through
>>> [ 9.680219] sda: sda1 sda2 sda3 < sda5 >
>>> [ 9.691620] sd 1:0:0:1: [sdb] No Caching mode page found
>>> [ 9.697014] sd 1:0:0:1: [sdb] Assuming drive cache: write through
>>> [ 9.709711] sd 1:0:0:0: [sda] No Caching mode page found
>>> [ 9.715070] sd 1:0:0:0: [sda] Assuming drive cache: write through
>>> [ 9.721238] sd 1:0:0:0: [sda] Attached SCSI removable disk
>>> [ 9.727862] sdb: sdb1 sdb4
>>> [ 9.742965] sd 1:0:0:1: [sdb] No Caching mode page found
>>> [ 9.748357] sd 1:0:0:1: [sdb] Assuming drive cache: write through
>>> [ 9.754487] sd 1:0:0:1: [sdb] Attached SCSI removable disk
>>> pre-mount:/# ls /etc
>>> cmdline.d group ld.so.conf mtab sysctl.d
>>> conf.d hostid ld.so.conf.d os-release systemd
>>> e2fsck.conf hostname machine-id passwd udev
>>> fstab.empty initrd-release modprobe.d profile virc
>>> fuse.conf ld.so.cache modules-load.d sysctl.conf zfs
>>> pre-mount:/# cat /etc/fstab.empty
>>> pre-mount:/#
>>> Hmm... Something isn't right here. I just went through your log
>>> again and I don't see any reference to zfs-fuse being loaded.
>>> Can you check:
>>> # ps auxw | grep zfs
>>> There should be a process called @sbin/zfs-fuse running.
>>> Is there anything in /sysroot/ ?
>>> Do you have /sbin/zfs-fuse binary?
>>> If zfs-fuse daemon isn't running start it (/sbin/zfs-fuse)
>>> Then do:
>>> # zpool import
>>> That should show you what pools are available (there whould be
>>> one called kirkwood or dreamplug).
>>> Does it work when you _only_ have the RSEL rootfs USB device
>>> plugged in without any other USB devices (i.e. remove whatever
>>> is showing up as /dev/sda).
>>> Gordan
>>> On Nov 3, 2015, at 7:17 PM, Gordan Bobic <[email protected]>
>>> wrote:
>>> On 2015-11-03 03:12, ioan stan wrote:
>>> I was suspecting that fstab needs changes but I couldn't mount the
>>> root partition. Mount command would not work, how would I mount
>>> /dev/sdc1 to /mnt for editing? It seems zfs or zpool would help
>>> but
>>> not sure.
>>> You don't need to modify the image before inserting the card into
>>> the
>>> device. When the boot fails it will drop you to the diagnostic
>>> prompt. Look carefully, it was obscured in your pasted log by kernel
>>> messages from drivers still being loaded.
>>> Hit enter a couple of times and you'll see it. At that point the
>>> rootfs is already mounted and ready to go, just do:
>>> vi /etc/fstab and fix the problem (or comment out the line with
>>> /boot)
>>> then do "reboot" and it should come up OK. You can then fix fstab
>>> properly if you just commented out /boot.
>>> Another question, you're resizing partition with fdisk, parted
>>> would
>>> not work? I did find an article about resizing with fdisk
>>> https://access.redhat.com/articles/1190213
>>> <https://access.redhat.com/articles/1190213> [1] [1] [1] [2]
>>> I am less familiar with parted, I tend to use fdisk (for MBR) and
>>> gdisk (for GPT). If you are more familiar with parted, go for it,
>>> but bear in mind that uboot on *Plugs doesn't support GPT so it is
>>> essential you keep the partition table in MBR format or it won't
>>> work.
>>> Gordan
>>> _______________________________________________
>>> users mailing list
>>> [email protected] <mailto:[email protected]>
>>> https://lists.redsleeve.org/mailman/listinfo/users
>>> <https://lists.redsleeve.org/mailman/listinfo/users> [2]
>> Links:
>> ------
>> [1] https://access.redhat.com/articles/1190213
>> <https://access.redhat.com/articles/1190213> [1] [1]
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users> [2]
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users>
>> Links:
>> ------
>> [1] https://access.redhat.com/articles/1190213
>> <https://access.redhat.com/articles/1190213>
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users>
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users> [2]
>> Links:
>> ------
>> [1] https://access.redhat.com/articles/1190213
>> <https://access.redhat.com/articles/1190213>
>> [2] https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users>
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.redsleeve.org/mailman/listinfo/users
>> <https://lists.redsleeve.org/mailman/listinfo/users>
>
> _______________________________________________
> users mailing list
> [email protected] <mailto:[email protected]>
> https://lists.redsleeve.org/mailman/listinfo/users
> <https://lists.redsleeve.org/mailman/listinfo/users>
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
