[gentoo-user] Re: smartctrl drive error @60%
Mick writes: > echo "My first test message" | mail -v -s "Test for sSMTP 1" d...@gmail.com What about trying echo "My first test message" | mail -v -s "Test for sSMTP 1" root directly? Therefore you can see if your aliases are correct. -- Alberto
[gentoo-user] Re: smartctrl drive error @60%
On 2014-06-25, Dale wrote: > I have to say, I dread setting up a mail server about as bad as I dread > going to the Doctor. It's just something I really don't want to add to > my system unless I have to. It's sort of like the init thingy. I don't > want to add something else that will eventually break and I'll have to > fix. The mail system won't keep me from booting but it is just one more > thing to keep a eye on and make sure it is working. So, making sure the > mail system is working will likely take up the same amount of time that > checking the drive manually every month or so will take. I think you are _vastly_ overestimating the amount of effort required to install and set up something like msmtp. It's completely trivial compared to setting up sendmail (or even postfix). If you know the name of your ISP's smtp server along with the username and password, it doesn't take more than a minute or two to set up. And it just doesn't break (unless you change the password and forget to update the msmtp config file). -- Grant Edwards grant.b.edwardsYow! I'm having a at quadrophonic sensation gmail.comof two winos alone in a steel mill!
[gentoo-user] Re: smartctrl drive error @60%
On 2014-06-27, Neil Bothwick wrote: > On Fri, 27 Jun 2014 14:22:09 +0100, Mick wrote: > >>> You tell cron where to mail reports by setting MAILTO=you@wherever at >>> the top of /etc/crontab. It will then mail you every time a cronjob >>> produces output. >> >> Or complete the /etc/ssmtp/ssmtp.conf and revaliases with the info I >> have sent you in this thread and set MAILTO=root in your >> /etc/crontab. >> >> I would think that your ISP providers in the US will be blocking >> outgoing port 25 to stop compromised MSWindows machines spamming the >> rest of us. If you use my suggestion there shouldn't be a problem. > > It makes no difference whether you address it directly to your ISP > address or via an alias. The ISP won't block port 25 connections to > its own servers from its own customers, otherwise none of them could > send email at all! They _might_ block port 25 and require you to use SMTP/SSL on port 465. More likely, they would still allow an initial plaintext connection to port 25 and require use of the starttls command. -- Grant Edwards grant.b.edwardsYow! I wonder if I could at ever get started in the gmail.comcredit world?
Re: [gentoo-user] Re: smartctrl drive error @60%
On Fri, Jun 27, 2014 at 5:26 PM, Grant Edwards wrote: > They _might_ block port 25 and require you to use SMTP/SSL on port > 465. More likely, they would still allow an initial plaintext > connection to port 25 and require use of the starttls command. Check with your ISP. The rules vary. I have Verizon FIOS and I'm pretty sure they block port 25 from their own customers regardless of TLS. I guess that must means the virus writers have to write an extra 5 lines of code to extract the password from the configuration of whatever email software is in use... Rich
Re: [gentoo-user] Re: smartctrl drive error @60%
Grant Edwards wrote: > On 2014-06-25, Dale wrote: > >> I have to say, I dread setting up a mail server about as bad as I dread >> going to the Doctor. It's just something I really don't want to add to >> my system unless I have to. It's sort of like the init thingy. I don't >> want to add something else that will eventually break and I'll have to >> fix. The mail system won't keep me from booting but it is just one more >> thing to keep a eye on and make sure it is working. So, making sure the >> mail system is working will likely take up the same amount of time that >> checking the drive manually every month or so will take. > I think you are _vastly_ overestimating the amount of effort required > to install and set up something like msmtp. It's completely trivial > compared to setting up sendmail (or even postfix). If you know the > name of your ISP's smtp server along with the username and password, > it doesn't take more than a minute or two to set up. And it just > doesn't break (unless you change the password and forget to update the > msmtp config file). > It was more Murphy's law I was worried about. ;-) Dale :-) :-)
Re: [gentoo-user] Re: smartctrl drive error @60%
On Sat, 28 Jun 2014 06:55:28 -0500, Dale wrote: > It was more Murphy's law I was worried about. ;-) Hasn't that been deprecated in favour of Dale's Law? -- Neil Bothwick I thought the 10 commandments were multiple choice. signature.asc Description: PGP signature
Re: [gentoo-user] Re: smartctrl drive error @60%
Neil Bothwick wrote: > On Sat, 28 Jun 2014 06:55:28 -0500, Dale wrote: > >> It was more Murphy's law I was worried about. ;-) > Hasn't that been deprecated in favour of Dale's Law? > > If it hasn't, maybe it should. It's strange tho, I have good luck with a lot of things, even computer hardware really, but messing with some new software generally leads to trouble. Hal was the first really bad thing. There was some other thing that popped up that I can't recall and recently the init thingy kept me from booting. I then booted the init thingy off here. I just keep a up to date Kubuntu disk laying around. ;-) New software just doesn't like me or my rig much. Older stuff seems to work fine. It's the things that seem to be new that really crawl under my skin. It seems they always bite me even when it works for most everyone else. That was pretty much the case with hal. It just would not work on my rig. I give the dev credit tho, he realized it was a mess and started over from scratch. At least he realized the boo boo. On this old drive. I got my data copied over and tested the stuffin out of the new drive and then tested it a few more times. Looks good for the new drive. I'm doing a dd on the old drive now and I plan to let it at least get to where that bad spot is. I figure if I let dd do its thing on the whole drive, that should get it, unless I lose power or something and have to stop it. After that, I'm going to put a file system on it and fill it up and test it and see what it says then. Maybe it will fix itself and I can at least use it as a occasional backup or something. I dunno. I noticed when I copied the data over that some files had a line of question marks in the name. Since a question mark is a wild card, I can't find them now. How does one search for a file name that has a wild card in it? Dale :-) :-)
Re: [gentoo-user] Re: smartctrl drive error @60%
On 28/06/2014 15:05, Dale wrote: > Neil Bothwick wrote: >> On Sat, 28 Jun 2014 06:55:28 -0500, Dale wrote: >> >>> It was more Murphy's law I was worried about. ;-) >> Hasn't that been deprecated in favour of Dale's Law? >> >> > > If it hasn't, maybe it should. It's strange tho, I have good luck with > a lot of things, even computer hardware really, but messing with some > new software generally leads to trouble. Hal was the first really bad > thing. There was some other thing that popped up that I can't recall > and recently the init thingy kept me from booting. I then booted the > init thingy off here. I just keep a up to date Kubuntu disk laying > around. ;-) New software just doesn't like me or my rig much. Older > stuff seems to work fine. It's the things that seem to be new that > really crawl under my skin. It seems they always bite me even when it > works for most everyone else. That was pretty much the case with hal. > It just would not work on my rig. I give the dev credit tho, he > realized it was a mess and started over from scratch. At least he > realized the boo boo. > > On this old drive. I got my data copied over and tested the stuffin out > of the new drive and then tested it a few more times. Looks good for > the new drive. I'm doing a dd on the old drive now and I plan to let it > at least get to where that bad spot is. I figure if I let dd do its > thing on the whole drive, that should get it, unless I lose power or > something and have to stop it. After that, I'm going to put a file > system on it and fill it up and test it and see what it says then. > Maybe it will fix itself and I can at least use it as a occasional > backup or something. I dunno. > > I noticed when I copied the data over that some files had a line of > question marks in the name. Since a question mark is a wild card, I > can't find them now. How does one search for a file name that has a > wild card in it? escape the character with a \ But that's not your main problem. You got those filenames because the source disk somehow has a problem and the names couldn't be read properly. So junk was used instead. Reasons vary, but the basics never change: there is a problem with your source disk and now you need to go find what that problem is. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: smartctrl drive error @60%
Alan McKinnon wrote: > On 28/06/2014 15:05, Dale wrote: >> On this old drive. I got my data copied over and tested the stuffin out >> of the new drive and then tested it a few more times. Looks good for >> the new drive. I'm doing a dd on the old drive now and I plan to let it >> at least get to where that bad spot is. I figure if I let dd do its >> thing on the whole drive, that should get it, unless I lose power or >> something and have to stop it. After that, I'm going to put a file >> system on it and fill it up and test it and see what it says then. >> Maybe it will fix itself and I can at least use it as a occasional >> backup or something. I dunno. >> >> I noticed when I copied the data over that some files had a line of >> question marks in the name. Since a question mark is a wild card, I >> can't find them now. How does one search for a file name that has a >> wild card in it? > > escape the character with a \ > > But that's not your main problem. You got those filenames because the > source disk somehow has a problem and the names couldn't be read > properly. So junk was used instead. > > Reasons vary, but the basics never change: there is a problem with your > source disk and now you need to go find what that problem is. > Well, the drive is replaced but it copied the "bad" file over as well. I just want to find it so that I can check it and delete it if it is bad. It's one of my videos so no point in some corrupted file hanging around if it is no good. Plus, I hope I can figure out what is missing and find a copy on youtube or something. Maybe I will be that lucky. Now to go see if I can find it again. ;-) Thanks. Dale :-) :-)
Re: [gentoo-user] Re: smartctrl drive error @60%
Dale wrote: > Alan McKinnon wrote: >> On 28/06/2014 15:05, Dale wrote: >>> On this old drive. I got my data copied over and tested the stuffin out >>> of the new drive and then tested it a few more times. Looks good for >>> the new drive. I'm doing a dd on the old drive now and I plan to let it >>> at least get to where that bad spot is. I figure if I let dd do its >>> thing on the whole drive, that should get it, unless I lose power or >>> something and have to stop it. After that, I'm going to put a file >>> system on it and fill it up and test it and see what it says then. >>> Maybe it will fix itself and I can at least use it as a occasional >>> backup or something. I dunno. >>> >>> I noticed when I copied the data over that some files had a line of >>> question marks in the name. Since a question mark is a wild card, I >>> can't find them now. How does one search for a file name that has a >>> wild card in it? >> escape the character with a \ >> >> But that's not your main problem. You got those filenames because the >> source disk somehow has a problem and the names couldn't be read >> properly. So junk was used instead. >> >> Reasons vary, but the basics never change: there is a problem with your >> source disk and now you need to go find what that problem is. >> > Well, the drive is replaced but it copied the "bad" file over as well. > I just want to find it so that I can check it and delete it if it is > bad. It's one of my videos so no point in some corrupted file hanging > around if it is no good. Plus, I hope I can figure out what is missing > and find a copy on youtube or something. Maybe I will be that lucky. > > Now to go see if I can find it again. ;-) > > Thanks. > > Dale > > :-) :-) > Hm, slight glitch maybe. It listed some files with a question mark in it but not the ones I am looking for. So, is it possible that since it couldn't read the file it just skipped them? I used rsync to do the copy instead of cp. Maybe that is it or otherwise, I have a ton of directories to go diggin in to find them since it isn't the one I thought it was. Dale :-) :-)
Re: [gentoo-user] Re: smartctrl drive error @60%
On Saturday 28 June 2014 09:15:47 Dale wrote:
> > Alan McKinnon wrote:
--->8
> >> But that's not your main problem. You got those filenames because the
> >> source disk somehow has a problem and the names couldn't be read
> >> properly. So junk was used instead.
I thought it was more like: the file lister didn't recognise those bytes as
valid characters so it printed a question-mark for each of them. If it is so,
it's no use Dale looking for files with question-marks in their names.
--->8
> It listed some files with a question mark in it but not the ones I am
> looking for. So, is it possible that since it couldn't read the file it
> just skipped them?
It may not be true that it couldn't read the files; it just couldn't translate
their names into text characters. The names are not held in the files whose
names they are but somewhere in the inode structure. Someone with better
knowledge of this (i.e.any at all) will have to explain what goes wrong if
bytes on the disk adjacent to the file names get damaged along with the names.
> I used rsync to do the copy instead of cp. Maybe that is it or otherwise, I
> have a ton of directories to go diggin in to find them since it isn't the
> one I thought it was.
Do you know any characters in those dodgy names, Dale? If so, you may be able
to use /usr/bin/find like so (hoping this isn't a grandma's egg - apologies if
it is):
find /path-to-files -iname \*known-part-of-name\* {} +
--
Regards
Peter
Re: [gentoo-user] Re: smartctrl drive error @60%
On Saturday 28 Jun 2014 15:50:23 Peter Humphrey wrote:
> On Saturday 28 June 2014 09:15:47 Dale wrote:
> > > Alan McKinnon wrote:
> --->8
>
> > >> But that's not your main problem. You got those filenames because the
> > >> source disk somehow has a problem and the names couldn't be read
> > >> properly. So junk was used instead.
>
> I thought it was more like: the file lister didn't recognise those bytes as
> valid characters so it printed a question-mark for each of them. If it is
> so, it's no use Dale looking for files with question-marks in their names.
>
> --->8
>
> > It listed some files with a question mark in it but not the ones I am
> > looking for. So, is it possible that since it couldn't read the file it
> > just skipped them?
>
> It may not be true that it couldn't read the files; it just couldn't
> translate their names into text characters. The names are not held in the
> files whose names they are but somewhere in the inode structure. Someone
> with better knowledge of this (i.e.any at all) will have to explain what
> goes wrong if bytes on the disk adjacent to the file names get damaged
> along with the names.
>
> > I used rsync to do the copy instead of cp. Maybe that is it or
> > otherwise, I have a ton of directories to go diggin in to find them
> > since it isn't the one I thought it was.
>
> Do you know any characters in those dodgy names, Dale? If so, you may be
> able to use /usr/bin/find like so (hoping this isn't a grandma's egg -
> apologies if it is):
>
> find /path-to-files -iname \*known-part-of-name\* {} +
It could have something to do with the character set of the
terminal/application Vs the character set that the original file was created
as. If you have UTF8 set as your default character encoding, you should
hopefully be OK. If it shows ? in the name and 0 bytes size, it is likely a
corrupt file.
You can also try ddrescue with --input-position= and --max-size=
to retrieve just the borked part of the disk.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: smartctrl drive error @60%
Mick wrote:
> On Saturday 28 Jun 2014 15:50:23 Peter Humphrey wrote:
>> It may not be true that it couldn't read the files; it just couldn't
>> translate their names into text characters. The names are not held in
>> the files whose names they are but somewhere in the inode structure.
>> Someone with better knowledge of this (i.e.any at all) will have to
>> explain what goes wrong if bytes on the disk adjacent to the file
>> names get damaged along with the names. Do you know any characters in
>> those dodgy names, Dale? If so, you may be able to use /usr/bin/find
>> like so (hoping this isn't a grandma's egg - apologies if it is):
>> find /path-to-files -iname \*known-part-of-name\* {} +
> It could have something to do with the character set of the
> terminal/application Vs the character set that the original file was created
> as. If you have UTF8 set as your default character encoding, you should
> hopefully be OK. If it shows ? in the name and 0 bytes size, it is likely a
> corrupt file.
>
> You can also try ddrescue with --input-position= and
> --max-size=
> to retrieve just the borked part of the disk.
Well, I was planing to just find them and delete them. If I could play
them and they work fine then I might save them but I figure they are
likely messed up in some way.
I have already zeroed out the stuff on the old drive that was going
out. That data is gone. If rsync didn't copy the files over, that is
cool. I'll go figure out what was missed and see if I can find new
copies. I only saw a chunk that looked like maybe 4 or 5 scrolling by.
Given the amount of data, I'd say it was well under a 1% loss. Maybe
not even 0.1% loss.
Learned to use the \ to search tho. Let's see if I remember that for
next time. lol
Dale
:-) :-)
