I've looked around these boards for the last couple of days and if it's there I'm just missing it.

 

My question is simple (I think):

 

How to I actually look at my badblocks OR preclear_disk report?

 

For badblocks, I ran this:

badblocks -sv -w -o /tmp/badblocks.sdl.out /dev/sdl

 

If I look in /tmp, I see it.  But how do I look at it?

 

For preclear_disk.sh, I ran this:

preclear_disk.sh -M 4 -c 3 /dev/sdd

 

When I look in /boot/preclear_reports (via ls /boot/preclear_reports) I see this:

preclear_finish_\ WD-WCAZAH7799111_2012-10-30*
preclear_rpt_\ WD-WCAZAH799111_2012-10-30*
preclear_start_\ WD-WCAZAH799111_20120-10-30*

 

How do look at those?

 

Thanks,

~Whip

I usually just rename the files and put a .txt on the end to make it easier for Windows to open them.

 

But they are just text files so you can use any text editor to open them.  I use Windows Notepad.

Since /tmp is not accessible via windows or a share, i suppose i could copy the file to /boot/something and look at it there?

 

Also, specifically with regard to the preclear reports - when I'm in the console and I do a "ls /boot/preclear_reports" the listing that I see has a backslash ("\") followed by a space - is that a file name?  If so, how do I look at it because vi /boot/preclear_reports/preclear_rpt_\ WD-WCAZAH799111_2012-10-30* just gives me an error.

Since /tmp is not accessible via windows or a share, i suppose i could copy the file to /boot/something and look at it there?

yes, that would do.

 

Also, specifically with regard to the preclear reports - when I'm in the console and I do a "ls /boot/preclear_reports" the listing that I see has a backslash ("\") followed by a space - is that a file name?  If so, how do I look at it because vi /boot/preclear_reports/preclear_rpt_\ WD-WCAZAH799111_2012-10-30* just gives me an error.

 

The "\" would be just a regular character to Linux, but it is a rather poor choice given that it is bound to cause issues for windows users.  It may even be a bad character for the Linux shell as it is often used as an "escape" character, so you might have to type "\\" to actually get a single "\".  I would just rename the report file to something simpler while in the Linux environment (which you can do at the same time as moving or copying it to a different location).

 

Regards,

 

Stephen

Just to make sure I understand this correctly, I could try a couple different things to be able to read the preclear report.  While in the console for unRaid I could:

 

Try opening the file in vi by typing

vi /boot/preclear_reports/preclear_rpt_\ WD-WCAZAH799111_2012-10-30*

If that gives me an error again, I would try using /preclear_rpt_\\ and see if that works.

 

I could try to move/renaming the file:

mv /boot/preclear_reports/preclear_rpt_\ WD-WCAZAH799111_2012-10-30* /boot/preclear_reports/preclear_rpt_WCAZAH.txt

I could try the double "\\" if that gives me an error.

 

Does that seem appropriate?

 

One thing I can't figure out yet are the colors I see when I'm logged in unRaid via the console.  When I do "ls" against a given directory, some of the items in the list are GREEN.  Does that mean it is executable (I only guess this because preclear_disk.sh shows up green)?

 

Thanks for help and patience while I learn my way around unRaid.

 

~Whip

One thing I can't figure out yet are the colors I see when I'm logged in unRaid via the console.  When I do "ls" against a given directory, some of the items in the list are GREEN.  Does that mean it is executable (I only guess this because preclear_disk.sh shows up green)?

Yep.

I have some folders and files which originally came from Windows with embedded spaces in the names and when I use ls to see them on unRAID through telnet they are always shown with \ preceding the space so I think the \ is just escaping the embedded space.

I have some folders and files which originally came from Windows with embedded spaces in the names and when I use ls to see them on unRAID through telnet they are always shown with \ preceding the space so I think the \ is just escaping the embedded space.

 

doh.  Hadn't thought of that.  That would make sense.  Thanks!

 

~Whip

Thanks for all the help!

 

I have some folders and files which originally came from Windows with embedded spaces in the names and when I use ls to see them on unRAID through telnet they are always shown with \ preceding the space so I think the \ is just escaping the embedded space.

 

Turns out that is exactly what it was.