On Thu, 15 Sep 2011 13:17:14 +1000, yudi v wrote:
Got a reply back from WD asking me to return the drive, I wiped the
drive and tested the drive to see if it will throw up errors.
Again, both the WD tool and the Debian disk utility do not report any
bad sectors.
Can anyone explain what's
Got a reply back from WD asking me to return the drive, I wiped the drive
and tested the drive to see if it will throw up errors.
Again, both the WD tool and the Debian disk utility do not report any bad
sectors.
Can anyone explain what's going on?
--
Kind regards,
Yudi
On 11/09/11 22:58, consul tores wrote:
2011/9/11 Scott Ferguson prettyfly.producti...@gmail.com:
On 11/09/11 15:38, consul tores wrote:
2011/9/10 yudi vyudi@gmail.com:
snipped
-- Kind regards, Yudi
I think that, it is a problem with Squeeze fdisk+GPT; please try
cfdisk, it
On 11/09/11 23:27, consul tores wrote:
Adding Slackware test information:
bash-4.1# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes
On 11/09/11 14:09, yudi v wrote:
d-i uses parted (partman).
snipped
NOTE: neither fdisk or parted is the cause of your original problem...
This is what I thought. I suspect it's got something to do with the
kernel. I am just using the default Sqeeze kernel 2.6.32-5-686.
I'm unable to
On 10/09/11 15:51, consul tores wrote:
2011/9/9 yudi vyudi@gmail.com:
I would simply request for a hard disk replacement,
you will rest more relaxed after that :-)
I will definitely ask for a replacement as it's still under warranty but I
want to make sure it's not a software issue.
--
On 11/09/11 15:38, consul tores wrote:
2011/9/10 yudi vyudi@gmail.com:
snipped
--
Kind regards,
Yudi
I think that, it is a problem with Squeeze fdisk+GPT; please try
cfdisk, it seems updated.
Yudi is not using GPT.
cfdisk and fdisk are both part of (upstream) util-linux-ng[*1], so
cfdisk and fdisk are both part of (upstream) util-linux-ng[*1], so both
handle large sectors the same. In Squeeze they are both (currently) at
2.17.2-9.
I used gparted-live-0.8.1-3 (debian based with 2.6.38 kernel) to partition
it, I believe util-linux version on this image is 2.19. Then I
Scott Ferguson wrote:
Where did you get a version of cfdisk that is installable on normal
Debian system?
Umm, it is on my old lenny box and it is on my new squeeze box. I
didn't do anything special to install it. Most installs that I do are
minimal base installs to start with.
--
Kind
On 11/09/11 20:20, Andrew McGlashan wrote:
Scott Ferguson wrote:
Where did you get a version of cfdisk that is installable on normal
Debian system?
Umm, it is on my old lenny box and it is on my new squeeze box. I didn't
do anything special to install it. Most installs that I do are minimal
2011/9/11 Scott Ferguson prettyfly.producti...@gmail.com:
On 11/09/11 15:38, consul tores wrote:
2011/9/10 yudi vyudi@gmail.com:
snipped
--
Kind regards,
Yudi
I think that, it is a problem with Squeeze fdisk+GPT; please try
cfdisk, it seems updated.
Yudi is not using GPT.
Adding Slackware test information:
bash-4.1# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512
Have you tried # parted -l, fdisk works with cylinders.
here's the parted output:
Model: ATA WDC WD7500BPKT-6 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End SizeType File system Flags
1 1049kB 53.7GB
On 10/09/11 16:39, yudi v wrote:
Have you tried # parted -l, fdisk works with cylinders.
here's the parted output:
Model: ATA WDC WD7500BPKT-6 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
snipped
--
Kind regards,
Yudi
fdisk can't deal with non-4096B
On 10/09/11 16:39, yudi v wrote:
Have you tried # parted -l, fdisk works with cylinders.
here's the parted output:
Model: ATA WDC WD7500BPKT-6 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Sorry:-
fdisk can't deal with *non-*4096B
Use GPD instead of DOS partition types, *and* use parted instead of fdisk.
I used fdisk to partition the disk before installing the OS. Just to make
sure all the partitions started on the physical sector boundaries. The fdisk
output posted above looks fine, doesn't it? I followed this article
On 10/09/11 18:22, yudi v wrote:
Use GPD instead of DOS partition types, *and* use parted instead of
fdisk.
I used fdisk to partition the disk before installing the OS.
d-i uses parted (partman).
I know the first release of Squeeze failed to properly align 4K sectors
with
d-i uses parted (partman).
I know the first release of Squeeze failed to properly align 4K sectors
with partitions - but using the udeb from Wheezy fixed that for me - it
could be fixed in a previous point release, and, it could be just a DOS
partition table issue (what I used in that
2011/9/10 yudi v yudi@gmail.com:
d-i uses parted (partman).
I know the first release of Squeeze failed to properly align 4K sectors
with partitions - but using the udeb from Wheezy fixed that for me - it
could be fixed in a previous point release, and, it could be just a DOS
partition
2011/9/9 yudi v yudi@gmail.com:
I would simply request for a hard disk replacement,
you will rest more relaxed after that :-)
I will definitely ask for a replacement as it's still under warranty but I
want to make sure it's not a software issue.
--
Kind regards,
Yudi
Have you tried #
Disk utility tells that there are bad sectors on the new hard drive.
I had the same issue before and I was about to send it back to get it
replaced. I wrote random data to the drive and then checked once more to
make sure it had bad sectors. This time Disk utility came back saying that
the drive
On Fri, 09 Sep 2011 22:50:39 +1000, yudi v wrote:
Disk utility tells that there are bad sectors on the new hard drive.
New driver with bad sectors?
What is the output of smartctl -a /dev/sda
I had the same issue before and I was about to send it back to get it
replaced. I wrote random
I would simply request for a hard disk replacement,
you will rest more relaxed after that :-)
I will definitely ask for a replacement as it's still under warranty but I
want to make sure it's not a software issue.
--
Kind regards,
Yudi
smartctl -a /dev/sda output
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD7500BPKT-60PK4T0
Serial Number:WD-WX31E1177192
Firmware
On Sat, 10 Sep 2011 00:47:58 +1000, yudi v wrote:
smartctl -a /dev/sda output
Device Model: WDC WD7500BPKT-60PK4T0
(...)
Fiuu!... it's a WD :-P
Error 669 occurred at disk power-on lifetime: 312 hours (13 days + 0
hours)
When the command that caused the error occurred, the device
I would just return-back the unit. It is clearly new (less than 400 hours
of use!) and should not throw any error nor message about its SMART
health. This does not have to mean a bad drive per se, of course, but
better safe than sorry. If a new unit still fails, I would recheck the
cable
2011/9/9 yudi v yudi@gmail.com:
I would simply request for a hard disk replacement,
you will rest more relaxed after that :-)
I will definitely ask for a replacement as it's still under warranty but I
want to make sure it's not a software issue.
--
Kind regards,
Yudi
Have you tried #
27 matches
Mail list logo