Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
Hi, "Udo Grabowski (IMK)"írta 2017-09-08 17:39-kor: > On 08/09/2017 17:33, Apostolos Syropoulos via openindiana-discuss wrote: > >>I should mind my p's and s's. Thanks, Andrew; you're right. I was > >>thinking of s2, not p2. > > > >So what I did what correct, right? I have mounted both partitions and the > >dataare there and I can read and write. > > No. Your boot slice #8 is overlapped by s2. It is not > recommended to use s2 for anything. > > Configure s0 instead with tag root, and use only the region > above the boot slice (that is, from cylinder 1 upwards). I don't think he configured any slice by hand. It was zpool what prepared the whole stuff. And there is NO overlap here. As it was already told: s2 (NOT p2) means the whole "drive"/ "partition". Depends on the case. Everything is right. No need to scare him away. Regards, Gyu ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
On 08/09/2017 17:33, Apostolos Syropoulos via openindiana-discuss wrote: I should mind my p's and s's. Thanks, Andrew; you're right. I was thinking of s2, not p2. So what I did what correct, right? I have mounted both partitions and the dataare there and I can read and write. No. Your boot slice #8 is overlapped by s2. It is not recommended to use s2 for anything. Configure s0 instead with tag root, and use only the region above the boot slice (that is, from cylinder 1 upwards). -- Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT http://www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
>I should mind my p's and s's. Thanks, Andrew; you're right. I was >thinking of s2, not p2. So what I did what correct, right? I have mounted both partitions and the dataare there and I can read and write. A.S. -- Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
On 09/08/17 10:45, Andrew Gabriel wrote: > On x86, p0 is the whole disk, and p1-4 are the 4 primary FDISK partitions. I should mind my p's and s's. Thanks, Andrew; you're right. I was thinking of s2, not p2. -- James Carlson 42.703N 71.076W___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
On 08/09/2017 14:44, James Carlson via openindiana-discuss wrote: On 09/07/17 16:50, Apostolos Syropoulos via openindiana-discuss wrote: Ok, but what is the problem? What is the output and stderr of your zpool create cXtYdZp2 command? Does it gives any error? After more searching I concluded that the command should be # zpool create -f utank c13t0d0s2 The logical Node was /dev/rdsk/c13t0d0p0and format --> partition --> print showed that slice 2 is the one where I can store data. I have also used fdisk to delete all partitions and thenparted to create the NTFS partition. In order to create thefile system I have used # zfs create utank/External #chown -R user:group /utank/External Now I can use the partition! p2 is, by convention, "whole disk" when using old-style partitioning. If you're using that and you've partitioned the disk, I think you've trashed your NTFS partition or (worse) you have an overlap. Are you sure? What exactly does "format" say about the partition map? Um... On x86, p0 is the whole disk, and p1-4 are the 4 primary FDISK partitions. s0-15 are slices in the Solaris FDISK partition, with s2 by convention being the whole Solaris FDISK partition, overlapping all the other slices in the Solaris FDISK partition. On SPARC, there is no FDISK partitioning. s0-7 are slices on the disk, and s2 is the whole disk by convention, overlapping all other slices on the disk. -- Andrew ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
>p2 is, by convention, "whole disk" when using old-style partitioning. >If you're using that and you've partitioned the disk, I think you've >trashed your NTFS partition or (worse) you have an overlap. > >Are you sure? What exactly does "format" say about the partition map? This is what fdisk says about the disk: Cylinders Partition Status Type Start End Length % = == = === == === 1 Active IFS: NTFS 0 45600 45601 75 2 Solaris2 45600 60191 14592 24 and this is what the partition item of format says: partition> p Current partition table (original): Total disk cylinders available: 14590 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned wm 0 0 (0/0/0) 0 2 backup wu 0 - 14589 447.06GB (14590/0/0) 937553400 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 8 boot wu 0 - 0 31.38MB (1/0/0) 64260 9 unassigned wm 0 0 (0/0/0) 0 A.S. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool on the second partition of an external disk
On 09/07/17 16:50, Apostolos Syropoulos via openindiana-discuss wrote: > >> Ok, but what is the problem? >> What is the output and stderr of your zpool create cXtYdZp2 command? >> Does it gives any error? > > After more searching I concluded that the command should be > # zpool create -f utank c13t0d0s2 > > The logical Node was /dev/rdsk/c13t0d0p0and format --> partition --> print > showed that slice 2 is the one where I can store data. > I have also used fdisk to delete all partitions and thenparted to create the > NTFS partition. In order to create thefile system I have used > # zfs create utank/External #chown -R user:group /utank/External > > Now I can use the partition! p2 is, by convention, "whole disk" when using old-style partitioning. If you're using that and you've partitioned the disk, I think you've trashed your NTFS partition or (worse) you have an overlap. Are you sure? What exactly does "format" say about the partition map? -- James Carlson 42.703N 71.076W___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] No rootfs module provided
I just put together a system with a ASUS B350M-A system board, an AMD Ryzen 3 1200 CPU and an ASUS HD 6450 Silent video card. When I attempt to boot the OI-hipster-gui-20170502 DVD on this system, I get the boot menu normally, but it's followed by these three lines: Loading unix... Loading /platform/186pc/amd64/boot_archive... Loading /platform/186pc/amd64/boot_archive.hash... Booting... No rootfs module provided, aborting What's missing? Is it in illumos yet? The OI-hipster-gui-20160421 DVD gives me the GRUB menu, but hangs part way through the parade of dots. I presume this is an example of the short read problem. The sol-11_3-live-x86 gives me the GRUB menu, the console messages, and the GUI. When I ran the device driver utility, it stopped at CPU. I presume that's because it doesn't have a CPU driver. I'm considering my options. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what to expect setting timeslider to `all'
Harry Putnamwrites: > Alexander Pyhalov writes: > > [...] > > Harry wrote: This is happening on a recently updated (about 170825 or so) hipster OS. So if an old bug has recurred somehow, one would think it would be getting reported by others on this list. > > Dave M responded: >>> If hipster is still using old time-slider tarballs from the >>> OpenSolaris days then it's probably never been fixed and others >>> aren't reporting it for whatever reason. In a lot of situations >>> it's benign as data is more in the leaf datasets than intermediate. >>> > > Alexander P responded: >> Yes, seems to be an issue in our time-slider. >> Harry, can you create an issue in the bug tracker >> (http://bugs.openindiana.org/)? > > Yes, I will get that done. [Just a note hoping to head off any confusion] I'm sorry to say I made a bit of a mess of it. It was my first time using the bug tracker. It appears I got a bit rambunctious with the copy/paste and managed to duplicate the information twice on the bug writeup. The salient points are readable enough even if needlessly repeated twice. But, worse I also managed to end up creating 2 identical bug reports. On separate numbers. Once I saw what I had done I did not see a way to remove the duplicate or flag it or whatever, so quit before bungling something else up. end result identical bug reports #8637 and #8638 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss