From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] m.2 nvme stick not what I was expecting at all.
Date: Mon, 24 Feb 2025 12:58:13 -0600 [thread overview]
Message-ID: <e902eadf-b056-c19a-6851-77398bfaf145@gmail.com> (raw)
Howdy,
I ordered a m.2 stick and a enclosure as I posted on another thread. I
want some people to look at this and see if I should return it. The
title says 1TB but I got a 480GB stick. If I look down at the smaller
print, it says 480GB. Thing is, I went by the title. I wanted a 1TB
m.2 nvme stick and the title gave me the info to know it would fit and
was the size I wanted. I might add, I searched Amazon for a 1tb stick,
not a 480GB stick. I wouldn't expect a wrong item to show up so close
to the top so Amazon was confused too. Here is a link.
https://www.amazon.com/gp/product/B0DQSX3Z76
I was really wanting a 1TB stick. Would I be wrong to want to return
this given the title is so misleading as to the size? Price wise, it
isn't a bad deal for the size. Given some info posted by someone in the
other thread, I'll likely replace this with a Samsung and just hang on
to it for a backup in case I need one later or something. Part of me
says keep it, order what I really want, the Samsung, and keep this for a
backup since the price for what I got is reasonable. After all, I
didn't pay the 1TB price. Other part of me says this is misleading and
not what I wanted. Returning is a hassle and could even cost me a fee
tho. It isn't a Prime deal.
Thoughts? What would you do? The 480GB is likely big enough for now.
Dale
:-) :-)
next reply other threads:[~2025-02-24 18:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:58 Dale [this message]
2025-02-24 19:20 ` [gentoo-user] m.2 nvme stick not what I was expecting at all Jack
2025-02-24 19:49 ` Dale
2025-02-24 19:40 ` Mark Knecht
2025-02-24 19:41 ` Rich Freeman
2025-02-24 19:53 ` Dale
2025-02-24 20:00 ` Rich Freeman
2025-02-24 20:34 ` Dale
2025-02-24 20:02 ` eric
2025-02-24 20:11 ` Mark Knecht
2025-02-24 20:44 ` Dale
2025-02-24 22:48 ` Frank Steinmetzger
2025-02-25 3:56 ` Dale
2025-02-25 10:08 ` Michael
2025-02-25 11:00 ` Dale
2025-02-25 11:16 ` Michael
2025-02-25 15:57 ` Dale
2025-02-25 17:05 ` Rich Freeman
2025-02-25 19:00 ` Michael
2025-02-25 19:18 ` Rich Freeman
2025-02-25 20:39 ` Michael
2025-02-25 22:16 ` Frank Steinmetzger
2025-02-25 14:48 ` Peter Humphrey
2025-02-25 17:00 ` Michael
2025-02-24 22:13 ` Frank Steinmetzger
2025-02-25 4:20 ` Dale
2025-02-25 8:18 ` Wols Lists
2025-02-25 14:07 ` [gentoo-user] " Grant Edwards
2025-02-25 8:20 ` [gentoo-user] " Wols Lists
2025-02-25 11:09 ` Dale
2025-02-25 12:26 ` Dale
2025-02-25 15:04 ` Rich Freeman
2025-02-25 15:32 ` Dale
2025-02-25 16:29 ` Rich Freeman
2025-02-25 17:26 ` Dale
2025-02-25 17:41 ` Rich Freeman
2025-02-26 14:43 ` Dale
2025-02-26 16:38 ` Michael
2025-02-26 20:34 ` Dale
2025-02-26 20:48 ` Mark Knecht
2025-02-25 20:19 ` Wol
2025-02-25 20:21 ` Michael
2025-02-25 21:34 ` Frank Steinmetzger
2025-02-26 7:52 ` Wols Lists
2025-02-26 16:44 ` Michael
2025-02-26 18:03 ` Wol
2025-02-26 18:05 ` Rich Freeman
2025-02-26 18:42 ` Wol
2025-02-26 19:26 ` Rich Freeman
2025-02-26 19:47 ` Wols Lists
2025-02-26 19:56 ` Rich Freeman
2025-02-26 21:25 ` Wol
2025-02-26 22:37 ` Michael
2025-02-26 16:41 ` Michael
2025-02-28 5:43 ` Dale
2025-02-28 16:40 ` [gentoo-user] " Grant Edwards
2025-03-02 16:01 ` Dale
2025-03-02 22:06 ` Frank Steinmetzger
2025-03-02 22:39 ` Dale
2025-03-03 3:01 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e902eadf-b056-c19a-6851-77398bfaf145@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox