[Expired for parted (Ubuntu) because there has been no activity for 60
days.]
** Changed in: parted (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/415888
Some comments seem to indicate that the problem is due to alignment, and
some due to ncq. If it is an alignment issue that should be fixed since
partitions are now alined to 1 MiB by default. If it is an ncq issue,
then it's not a bug in parted, but a hardware defect that may be worked
around wit
** Changed in: parted (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: parted (Ubuntu Karmic)
Assignee: Colin Watson (cjwatson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: parted (Ubuntu Karmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/415888
Title:
Installation fails on Crucial/Micron M225 256gb SSD
To manage n
Note I've had problems with my 128gb model on an Intel mobo, so I need
to, to this day, specify the "libata.force=noncq" kernel boot option for
things to apparently become smooth :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
What can you glean from the output of those three commands? I'm posting
mine here too FYI.
** Attachment added: "requested command output"
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/415888/+attachment/1956738/+files/info.log.zip
--
You received this bug notification because you a
This looks like the drive is rejecting IO requests that are not 4kb
aligned, which causes the journal to fail into read only mode.
Can you post the output of the following 3 commands:
sudo hdparm -I /dev/sda
sudo dd bs=512 count=1 iflag=direct of=/dev/null if=/dev/sda
sudo dd bs=512 count=1 iflag
with
mke2fs -t ext3 -E stripe-width=32 /dev/sda(x)
you attempt using 32 disks . You probably mean:
mke2fs -t ext3 -E stride=32 /dev/sda(x)
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member of U
Only quoting the fabled Ted Tso on that one :) personally I don't think it
makes much difference!
-Original Message-
From: Ralph Ulrich
Date: Wed, 17 Mar 2010 20:51:48
To:
Subject: [Bug 415888] Re: Installation fails on Crucial/Micron M225 256gb SSD
Rachael wrote:
> formattin
Rachael wrote:
> formatting should take place with:
> ~# mke2fs -t ext3 -E stripe-width=32 /dev/sda(x)
??
But due to man mkfs.ext3:
stripe-width=stripe-width
Configure the filesystem for a RAID array with
stripe-width filesystem blocks per stripe.
(posting this related, if not similar, issue as an FYI)
Folks, my problems are solved with Lucid 10.04 (alpha 2) and workarounds
- it looks like an NCQ issue, please go through the following
links/posts/threads:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/502219/comments/7
http://ubuntuf
P.S. Please let me know if you think I've messed up the maths somewhere
and got the geometry wrong! :(
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hi Colin,
So sorry for the delay - been up to my neck in work and kind of forgot about
your request.
Anyway, attached is the sda folder - I hope it helps you.
As I said before tho, the problem doesn't appear to the balancing of the ssd
itself.
The problem definitely resides with the implementat
Hi Rachael,
Did you get a chance to get the tarball of /sys/block/sda/ that I asked
for? I'll need that to make sure I get the code right, I think.
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a m
Thanks for that! That doesn't look *too* bad, so I'll see what I can do
to get something similar integrated.
Could you attach a tarball of /sys/block/sda/, just so that I can make
sure to get the detection code right?
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.
OK... problem solved (at least, sort of...)
the installation failure is entirely to do with the ext4 file system.
using ext3 gives no problems whatsoever. this is irrespective of whether
or not the ssd is correctly balanced.
the correct balancing for a 128k erase block ssd (most ssd but not ocz)
The size difference is actually a red herring, and nothing to do with
this bug. GParted shows sizes in binary units (note the "i" in "GiB"
after the number) - a GiB is 1024 * 1024 * 1024 bytes. The installer's
partitioner, partman, shows sizes in decimal units (GB) - a GB here is
1000 * 1000 * 1000
and this is the partition manager screen photo...
** Attachment added: "DSCN0358.JPG"
http://launchpadlibrarian.net/30717933/DSCN0358.JPG
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member o
hi colin
thnkyou SO much for looking at this - i'm very relieved to know that i'm
definitely not going round the twist!
the only other information i think i can give you which may help are the
attached 2 photographs. the first is a shot of how GParted sees the disk
structure of a successful ext3
** Changed in: parted (Ubuntu Karmic)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It does sort of look like an alignment issue (and the fact that LVM
makes it work is very suggestive of this), but I agree that it's
surprising that that would make it not work at all. I don't have a quick
answer for you, but since this is important for performance on other
SSDs anyway I hope that
and the partman file for the successful installation...
told ya it wasnt my SSD lol
** Attachment added: "partman"
http://launchpadlibrarian.net/30706404/partman
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification b
Ah-Ha now THAT'S interesting
have just tried the install again from the 9.04 live CD, but this time
with ext3 formatting instead of ext4 and its worked
So I guess the problem must lie either in the ext4 file system
itself or the way the installer attempts to implement it
And
and here's the partition manager log
** Attachment added: "partman"
http://launchpadlibrarian.net/30705887/partman
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK these are the install files for the 9.04 Kubuntu live cd. Hope they
help.
On this occasion the error give was "/target/bin is read only" - which
it isn't and there is nothing wrong with the SSD.
** Attachment added: "syslog"
http://launchpadlibrarian.net/30705876/syslog
--
Installation f
Please do a test installation using the desktop (live) CD up to the
point where it falls over, and then *before rebooting* attach these two
files to this bug report:
/var/log/syslog
/var/log/partman
That should help us see what's going on in a bit more detail.
** Package changed: kubuntu-me
it doesnt work, the installer cd still mis-represents the size of the
partitions.
crucial support (us) also suggested using GParted to form a unformatted
partition which could then be used. once again, doesnt work
the installation fails universally at one of 3 points:
(1) right at the beginning
What happens if you make your partitions yourself using fdisk/gparted
before doing the installation? Afaik the alignment of partitions affects
performance on SSDs but shouldn't make it not work at all.
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
Y
Might also be something to do with "partition balancing" Apparently
this is required for SSD operation
--
Installation fails on Crucial/Micron M225 256gb SSD
https://bugs.launchpad.net/bugs/415888
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscr
have just spent most of today on the phone to Crucial support.
Apprently the 256gb SDD drive does only have 238.47gb of usable space...
so, therefore, my unit is fine.
What I'm guessing is that the installer disks are trying to partition to
the declared 256.1gb and so are crashing when unable to
30 matches
Mail list logo