Re: Fedora 24 and PNY SSD Problems

[Gregory P. Ennis]

On Sun, Jul 17, 2016 at 08:45:13AM -0500, Gregory P. Ennis wrote:
> 
> Everyone,
> 
> I am trying to reclaim some use out of a couple old Compaq Presaio
> SR1720NX machines for the office by adding some memory and a PNY 240
> GB
> CS1311 SSD drives.  The bios was made by Phoenix; I did not identify
> a
> version number of the bios.  I did not plan on keep the hard drive
> installed and planned on just using the SSD.  These machines were IDE
> machines and only had two SATA ports on the motherboard.  
> 
> When I install the SSD the bios recognizes the Pny SSD properly, and
> I
> was able to set up the boot order without difficulty.
> 
When I had to replace the MB of a similar, older system, I used a non-
HP MB.
Later when I wanted to beef it up, the new MB only had 2 SATA ports and
I wanted to install more drives.  So I purchased a really cheap SATA
controller card.

I got a store-brand SSD and to my surprise the MB controller did not
see it but the cheap controller did.  Blaming the store-brand SSD,
I returned it and got a Crucial SSD.  Same problem though.  So it
was the controller, not the SSD.  MB controller worked fine with
other SATA drives, but not with the SSD.

Jon
---
Jon,

That is helpful.  I have tried everything I could think of as well as
read on the internet.  So far nothing is working.  I think a cheap SATA
controller card is my next step.

Greg

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

[389-users] Re: 389ds refuses to start up after a reboot on CentOS7

[William Brown]

On Sun, 2016-07-17 at 19:30 +0200, Graham Leggett wrote:
> Hi all,
> 
> I am having some unexpected behaviour from 389ds v1.3.4.0-32 on CentOS7 and I 
> need to check if this looks familiar to anybody.
> 
> After installing 389ds and configuring it successfully, and proving 
> successfully that I can connect to it and that it contains data, I restarted 
> the machine to prove the server comes up on reboot. 389ds refused to come up.
> 
> Attempts to bring the server up manually using “systemctl start 
> dirsrv.target” have no effect.
> 
> What eventually got the service to start was “systemctl restart 
> dirsrv@instancename”, but this hasn’t solved the start-at-boot problem.
> 
> Does anyone have an accurate guide on 389ds and systemd?
> 

Yes, I have seen this issue.

It's actually a bug in the design of the .service files for the 1.3.4
release of 389-ds. 

This is fixed in 1.3.5.

The manual fix is:

cp /usr/lib/systemd/system/dirsrv@.service /etc/systemd/system/

Then to the file /etc/systemd/system/dirsrv@.service append:

[Install]
WantedBy=dirsrv.target


Assert the file /usr/lib/systemd/system/dirsrv.target contains:

[Install]
WantedBy=multi-user.target

Now you can do:

systemctl enable dirsrv.target
systemctl enable dirsrv@instance.target.


Hope this helps.


PS: You'll need to remove /etc/systemd/system/dirsrv@.service when you
upgrade to 1.3.5.



-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane


signature.asc
Description: This is a digitally signed message part
--
389-users mailing list
389-users@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org

Re: bad results from adding samsung v-nand SSD 950 PRO M.2 to ASUS laptop

[Tod Merley]

.. perhaps .. google "M.2 PCIE adapter"? ...

On Sun, Jul 17, 2016 at 2:18 PM, Chris Murphy 
wrote:

> Try a search for both errors, I'd put the salient portion in quotes.
>
>
>
>
> ---
> Chris Murphy
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 24 and PNY SSD Problems

[Jon LaBadie]

On Sun, Jul 17, 2016 at 08:45:13AM -0500, Gregory P. Ennis wrote:
> Everyone,
> 
> I am trying to reclaim some use out of a couple old Compaq Presaio
> SR1720NX machines for the office by adding some memory and a PNY 240 GB
> CS1311 SSD drives.  The bios was made by Phoenix; I did not identify a
> version number of the bios.  I did not plan on keep the hard drive
> installed and planned on just using the SSD.  These machines were IDE
> machines and only had two SATA ports on the motherboard.  
> 
> When I install the SSD the bios recognizes the Pny SSD properly, and I
> was able to set up the boot order without difficulty.
> 
When I had to replace the MB of a similar, older system, I used a non-HP MB.
Later when I wanted to beef it up, the new MB only had 2 SATA ports and
I wanted to install more drives.  So I purchased a really cheap SATA
controller card.

I got a store-brand SSD and to my surprise the MB controller did not
see it but the cheap controller did.  Blaming the store-brand SSD,
I returned it and got a Crucial SSD.  Same problem though.  So it
was the controller, not the SSD.  MB controller worked fine with
other SATA drives, but not with the SSD.

Jon
-- 
Jon H. LaBadie  jo...@jgcomp.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: bad results from adding samsung v-nand SSD 950 PRO M.2 to ASUS laptop

[Chris Murphy]

Try a search for both errors, I'd put the salient portion in quotes.




---
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 24 and PNY SSD Problems

[Chris Murphy]

Kernel messages might be revealing for both failure cases.


---
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 24 and PNY SSD Problems

[Gregory P. Ennis]

> 
> Are there preparatory things that I need to do with the SSD drives
> that
> I am missing?  Any help would be appreciated.
I know nothing for sure, but I'd try booting a live CD and
running gnome-disks from it to see what it sees. If it can see
the SSD, then perhaps there are already partitions on it
you could delete to make it a blank disk which the
installer might be more willing to install on.
--

Tom,

Thanks for the reply.  When I booted to the live f24 CD gnome-disks
does not identify the SSD drive.

I have two of these compaq machines and they are identical, just for
grins I set up the second machine, but unfortunately had the very same
symptoms, and observations as the first.

Both the F24 live CD install disc and the Net install disc present an
option to ADD DISC during the partition assignments.  I have never had
to use the 'ADD DISC' option.  I have played around with it, but never
could get the SSD to appear.  

Greg
--

So far I am having no success with these PNY SSD drives.  I installed
one of the SSD's in a different desktop computer that is quite a bit
more recent than those old Compaq units.  I was able to recognize the
SSD with the Fedora 24 install process, and the install appeared to
proceed without a problem.  However, I could not get the system to boot
the newly installed f24 os.  The boot process died after the message
"Verifing DMI Pool Data .."

I had hoped this would be an easy thing to do, but looks like this is
going to be a real fun project.  Any body have ideas?

Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

[389-users] 389ds refuses to start up after a reboot on CentOS7

[Graham Leggett]

Hi all,

I am having some unexpected behaviour from 389ds v1.3.4.0-32 on CentOS7 and I 
need to check if this looks familiar to anybody.

After installing 389ds and configuring it successfully, and proving 
successfully that I can connect to it and that it contains data, I restarted 
the machine to prove the server comes up on reboot. 389ds refused to come up.

Attempts to bring the server up manually using “systemctl start dirsrv.target” 
have no effect.

What eventually got the service to start was “systemctl restart 
dirsrv@instancename”, but this hasn’t solved the start-at-boot problem.

Does anyone have an accurate guide on 389ds and systemd?

Regards,
Graham
—
--
389-users mailing list
389-users@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org

Re: chroot

[Mike Wright]

On 07/17/2016 07:23 AM, Tom H wrote:


but you'd be better off using

systemd-nspawn -D /path/to/chroot_dir


Good contribution Tom.  I'd never heard of it before.  Very powerful.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: chroot

[Patrick Dupre]

Thank,

mount -t proc proc /path/to/chroot_dir/proc
chroot
works fine

but
systemd-nspawn -D /path/to/chroot_dir
provides:
Failed to determine whether the unified cgroups hierarchy is used: No such file 
or directory

then,

Spawning container linux on /mnt/linux.
Press ^] three times within 1s to kill container.
Host and machine ids are equal (a386c24a48d84be2825a0b0cb284c5e0): refusing to 
link journals

Any idea?

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Sunday, July 17, 2016 at 4:23 PM
> From: "Tom H" 
> To: "Fedora Users" 
> Subject: Re: chroot
>
> On Sun, Jul 17, 2016 at 9:55 AM, Patrick Dupre  wrote:
> >
> > I wanted to make a chroot, and I get:
> >
> > Error, do this: mount -t proc proc /proc
> > /bin/basename: missing operand
> > Try '/bin/basename --help' for more information.
> 
> Not enough info. What's calling basename?
> 
> The proc mount should be
> 
> mount -t proc proc /path/to/chroot_dir/proc
> 
> but you'd be better off using
> 
> systemd-nspawn -D /path/to/chroot_dir
> 
> to chroot without having to pre-mount proc or any other "api" filesystem.
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 24 and PNY SSD Problems

[Gregory P. Ennis]

> Are there preparatory things that I need to do with the SSD drives
> that
> I am missing?  Any help would be appreciated.
I know nothing for sure, but I'd try booting a live CD and
running gnome-disks from it to see what it sees. If it can see
the SSD, then perhaps there are already partitions on it
you could delete to make it a blank disk which the
installer might be more willing to install on.
--

Tom,

Thanks for the reply.  When I booted to the live f24 CD gnome-disks
does not identify the SSD drive.

I have two of these compaq machines and they are identical, just for
grins I set up the second machine, but unfortunately had the very same
symptoms, and observations as the first.

Both the F24 live CD install disc and the Net install disc present an
option to ADD DISC during the partition assignments.  I have never had
to use the 'ADD DISC' option.  I have played around with it, but never
could get the SSD to appear.  

Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: chroot

[Tom H]

On Sun, Jul 17, 2016 at 9:55 AM, Patrick Dupre  wrote:
>
> I wanted to make a chroot, and I get:
>
> Error, do this: mount -t proc proc /proc
> /bin/basename: missing operand
> Try '/bin/basename --help' for more information.

Not enough info. What's calling basename?

The proc mount should be

mount -t proc proc /path/to/chroot_dir/proc

but you'd be better off using

systemd-nspawn -D /path/to/chroot_dir

to chroot without having to pre-mount proc or any other "api" filesystem.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

chroot

[Patrick Dupre]

Hello,

I wanted to make a chroot, and I get:

Error, do this: mount -t proc proc /proc
/bin/basename: missing operand
Try '/bin/basename --help' for more information.


In the past, chroot was a working command (at least to make
to check). Does it not work properly anymore ?

Thank for your help.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 24 and PNY SSD Problems

[Tom Horsley]

On Sun, 17 Jul 2016 08:45:13 -0500
Gregory P. Ennis wrote:

> Are there preparatory things that I need to do with the SSD drives that
> I am missing?  Any help would be appreciated.

I know nothing for sure, but I'd try booting a live CD and
running gnome-disks from it to see what it sees. If it can see
the SSD, then perhaps there are already partitions on it
you could delete to make it a blank disk which the
installer might be more willing to install on.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Fedora 24 and PNY SSD Problems

[Gregory P. Ennis]

Everyone,

I am trying to reclaim some use out of a couple old Compaq Presaio
SR1720NX machines for the office by adding some memory and a PNY 240 GB
CS1311 SSD drives.  The bios was made by Phoenix; I did not identify a
version number of the bios.  I did not plan on keep the hard drive
installed and planned on just using the SSD.  These machines were IDE
machines and only had two SATA ports on the motherboard.  

When I install the SSD the bios recognizes the Pny SSD properly, and I
was able to set up the boot order without difficulty.

When I tried to install Fedora 24 on the first machine the installation
software did not identify the presences of the SSD.  I also tried a
Centso 7.2 install disc and the SSD was not recognized with it as well.
Just to make sure things were working, I added the hard drive back to
the machine, and the Fedora install routines did recognize the hard
drive but continued to fail to recognize the SSD. 

Are there preparatory things that I need to do with the SSD drives that
I am missing?  Any help would be appreciated.

Thanks,

Greg Ennis




--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

bad results from adding samsung v-nand SSD 950 PRO M.2 to ASUS laptop

[Robert P. J. Day]

  yesterday, i popped open my ASUS G752VL-DH71 to see two available
slots for SSD drives, both clearly labelled "PCIE only", so i inserted
a new samsung 950 PRO in slot 1, closed it up and booted and
(reproducing from scribbling on some paper, just the first bit):

  ata1.00: failed to enable AA (error_mask=0x4)
  ata1.00: revalidation failed

etc, etc, at which point it finally dropped me into an emergency
shell.

  i didn't have time to debug so i just removed it and got back to
work, but is there something i'm forgetting here? here's the samsung
page for that drive:

http://www.samsung.com/semiconductor/minisite/ssd/product/consumer/950pro.html

thoughts? like i said, i did not invest a lot of time trying to track
this down as i have way too much to do, but if there's something
stupid i've done, it would be good to know.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org