Re: new external drive
You will need to use the manufacturer disk tools to verify the hardware is bad. I would still go that route. On Nov 26, 2016 7:31 AM, "Michael" wrote: > this was the result of badblocks: > > Testing with pattern 0x55: 0.00% done, 12:18:18 elapsed. > (98304/60951342/0 errdone > ors) > Reading and comparing: done > ors) > Testing with pattern 0xff: 0.00% done, 12:20:59 elapsed. > (98304/60951342/0 errdone > ors) > Reading and comparing: done > ors) > Testing with pattern 0x00: 0.00% done, 12:23:41 elapsed. > (98304/60951342/0 errdone > ors) > Reading and comparing: done > ors) > > that is a whole bunch of write errors! > > On Fri, Nov 25, 2016 at 6:38 PM, Brien Dieterle wrote: > >> Yeah I would send it back :-p >> >> On Nov 25, 2016 4:37 PM, "Michael" wrote: >> >>> I would love to use a *nix native file system but I want to be able to >>> share this between systems. Everytime the thing goes to a new line the >>> write error is incremented by 1. This is a new disk. It shouldn't do that! >>> I think I should send it back! What do you guys think? >>> >>> On Fri, Nov 25, 2016 at 6:08 PM, Brien Dieterle >>> wrote: >>> http://unix.stackexchange.com/questions/65349/how-to-interpr et-badblocks-output Sounds like it had a lot of writing errors. Thing is I'll not sure how to deal with it while using NTFS http://linux.bigresource.com/General-NTFS-marking-sectors-ba d--aLwrEyk32.html If you use ext3 or ext4 you can check for and mark bad blocks during format with the -c option. mkfs.ext4 -c /dev/sdd1 On Nov 25, 2016 1:59 PM, "Michael" wrote: > I was wondering: > The print out on the terminal reads: > > 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) > > what does "(0/7649/0 errors)" mean? > > On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: > >> I'm trying to run 'badblocks' but each time I run it get the same >> thing. >> >> $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar >> badblocks: invalid starting block (0): must be less than 0 >> . >> . >> . >> I just googled the error and find: >> >> -Apparently this is Linux-speak for "This program needs the name of a >> device file, and the programmer was too lazy to have it detect that you >> supplied the name of the mount point instead".- >> >> How do I discover the device as opposed to the mount point? >> >> On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle >> wrote: >> >>> Almost looks like bad sectors. Might want to try badblocks >>> https://wiki.archlinux.org/index.php/badblocks >>> Maybe try formatting it ext4 >>> Maybe try another USB port and cable >>> >>> On Nov 24, 2016 1:21 PM, "Michael" wrote: >>> I really appreciate the help It errored out though. Here is what gparted reported: *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37 ( ERROR ) create empty partition 00:00:00( SUCCESS ) *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( SUCCESS ) flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) set partition type on /dev/sdd1 00:00:00( SUCCESS ) *new partition type: ntfs* create new ntfs file system 00:00:37( ERROR ) *mkntfs -Q -v -L "NexStar" /dev/sdd1* *Cluster size has been automatically set to 4096 bytes.Creating NTFS volume structures.Creating root directory (mft record 5)Creating $MFT (mft record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating system file (mft record 0xc)Creating system file (mft record 0xd)Creating system file (mft record 0xe)Creating system file (mft record 0xf)Creating $Quota (mft record 24)Crea
Re: new external drive
this was the result of badblocks: Testing with pattern 0x55: 0.00% done, 12:18:18 elapsed. (98304/60951342/0 errdone ors) Reading and comparing: done ors) Testing with pattern 0xff: 0.00% done, 12:20:59 elapsed. (98304/60951342/0 errdone ors) Reading and comparing: done ors) Testing with pattern 0x00: 0.00% done, 12:23:41 elapsed. (98304/60951342/0 errdone ors) Reading and comparing: done ors) that is a whole bunch of write errors! On Fri, Nov 25, 2016 at 6:38 PM, Brien Dieterle wrote: > Yeah I would send it back :-p > > On Nov 25, 2016 4:37 PM, "Michael" wrote: > >> I would love to use a *nix native file system but I want to be able to >> share this between systems. Everytime the thing goes to a new line the >> write error is incremented by 1. This is a new disk. It shouldn't do that! >> I think I should send it back! What do you guys think? >> >> On Fri, Nov 25, 2016 at 6:08 PM, Brien Dieterle wrote: >> >>> http://unix.stackexchange.com/questions/65349/how-to-interpr >>> et-badblocks-output >>> >>> Sounds like it had a lot of writing errors. Thing is I'll not sure how >>> to deal with it while using NTFS >>> >>> http://linux.bigresource.com/General-NTFS-marking-sectors-ba >>> d--aLwrEyk32.html >>> >>> If you use ext3 or ext4 you can check for and mark bad blocks during >>> format with the -c option. mkfs.ext4 -c /dev/sdd1 >>> >>> On Nov 25, 2016 1:59 PM, "Michael" wrote: >>> I was wondering: The print out on the terminal reads: 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) what does "(0/7649/0 errors)" mean? On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: > I'm trying to run 'badblocks' but each time I run it get the same > thing. > > $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar > badblocks: invalid starting block (0): must be less than 0 > . > . > . > I just googled the error and find: > > -Apparently this is Linux-speak for "This program needs the name of a > device file, and the programmer was too lazy to have it detect that you > supplied the name of the mount point instead".- > > How do I discover the device as opposed to the mount point? > > On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle > wrote: > >> Almost looks like bad sectors. Might want to try badblocks >> https://wiki.archlinux.org/index.php/badblocks >> Maybe try formatting it ext4 >> Maybe try another USB port and cable >> >> On Nov 24, 2016 1:21 PM, "Michael" wrote: >> >>> I really appreciate the help It errored out though. Here is what >>> gparted reported: >>> >>> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37 >>> ( >>> ERROR ) >>> >>> create empty partition 00:00:00( SUCCESS ) >>> >>> >>> >>> >>> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 >>> GiB)* >>> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS >>> ) >>> >>> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( >>> SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >>> SUCCESS ) >>> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >>> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >>> >>> *new partition type: ntfs* >>> create new ntfs file system 00:00:37( ERROR ) >>> >>> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >>> volume structures.Creating root directory (mft record 5)Creating $MFT >>> (mft >>> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >>> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record >>> 6)Creating >>> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >>> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >>> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record >>> 11)Creating >>> system file (mft record 0xc)Creating system file (mft record >>> 0xd)Creating >>> system file (mft record 0xe)Creating system file (mft record >>> 0xf)Creating >>> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse >>> (mft >>> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >>> $MFT.Updating $MFTMirr.Syncing device.* >>> >>> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >>> FAILED* >>> >>> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Part
Re: new external drive
Yeah I would send it back :-p On Nov 25, 2016 4:37 PM, "Michael" wrote: > I would love to use a *nix native file system but I want to be able to > share this between systems. Everytime the thing goes to a new line the > write error is incremented by 1. This is a new disk. It shouldn't do that! > I think I should send it back! What do you guys think? > > On Fri, Nov 25, 2016 at 6:08 PM, Brien Dieterle wrote: > >> http://unix.stackexchange.com/questions/65349/how-to-interpr >> et-badblocks-output >> >> Sounds like it had a lot of writing errors. Thing is I'll not sure how >> to deal with it while using NTFS >> >> http://linux.bigresource.com/General-NTFS-marking-sectors-ba >> d--aLwrEyk32.html >> >> If you use ext3 or ext4 you can check for and mark bad blocks during >> format with the -c option. mkfs.ext4 -c /dev/sdd1 >> >> On Nov 25, 2016 1:59 PM, "Michael" wrote: >> >>> I was wondering: >>> The print out on the terminal reads: >>> >>> 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) >>> >>> what does "(0/7649/0 errors)" mean? >>> >>> On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: >>> I'm trying to run 'badblocks' but each time I run it get the same thing. $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar badblocks: invalid starting block (0): must be less than 0 . . . I just googled the error and find: -Apparently this is Linux-speak for "This program needs the name of a device file, and the programmer was too lazy to have it detect that you supplied the name of the mount point instead".- How do I discover the device as opposed to the mount point? On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: > Almost looks like bad sectors. Might want to try badblocks > https://wiki.archlinux.org/index.php/badblocks > Maybe try formatting it ext4 > Maybe try another USB port and cable > > On Nov 24, 2016 1:21 PM, "Michael" wrote: > >> I really appreciate the help It errored out though. Here is what >> gparted reported: >> >> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37 >> ( >> ERROR ) >> >> create empty partition 00:00:00( SUCCESS ) >> >> >> >> >> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* >> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) >> >> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( >> SUCCESS ) >> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >> SUCCESS ) >> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >> >> *new partition type: ntfs* >> create new ntfs file system 00:00:37( ERROR ) >> >> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >> volume structures.Creating root directory (mft record 5)Creating $MFT >> (mft >> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating >> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record >> 11)Creating >> system file (mft record 0xc)Creating system file (mft record 0xd)Creating >> system file (mft record 0xe)Creating system file (mft record 0xf)Creating >> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse >> (mft >> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >> $MFT.Updating $MFTMirr.Syncing device.* >> >> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >> FAILED* >> >> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington < >> cryptwo...@gmail.com> wrote: >> >>> Get gparted and use it to take a look. Lots of USB drives have some >>> wonky trick they use. >>> >>> On Nov 24, 2016 12:04 PM, "Michael" wrote: >>> I got a problem. This new drive won't format. Linux saw it when I first plugged it in. I then tried copying some files to it which resulted in an error appearing after 5-10 minutes telling me to open windows and run 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't figure out how to open a terminal so I decided to format it. But it wouldn
Re: new external drive
I would love to use a *nix native file system but I want to be able to share this between systems. Everytime the thing goes to a new line the write error is incremented by 1. This is a new disk. It shouldn't do that! I think I should send it back! What do you guys think? On Fri, Nov 25, 2016 at 6:08 PM, Brien Dieterle wrote: > http://unix.stackexchange.com/questions/65349/how-to- > interpret-badblocks-output > > Sounds like it had a lot of writing errors. Thing is I'll not sure how to > deal with it while using NTFS > > http://linux.bigresource.com/General-NTFS-marking-sectors- > bad--aLwrEyk32.html > > If you use ext3 or ext4 you can check for and mark bad blocks during > format with the -c option. mkfs.ext4 -c /dev/sdd1 > > On Nov 25, 2016 1:59 PM, "Michael" wrote: > >> I was wondering: >> The print out on the terminal reads: >> >> 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) >> >> what does "(0/7649/0 errors)" mean? >> >> On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: >> >>> I'm trying to run 'badblocks' but each time I run it get the same thing. >>> >>> $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar >>> badblocks: invalid starting block (0): must be less than 0 >>> . >>> . >>> . >>> I just googled the error and find: >>> >>> -Apparently this is Linux-speak for "This program needs the name of a >>> device file, and the programmer was too lazy to have it detect that you >>> supplied the name of the mount point instead".- >>> >>> How do I discover the device as opposed to the mount point? >>> >>> On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle >>> wrote: >>> Almost looks like bad sectors. Might want to try badblocks https://wiki.archlinux.org/index.php/badblocks Maybe try formatting it ext4 Maybe try another USB port and cable On Nov 24, 2016 1:21 PM, "Michael" wrote: > I really appreciate the help It errored out though. Here is what > gparted reported: > > *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37 > ( > ERROR ) > > create empty partition 00:00:00( SUCCESS ) > > > > > *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* > clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) > > write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) > write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS > ) > write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( > SUCCESS ) > flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) > set partition type on /dev/sdd1 00:00:00( SUCCESS ) > > *new partition type: ntfs* > create new ntfs file system 00:00:37( ERROR ) > > *mkntfs -Q -v -L "NexStar" /dev/sdd1* > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Cluster size has been automatically set to 4096 bytes.Creating NTFS > volume structures.Creating root directory (mft record 5)Creating $MFT (mft > record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record > 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating > $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft > record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record > 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record > 11)Creating > system file (mft record 0xc)Creating system file (mft record 0xd)Creating > system file (mft record 0xe)Creating system file (mft record 0xf)Creating > $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse > (mft > record 26)Syncing root directory index record.Syncing $Bitmap.Syncing > $MFT.Updating $MFTMirr.Syncing device.* > > *Failed to sync device /dev/sdd1: Input/output errorSyncing device. > FAILED* > > On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington < > cryptwo...@gmail.com> wrote: > >> Get gparted and use it to take a look. Lots of USB drives have some >> wonky trick they use. >> >> On Nov 24, 2016 12:04 PM, "Michael" wrote: >> >>> >>> I got a problem. This new drive won't format. Linux saw it when I >>> first plugged it in. I then tried copying some files to it which >>> resulted >>> in an error appearing after 5-10 minutes telling me to open windows and >>> run >>> 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't >>> figure out how to open a terminal so I decided to format it. But it >>> wouldn't format. When I attempt to it flashes twice a second for a >>> little >>> then a long flash then again quickly. So I figured I would attempt the >>> format with Linux but Linux doesn't see the drive now so no formatting >>> with
Re: new external drive
http://unix.stackexchange.com/questions/65349/how-to-interpret-badblocks-output Sounds like it had a lot of writing errors. Thing is I'll not sure how to deal with it while using NTFS http://linux.bigresource.com/General-NTFS-marking-sectors-bad--aLwrEyk32.html If you use ext3 or ext4 you can check for and mark bad blocks during format with the -c option. mkfs.ext4 -c /dev/sdd1 On Nov 25, 2016 1:59 PM, "Michael" wrote: > I was wondering: > The print out on the terminal reads: > > 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) > > what does "(0/7649/0 errors)" mean? > > On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: > >> I'm trying to run 'badblocks' but each time I run it get the same thing. >> >> $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar >> badblocks: invalid starting block (0): must be less than 0 >> . >> . >> . >> I just googled the error and find: >> >> -Apparently this is Linux-speak for "This program needs the name of a >> device file, and the programmer was too lazy to have it detect that you >> supplied the name of the mount point instead".- >> >> How do I discover the device as opposed to the mount point? >> >> On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: >> >>> Almost looks like bad sectors. Might want to try badblocks >>> https://wiki.archlinux.org/index.php/badblocks >>> Maybe try formatting it ext4 >>> Maybe try another USB port and cable >>> >>> On Nov 24, 2016 1:21 PM, "Michael" wrote: >>> I really appreciate the help It errored out though. Here is what gparted reported: *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( ERROR ) create empty partition 00:00:00( SUCCESS ) *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( SUCCESS ) flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) set partition type on /dev/sdd1 00:00:00( SUCCESS ) *new partition type: ntfs* create new ntfs file system 00:00:37( ERROR ) *mkntfs -Q -v -L "NexStar" /dev/sdd1* *Cluster size has been automatically set to 4096 bytes.Creating NTFS volume structures.Creating root directory (mft record 5)Creating $MFT (mft record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating system file (mft record 0xc)Creating system file (mft record 0xd)Creating system file (mft record 0xe)Creating system file (mft record 0xf)Creating $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft record 26)Syncing root directory index record.Syncing $Bitmap.Syncing $MFT.Updating $MFTMirr.Syncing device.* *Failed to sync device /dev/sdd1: Input/output errorSyncing device. FAILED* On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington < cryptwo...@gmail.com> wrote: > Get gparted and use it to take a look. Lots of USB drives have some > wonky trick they use. > > On Nov 24, 2016 12:04 PM, "Michael" wrote: > >> >> I got a problem. This new drive won't format. Linux saw it when I >> first plugged it in. I then tried copying some files to it which resulted >> in an error appearing after 5-10 minutes telling me to open windows and >> run >> 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't >> figure out how to open a terminal so I decided to format it. But it >> wouldn't format. When I attempt to it flashes twice a second for a little >> then a long flash then again quickly. So I figured I would attempt the >> format with Linux but Linux doesn't see the drive now so no formatting >> with >> it. Can someone help? >> -- >> :-)~MIKE~(-: >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings:
Re: new external drive
I was wondering: The print out on the terminal reads: 1973729 done, 3:49:08 elapsed. (0/7649/0 errors) what does "(0/7649/0 errors)" mean? On Fri, Nov 25, 2016 at 10:49 AM, Michael wrote: > I'm trying to run 'badblocks' but each time I run it get the same thing. > > $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar > badblocks: invalid starting block (0): must be less than 0 > . > . > . > I just googled the error and find: > > -Apparently this is Linux-speak for "This program needs the name of a > device file, and the programmer was too lazy to have it detect that you > supplied the name of the mount point instead".- > > How do I discover the device as opposed to the mount point? > > On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: > >> Almost looks like bad sectors. Might want to try badblocks >> https://wiki.archlinux.org/index.php/badblocks >> Maybe try formatting it ext4 >> Maybe try another USB port and cable >> >> On Nov 24, 2016 1:21 PM, "Michael" wrote: >> >>> I really appreciate the help It errored out though. Here is what >>> gparted reported: >>> >>> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( >>> ERROR ) >>> >>> create empty partition 00:00:00( SUCCESS ) >>> >>> >>> >>> >>> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* >>> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) >>> >>> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >>> SUCCESS ) >>> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >>> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >>> >>> *new partition type: ntfs* >>> create new ntfs file system 00:00:37( ERROR ) >>> >>> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >>> volume structures.Creating root directory (mft record 5)Creating $MFT (mft >>> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >>> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating >>> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >>> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >>> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating >>> system file (mft record 0xc)Creating system file (mft record 0xd)Creating >>> system file (mft record 0xe)Creating system file (mft record 0xf)Creating >>> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft >>> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >>> $MFT.Updating $MFTMirr.Syncing device.* >>> >>> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >>> FAILED* >>> >>> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington < >>> cryptwo...@gmail.com> wrote: >>> Get gparted and use it to take a look. Lots of USB drives have some wonky trick they use. On Nov 24, 2016 12:04 PM, "Michael" wrote: > > I got a problem. This new drive won't format. Linux saw it when I > first plugged it in. I then tried copying some files to it which resulted > in an error appearing after 5-10 minutes telling me to open windows and > run > 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't > figure out how to open a terminal so I decided to format it. But it > wouldn't format. When I attempt to it flashes twice a second for a little > then a long flash then again quickly. So I figured I would attempt the > format with Linux but Linux doesn't see the drive now so no formatting > with > it. Can someone help? > -- > :-)~MIKE~(-: > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >>> >>> >>> -- >>> :-)~MIKE~(-: >>> >>> --- >>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >>> To subscribe, unsubscribe, or to change your mail settings: >>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/ma
Re: new external drive
> From: Bob Holtzman > Date: Fri, 25 Nov 2016 11:06:29 -0700 > > Take your HTML and. > > My apologies to anyone I've offended with that. It's the ones you've frightened that you should worry about. ;-) I didn't even see the HTML. What damaged email reader are you abusing? :-) :-) --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
On Thu, Nov 24, 2016 at 06:14:12PM -0700, Michael Butash wrote: > > > > > > I'd say you have a bad unit. Try pulling the drive out of it and > connecting it direct to a sata bus and see if that works to get a > response to the bus. Either the drive, or the usb converter chip ..snip. Take your HTML and. My apologies to anyone I've offended with that. > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss -- Bob Holtzman "Bother", said Pooh, as he chambered another round... --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
I should have realized that! Thanks On Fri, Nov 25, 2016 at 11:15 AM, Brien Dieterle wrote: > Gparted tells you. It was /dev/sdd before, but check again as it can > change. Also unmount the filesystem first > > On Nov 25, 2016 8:50 AM, "Michael" wrote: > > I'm trying to run 'badblocks' but each time I run it get the same thing. > > $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar > badblocks: invalid starting block (0): must be less than 0 > . > . > . > I just googled the error and find: > > -Apparently this is Linux-speak for "This program needs the name of a > device file, and the programmer was too lazy to have it detect that you > supplied the name of the mount point instead".- > > How do I discover the device as opposed to the mount point? > > On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: > >> Almost looks like bad sectors. Might want to try badblocks >> https://wiki.archlinux.org/index.php/badblocks >> Maybe try formatting it ext4 >> Maybe try another USB port and cable >> >> On Nov 24, 2016 1:21 PM, "Michael" wrote: >> >>> I really appreciate the help It errored out though. Here is what >>> gparted reported: >>> >>> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( >>> ERROR ) >>> >>> create empty partition 00:00:00( SUCCESS ) >>> >>> >>> >>> >>> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* >>> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) >>> >>> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) >>> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >>> SUCCESS ) >>> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >>> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >>> >>> *new partition type: ntfs* >>> create new ntfs file system 00:00:37( ERROR ) >>> >>> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >>> volume structures.Creating root directory (mft record 5)Creating $MFT (mft >>> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >>> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating >>> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >>> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >>> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating >>> system file (mft record 0xc)Creating system file (mft record 0xd)Creating >>> system file (mft record 0xe)Creating system file (mft record 0xf)Creating >>> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft >>> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >>> $MFT.Updating $MFTMirr.Syncing device.* >>> >>> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >>> FAILED* >>> >>> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington < >>> cryptwo...@gmail.com> wrote: >>> Get gparted and use it to take a look. Lots of USB drives have some wonky trick they use. On Nov 24, 2016 12:04 PM, "Michael" wrote: > > I got a problem. This new drive won't format. Linux saw it when I > first plugged it in. I then tried copying some files to it which resulted > in an error appearing after 5-10 minutes telling me to open windows and > run > 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't > figure out how to open a terminal so I decided to format it. But it > wouldn't format. When I attempt to it flashes twice a second for a little > then a long flash then again quickly. So I figured I would attempt the > format with Linux but Linux doesn't see the drive now so no formatting > with > it. Can someone help? > -- > :-)~MIKE~(-: > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >>> >>> >>> -- >>> :-)~MIKE~(-: >>> >>> --- >>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >>> To subscribe, unsubscribe, or to change your mail settings: >>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsub
Re: new external drive
Gparted tells you. It was /dev/sdd before, but check again as it can change. Also unmount the filesystem first On Nov 25, 2016 8:50 AM, "Michael" wrote: I'm trying to run 'badblocks' but each time I run it get the same thing. $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar badblocks: invalid starting block (0): must be less than 0 . . . I just googled the error and find: -Apparently this is Linux-speak for "This program needs the name of a device file, and the programmer was too lazy to have it detect that you supplied the name of the mount point instead".- How do I discover the device as opposed to the mount point? On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: > Almost looks like bad sectors. Might want to try badblocks > https://wiki.archlinux.org/index.php/badblocks > Maybe try formatting it ext4 > Maybe try another USB port and cable > > On Nov 24, 2016 1:21 PM, "Michael" wrote: > >> I really appreciate the help It errored out though. Here is what >> gparted reported: >> >> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( >> ERROR ) >> >> create empty partition 00:00:00( SUCCESS ) >> >> >> >> >> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* >> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) >> >> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) >> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >> SUCCESS ) >> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >> >> *new partition type: ntfs* >> create new ntfs file system 00:00:37( ERROR ) >> >> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >> volume structures.Creating root directory (mft record 5)Creating $MFT (mft >> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating >> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating >> system file (mft record 0xc)Creating system file (mft record 0xd)Creating >> system file (mft record 0xe)Creating system file (mft record 0xf)Creating >> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft >> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >> $MFT.Updating $MFTMirr.Syncing device.* >> >> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >> FAILED* >> >> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington > > wrote: >> >>> Get gparted and use it to take a look. Lots of USB drives have some >>> wonky trick they use. >>> >>> On Nov 24, 2016 12:04 PM, "Michael" wrote: >>> I got a problem. This new drive won't format. Linux saw it when I first plugged it in. I then tried copying some files to it which resulted in an error appearing after 5-10 minutes telling me to open windows and run 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't figure out how to open a terminal so I decided to format it. But it wouldn't format. When I attempt to it flashes twice a second for a little then a long flash then again quickly. So I figured I would attempt the format with Linux but Linux doesn't see the drive now so no formatting with it. Can someone help? -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >>> --- >>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >>> To subscribe, unsubscribe, or to change your mail settings: >>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >> >> >> >> -- >> :-)~MIKE~(-: >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: ht
Re: new external drive
I'm trying to run 'badblocks' but each time I run it get the same thing. $ sudo badblocks -b 4096 -c 98304 -p 0 -w -s /media/bmike1/NexStar badblocks: invalid starting block (0): must be less than 0 . . . I just googled the error and find: -Apparently this is Linux-speak for "This program needs the name of a device file, and the programmer was too lazy to have it detect that you supplied the name of the mount point instead".- How do I discover the device as opposed to the mount point? On Thu, Nov 24, 2016 at 4:30 PM, Brien Dieterle wrote: > Almost looks like bad sectors. Might want to try badblocks > https://wiki.archlinux.org/index.php/badblocks > Maybe try formatting it ext4 > Maybe try another USB port and cable > > On Nov 24, 2016 1:21 PM, "Michael" wrote: > >> I really appreciate the help It errored out though. Here is what >> gparted reported: >> >> *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( >> ERROR ) >> >> create empty partition 00:00:00( SUCCESS ) >> >> >> >> >> *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* >> clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) >> >> write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) >> write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) >> write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( >> SUCCESS ) >> flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) >> set partition type on /dev/sdd1 00:00:00( SUCCESS ) >> >> *new partition type: ntfs* >> create new ntfs file system 00:00:37( ERROR ) >> >> *mkntfs -Q -v -L "NexStar" /dev/sdd1* >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Cluster size has been automatically set to 4096 bytes.Creating NTFS >> volume structures.Creating root directory (mft record 5)Creating $MFT (mft >> record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record >> 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating >> $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft >> record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record >> 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating >> system file (mft record 0xc)Creating system file (mft record 0xd)Creating >> system file (mft record 0xe)Creating system file (mft record 0xf)Creating >> $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft >> record 26)Syncing root directory index record.Syncing $Bitmap.Syncing >> $MFT.Updating $MFTMirr.Syncing device.* >> >> *Failed to sync device /dev/sdd1: Input/output errorSyncing device. >> FAILED* >> >> On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington > > wrote: >> >>> Get gparted and use it to take a look. Lots of USB drives have some >>> wonky trick they use. >>> >>> On Nov 24, 2016 12:04 PM, "Michael" wrote: >>> I got a problem. This new drive won't format. Linux saw it when I first plugged it in. I then tried copying some files to it which resulted in an error appearing after 5-10 minutes telling me to open windows and run 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't figure out how to open a terminal so I decided to format it. But it wouldn't format. When I attempt to it flashes twice a second for a little then a long flash then again quickly. So I figured I would attempt the format with Linux but Linux doesn't see the drive now so no formatting with it. Can someone help? -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >>> --- >>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >>> To subscribe, unsubscribe, or to change your mail settings: >>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >> >> >> >> -- >> :-)~MIKE~(-: >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
I don't know... it is so weird! I stepped away from the computer for the night. I thought all activity between gparted and the drive had ceased. In the morning everything was good. It was even reformatted just a few minutes ago. I think I'll run badblock on the device. On Thu, Nov 24, 2016 at 10:18 PM, Stephen Partington wrote: > Before you yank the drive from the enclosure see about using the > manufacturer software to verify the disk. > > On Nov 24, 2016 6:14 PM, "Michael Butash" wrote: > >> I'd say you have a bad unit. Try pulling the drive out of it and >> connecting it direct to a sata bus and see if that works to get a response >> to the bus. Either the drive, or the usb converter chip could be dead. >> >> I began to find at one point years ago my chances of buying those cheap >> external enclosure "backup drives" meant more than likely they would be >> doa, die soon, or otherwise cause me grief (like causing systems not to >> post with them connected) indicating some sort of electrical short. More >> often than not, usb drives are crap. >> >> What I have found is vendors sell _garbage_ drives as "usb", most have >> signfiicantly lower warranties (6mo-1yr vs 3-5yr) and mtbf rates. This >> means you're usually buying the stuff that doesn't otherwise cut muster for >> desktop or enterprise use. >> >> More simply: Expect they will die, and fast. >> >> What I do here is buy a normal desktop drive with a good warranty, get >> an enclosure myself, put it together myself, and run them this way. I >> rarely lose a disk, much better quality over all. >> -mb >> >> >> On 11/24/2016 12:03 PM, Michael wrote: >> >> >> I got a problem. This new drive won't format. Linux saw it when I first >> plugged it in. I then tried copying some files to it which resulted in an >> error appearing after 5-10 minutes telling me to open windows and run >> 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't >> figure out how to open a terminal so I decided to format it. But it >> wouldn't format. When I attempt to it flashes twice a second for a little >> then a long flash then again quickly. So I figured I would attempt the >> format with Linux but Linux doesn't see the drive now so no formatting with >> it. Can someone help? >> -- >> :-)~MIKE~(-: >> >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail >> settings:http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
Before you yank the drive from the enclosure see about using the manufacturer software to verify the disk. On Nov 24, 2016 6:14 PM, "Michael Butash" wrote: > I'd say you have a bad unit. Try pulling the drive out of it and > connecting it direct to a sata bus and see if that works to get a response > to the bus. Either the drive, or the usb converter chip could be dead. > > I began to find at one point years ago my chances of buying those cheap > external enclosure "backup drives" meant more than likely they would be > doa, die soon, or otherwise cause me grief (like causing systems not to > post with them connected) indicating some sort of electrical short. More > often than not, usb drives are crap. > > What I have found is vendors sell _garbage_ drives as "usb", most have > signfiicantly lower warranties (6mo-1yr vs 3-5yr) and mtbf rates. This > means you're usually buying the stuff that doesn't otherwise cut muster for > desktop or enterprise use. > > More simply: Expect they will die, and fast. > > What I do here is buy a normal desktop drive with a good warranty, get an > enclosure myself, put it together myself, and run them this way. I rarely > lose a disk, much better quality over all. > -mb > > > On 11/24/2016 12:03 PM, Michael wrote: > > > I got a problem. This new drive won't format. Linux saw it when I first > plugged it in. I then tried copying some files to it which resulted in an > error appearing after 5-10 minutes telling me to open windows and run > 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't > figure out how to open a terminal so I decided to format it. But it > wouldn't format. When I attempt to it flashes twice a second for a little > then a long flash then again quickly. So I figured I would attempt the > format with Linux but Linux doesn't see the drive now so no formatting with > it. Can someone help? > -- > :-)~MIKE~(-: > > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail > settings:http://lists.phxlinux.org/mailman/listinfo/plug-discuss > > > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
I'd say you have a bad unit. Try pulling the drive out of it and connecting it direct to a sata bus and see if that works to get a response to the bus. Either the drive, or the usb converter chip could be dead. I began to find at one point years ago my chances of buying those cheap external enclosure "backup drives" meant more than likely they would be doa, die soon, or otherwise cause me grief (like causing systems not to post with them connected) indicating some sort of electrical short. More often than not, usb drives are crap. What I have found is vendors sell _garbage_ drives as "usb", most have signfiicantly lower warranties (6mo-1yr vs 3-5yr) and mtbf rates. This means you're usually buying the stuff that doesn't otherwise cut muster for desktop or enterprise use. More simply: Expect they will die, and fast. What I do here is buy a normal desktop drive with a good warranty, get an enclosure myself, put it together myself, and run them this way. I rarely lose a disk, much better quality over all. -mb On 11/24/2016 12:03 PM, Michael wrote: I got a problem. This new drive won't format. Linux saw it when I first plugged it in. I then tried copying some files to it which resulted in an error appearing after 5-10 minutes telling me to open windows and run 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't figure out how to open a terminal so I decided to format it. But it wouldn't format. When I attempt to it flashes twice a second for a little then a long flash then again quickly. So I figured I would attempt the format with Linux but Linux doesn't see the drive now so no formatting with it. Can someone help? -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
Almost looks like bad sectors. Might want to try badblocks https://wiki.archlinux.org/index.php/badblocks Maybe try formatting it ext4 Maybe try another USB port and cable On Nov 24, 2016 1:21 PM, "Michael" wrote: > I really appreciate the help It errored out though. Here is what > gparted reported: > > *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( > ERROR ) > > create empty partition 00:00:00( SUCCESS ) > > > > > *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* > clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) > > write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) > write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) > write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( SUCCESS > ) > flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) > set partition type on /dev/sdd1 00:00:00( SUCCESS ) > > *new partition type: ntfs* > create new ntfs file system 00:00:37( ERROR ) > > *mkntfs -Q -v -L "NexStar" /dev/sdd1* > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Cluster size has been automatically set to 4096 bytes.Creating NTFS > volume structures.Creating root directory (mft record 5)Creating $MFT (mft > record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record > 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating > $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft > record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record > 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating > system file (mft record 0xc)Creating system file (mft record 0xd)Creating > system file (mft record 0xe)Creating system file (mft record 0xf)Creating > $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft > record 26)Syncing root directory index record.Syncing $Bitmap.Syncing > $MFT.Updating $MFTMirr.Syncing device.* > > *Failed to sync device /dev/sdd1: Input/output errorSyncing device. FAILED* > > On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington > wrote: > >> Get gparted and use it to take a look. Lots of USB drives have some wonky >> trick they use. >> >> On Nov 24, 2016 12:04 PM, "Michael" wrote: >> >>> >>> I got a problem. This new drive won't format. Linux saw it when I first >>> plugged it in. I then tried copying some files to it which resulted in an >>> error appearing after 5-10 minutes telling me to open windows and run >>> 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't >>> figure out how to open a terminal so I decided to format it. But it >>> wouldn't format. When I attempt to it flashes twice a second for a little >>> then a long flash then again quickly. So I figured I would attempt the >>> format with Linux but Linux doesn't see the drive now so no formatting with >>> it. Can someone help? >>> -- >>> :-)~MIKE~(-: >>> >>> --- >>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >>> To subscribe, unsubscribe, or to change your mail settings: >>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >>> >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > > > -- > :-)~MIKE~(-: > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
I really appreciate the help It errored out though. Here is what gparted reported: *Create Primary Partition #1 (ntfs, 232.88 GiB) on /dev/sdd* 00:00:37( ERROR ) create empty partition 00:00:00( SUCCESS ) *path: /dev/sdd1start: 2048end: 488396799size: 488394752 (232.88 GiB)* clear old file system signatures in /dev/sdd1 00:00:00( SUCCESS ) write 68.00 KiB of zeros at byte offset 0 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 67108864 00:00:00( SUCCESS ) write 4.00 KiB of zeros at byte offset 250058108928 00:00:00( SUCCESS ) flush operating system cache of /dev/sdd 00:00:00( SUCCESS ) set partition type on /dev/sdd1 00:00:00( SUCCESS ) *new partition type: ntfs* create new ntfs file system 00:00:37( ERROR ) *mkntfs -Q -v -L "NexStar" /dev/sdd1* *Cluster size has been automatically set to 4096 bytes.Creating NTFS volume structures.Creating root directory (mft record 5)Creating $MFT (mft record 0)Creating $MFTMirr (mft record 1)Creating $LogFile (mft record 2)Creating $AttrDef (mft record 4)Creating $Bitmap (mft record 6)Creating $Boot (mft record 7)Creating backup boot sector.Creating $Volume (mft record 3)Creating $BadClus (mft record 8)Creating $Secure (mft record 9)Creating $UpCase (mft record 0xa)Creating $Extend (mft record 11)Creating system file (mft record 0xc)Creating system file (mft record 0xd)Creating system file (mft record 0xe)Creating system file (mft record 0xf)Creating $Quota (mft record 24)Creating $ObjId (mft record 25)Creating $Reparse (mft record 26)Syncing root directory index record.Syncing $Bitmap.Syncing $MFT.Updating $MFTMirr.Syncing device.* *Failed to sync device /dev/sdd1: Input/output errorSyncing device. FAILED* On Thu, Nov 24, 2016 at 2:28 PM, Stephen Partington wrote: > Get gparted and use it to take a look. Lots of USB drives have some wonky > trick they use. > > On Nov 24, 2016 12:04 PM, "Michael" wrote: > >> >> I got a problem. This new drive won't format. Linux saw it when I first >> plugged it in. I then tried copying some files to it which resulted in an >> error appearing after 5-10 minutes telling me to open windows and run >> 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't >> figure out how to open a terminal so I decided to format it. But it >> wouldn't format. When I attempt to it flashes twice a second for a little >> then a long flash then again quickly. So I figured I would attempt the >> format with Linux but Linux doesn't see the drive now so no formatting with >> it. Can someone help? >> -- >> :-)~MIKE~(-: >> >> --- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
Re: new external drive
Get gparted and use it to take a look. Lots of USB drives have some wonky trick they use. On Nov 24, 2016 12:04 PM, "Michael" wrote: > > I got a problem. This new drive won't format. Linux saw it when I first > plugged it in. I then tried copying some files to it which resulted in an > error appearing after 5-10 minutes telling me to open windows and run > 'chkdsk \f' on the device. Then I plugged it into windows10 and couldn't > figure out how to open a terminal so I decided to format it. But it > wouldn't format. When I attempt to it flashes twice a second for a little > then a long flash then again quickly. So I figured I would attempt the > format with Linux but Linux doesn't see the drive now so no formatting with > it. Can someone help? > -- > :-)~MIKE~(-: > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss
