«608 »
  • Post
  • Reply
WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


ChiralCondensate posted:

Hm, 0x80041607 is QUERY_E_TIMEDOUT. How long does it run for before saying that? If you redirect the output per H110Hawk's suggestion, does it still happen? (edit: looks like it does per your new post.) How many paths are printed?
code:
Get-Content logfile | Measure-Object -Line
Some other forum post says you can increase the timeout. Try putting in
code:
    $fsSearchCon.CommandTimeout = 0
    $fsSearchCon.ConnectionTimeout = 0
before the $fsSearchCon.Open call. (Again I have no idea what I'm talking about, this might just make the whole thing hang.

The errorlog does not show any file names or directories. Is it supposed to? It only shows the error at the end in the document.

As soon as I type "blah" I see a billion names and directory names start flying by. Then after about half a minute, it stops and gives me that error.

I've never gotten the file/folder names to show up in a text document.

As per your instructions I changed the blah code to this:

code:
function Blah { 
    $global:fsSearchCon = New-Object -ComObject ADODB.Connection
    $global:fsSearchRs = New-Object -ComObject ADODB.Recordset

    Get-Content logfile | Measure-Object -Line
    $fsSearchCon.CommandTimeout = 0
    $fsSearchCon.ConnectionTimeout = 0    
    $fsSearchCon.Open("Provider=Search.CollatorDSO;Extended Properties='Application=Windows';")

    [string]$queryString = "SELECT System.ItemPathDisplay FROM SYSTEMINDEX"
    $queryString
	
    $fsSearchRs.Open($queryString, $fsSearchCon)

    While(-Not $fsSearchRs.EOF){
	# Return a FileSystemInfo object 
        # [System.IO.FileSystemInfo]$(Get-Item -LiteralPath ($fsSearchRs.Fields.Item("System.ItemPathDisplay").Value) -Force)
        $fsSearchRs.Fields.Item("System.ItemPathDisplay").Value
        $fsSearchRs.MoveNext()
    }
    $fsSearchRs.Close()
    $fsSearchCon.Close()
}
Did I do that right? I still get the error.

H110Hawk
Dec 28, 2006


WWWWWWWWWWWWWWWWWW posted:

The errorlog does not show any file names or directories. Is it supposed to? It only shows the error at the end in the document.

As soon as I type "blah" I see a billion names and directory names start flying by. Then after about half a minute, it stops and gives me that error.

I've never gotten the file/folder names to show up in a text document.

Try `1>files.txt` then? I only learned how to do powershell redirection yesterday. (Literally. And it was just the error output.)

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


H110Hawk posted:

Try `1>files.txt` then? I only learned how to do powershell redirection yesterday. (Literally. And it was just the error output.)

OK I tried that and I get this:


PS C:\Windows\system32> blah >logfile 1>files.txt
At line:1 char:15
+ blah >logfile 1>files.txt
+ ~~~~~~~~~~~
The output stream for this command is already redirected.
+ CategoryInfo : ParserError: ( [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : StreamAlreadyRedirected

ChiralCondensate
Nov 13, 2007

what is that man doing to his colour palette?


Grimey Drawer

WWWWWWWWWWWWWWWWWW posted:

The errorlog does not show any file names or directories. Is it supposed to? It only shows the error at the end in the document.

As soon as I type "blah" I see a billion names and directory names start flying by. Then after about half a minute, it stops and gives me that error.

I've never gotten the file/folder names to show up in a text document.

As per your instructions I changed the blah code to this:

code:
function Blah { 
    $global:fsSearchCon = New-Object -ComObject ADODB.Connection
    $global:fsSearchRs = New-Object -ComObject ADODB.Recordset

    Get-Content logfile | Measure-Object -Line
    $fsSearchCon.CommandTimeout = 0
    $fsSearchCon.ConnectionTimeout = 0    
    $fsSearchCon.Open("Provider=Search.CollatorDSO;Extended Properties='Application=Windows';")

    [string]$queryString = "SELECT System.ItemPathDisplay FROM SYSTEMINDEX"
    $queryString
	
    $fsSearchRs.Open($queryString, $fsSearchCon)

    While(-Not $fsSearchRs.EOF){
	# Return a FileSystemInfo object 
        # [System.IO.FileSystemInfo]$(Get-Item -LiteralPath ($fsSearchRs.Fields.Item("System.ItemPathDisplay").Value) -Force)
        $fsSearchRs.Fields.Item("System.ItemPathDisplay").Value
        $fsSearchRs.MoveNext()
    }
    $fsSearchRs.Close()
    $fsSearchCon.Close()
}
Did I do that right? I still get the error.

The
code:
Get-Content logfile | Measure-Object -Line
was just to tell how many lines were in log file, so you can take it out of Blah.

Are you running with
code:
Blah 1>files.txt 2>errlog.txt
Half a minute does make it sound like it's exceeding a timeout, but setting the timeouts to 0 were supposed to take care of that. If, in the same shell after running Blah, you type
code:
$fsSearchCon
what does the printout look like?

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


ChiralCondensate posted:

The
code:
Get-Content logfile | Measure-Object -Line
was just to tell how many lines were in log file, so you can take it out of Blah.

Are you running with
code:
Blah 1>files.txt 2>errlog.txt
Half a minute does make it sound like it's exceeding a timeout, but setting the timeouts to 0 were supposed to take care of that. If, in the same shell after running Blah, you type
code:
$fsSearchCon
what does the printout look like?

OK so here is what I am doing now, from start to finish

opening PowerShell as an admin

typing in
code:
powershell.exe -ExecutionPolicy AllSigned
and hitting enter

then typing in
code:
function Blah { 
    $global:fsSearchCon = New-Object -ComObject ADODB.Connection
    $global:fsSearchRs = New-Object -ComObject ADODB.Recordset

    $fsSearchCon.CommandTimeout = 0
    $fsSearchCon.ConnectionTimeout = 0    
    $fsSearchCon.Open("Provider=Search.CollatorDSO;Extended Properties='Application=Windows';")

    [string]$queryString = "SELECT System.ItemPathDisplay FROM SYSTEMINDEX"
    $queryString
	
    $fsSearchRs.Open($queryString, $fsSearchCon)

    While(-Not $fsSearchRs.EOF){
	# Return a FileSystemInfo object 
        # [System.IO.FileSystemInfo]$(Get-Item -LiteralPath ($fsSearchRs.Fields.Item("System.ItemPathDisplay").Value) -Force)
        $fsSearchRs.Fields.Item("System.ItemPathDisplay").Value
        $fsSearchRs.MoveNext()
    }
    $fsSearchRs.Close()
    $fsSearchCon.Close()
}
and then hitting enter

then typing in
code:
blah >logfile 2>files.txt
and hitting enter

Is that correct?

I did that and now PowerShell looks like it's doing something as the cursor has been flashing for 10 minutes (I can't type anything) and a files.txt file has been created in system32

The files.txt file is 0kb and does not seem to be growing, but I am guessing I have to wait until PowerShell finishes doing its thing?

Delthalaz
Mar 5, 2003






Slippery Tilde

Ryaath posted:

The DS918+ is great. I've had no issues with Plex transcoding, either 720p or 1080p. I typically only have 1-2 clients connected at a time though.

Cool, maybe if that makes sense for what I have in mind, I'm leaning toward going for that in the end. I was thinking I could fill it with 4 x 8tb drives and I guess use SHR2 for redundancy?

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


WWWWWWWWWWWWWWWWWW posted:

OK so here is what I am doing now, from start to finish

opening PowerShell as an admin

typing in
code:
powershell.exe -ExecutionPolicy AllSigned
and hitting enter

then typing in
code:
function Blah { 
    $global:fsSearchCon = New-Object -ComObject ADODB.Connection
    $global:fsSearchRs = New-Object -ComObject ADODB.Recordset

    $fsSearchCon.CommandTimeout = 0
    $fsSearchCon.ConnectionTimeout = 0    
    $fsSearchCon.Open("Provider=Search.CollatorDSO;Extended Properties='Application=Windows';")

    [string]$queryString = "SELECT System.ItemPathDisplay FROM SYSTEMINDEX"
    $queryString
	
    $fsSearchRs.Open($queryString, $fsSearchCon)

    While(-Not $fsSearchRs.EOF){
	# Return a FileSystemInfo object 
        # [System.IO.FileSystemInfo]$(Get-Item -LiteralPath ($fsSearchRs.Fields.Item("System.ItemPathDisplay").Value) -Force)
        $fsSearchRs.Fields.Item("System.ItemPathDisplay").Value
        $fsSearchRs.MoveNext()
    }
    $fsSearchRs.Close()
    $fsSearchCon.Close()
}
and then hitting enter

then typing in
code:
blah >logfile 2>files.txt
and hitting enter

Is that correct?

I did that and now PowerShell looks like it's doing something as the cursor has been flashing for 10 minutes (I can't type anything) and a files.txt file has been created in system32

The files.txt file is 0kb and does not seem to be growing, but I am guessing I have to wait until PowerShell finishes doing its thing?



OK so after doing the above and waiting about an hour and a half I came back and the operation is complete in PowerShell and there's nothing in files.txt. It's completely blank. Did I do something wrong?

phosdex
Dec 16, 2005



Tortured By Flan

quote:

blah >logfile 2>files.txt

files.txt is where errors are piped to, the file list should be in logfile.

Nam Taf
Jun 25, 2005

I am Fat Man, hear me roar!



If you want to dump it elsewhere, just change your directory out of system32. For example. cd / will change to the root C:. If you then run
code:
Blah >files.txt 2>errors.txt
it'll dump the file list into files.txt in C: and the errors into errors.txt.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


Nam Taf posted:

If you want to dump it elsewhere, just change your directory out of system32. For example. cd / will change to the root C:. If you then run
code:
Blah >files.txt 2>errors.txt
it'll dump the file list into files.txt in C: and the errors into errors.txt.

oh fuck yeah, this is the command that fixed it

files.txt is currently 200 MB and growing. Thanks so much to everyone in this thread. Praying my dead drive's filenames show up, and I am feeling like it most likely will

edit: welp, nope. There's only file lists for like 3 out of my 8 hard drives. I have no clue why this is. Also there's a TON of blank spaces in the files.txt. I have no clue why this is either.

There were no errors when it was done and errors.txt is completely blank

WWWWWWWWWWWWWWWWWW fucked around with this message at 05:43 on Mar 1, 2019

redeyes
Sep 14, 2002
I LOVE THE WHITE STRIPES!

Why arn't you using some data recovery software?

Heners_UK
Jun 1, 2002


redeyes posted:

Why arn't you using some data recovery software?

Sounds like there's a physical device failure element. Posts above describe that better than I can.

Although it may not be able to help here, I would have said PhotoRec, which does more than just photos (in fact I'm yet to find a common file format it doesn't do). However, to the OP has specific interest in preserving the file names of the files, which photorec doesn't do. Usually you have to recreate that from metadata.

Flipperwaldt
Nov 11, 2011

Won't somebody think of the starving hamsters in China?



Voidtools Everything search uses the ntfs content table for filenames. If the drive still mounts locally, you might be able to export a list from that?

H110Hawk
Dec 28, 2006


Heners_UK posted:

Sounds like there's a physical device failure element. Posts above describe that better than I can.

Although it may not be able to help here, I would have said PhotoRec, which does more than just photos (in fact I'm yet to find a common file format it doesn't do). However, to the OP has specific interest in preserving the file names of the files, which photorec doesn't do. Usually you have to recreate that from metadata.

This is my go-to as well, but if the heads won't go out over the platter it's a non-starter. You're immediately into platter+controller transplant and hoping the new motor/heads are aligned close enough. (Assuming our internet webmd skills are correct based upon his description.)

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


Yeah I'm screwed on the drive. I can't get it to read anything

I know this blah. Powershell trick will work. The first time I ran it I saw a list of files on the dead drive show up. But I can't figure out why it won't show up in the text document. The text document is leaving out entire drives that still work and are connected. he;lp

bobfather
Sep 20, 2001

I will analyze your nervous system for beer money

HereÂ’s a different perspective: if the data that are gone were not mission critical and you canÂ’t even remember five things that were on the drive, just learn a lesson and let it go.

Edit: that lesson being, keep a backup of any data that are important to you.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


Yes I learned my lesson and will back up in the future but I know my mentality and this will haunt me for the next 5-7 years so please I beg of you I'm so close, just help me figure out why only a small amount of file names show up in files.txt, I'm begging like that cop in Reservoir Dogs over here

Heners_UK
Jun 1, 2002


WWWWWWWWWWWWWWWWWW posted:

Yes I learned my lesson and will back up in the future but I know my mentality and this will haunt me for the next 5-7 years so please I beg of you I'm so close, just help me figure out why only a small amount of file names show up in files.txt, I'm begging like that cop in Reservoir Dogs over here

Again, but with special emphasis on calming the anxiety you clearly feel about having something occur to you that was on that drive: If this was mostly easily downloadable Linux ISOs or similar, I'd spend the money on a decent internet connection and an automatic solution to find and download them. You can have a decent movie collection recreated in the time we've taken talking about this in this thread, and should a Linux ISO occur to you that you want, it can be downloaded and ready to use on your 1920x1080 monitor in under an hour. It can be so easy that you just grab your phone as soon as it occurs to you, type in the ISO name and your computer searches and downloads for you. I've lost Linux ISOs before, willfully in some cases, and don't mind recreating my archive every so often.

If however these were home movies only you have and are truly irreplaceable: Time to call a data recovery firm and get the wallet out. I know you're asking for the bare minimum here (just file names, a simple request) but your drive sounds like it will not physically start up to give any OS that information.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


I live in a 3rd world shithole with abysmal download speeds. But the biggest issue is a lot of the stuff on the drive was named things like "Remember to upload this folder to the PS2 hard drive" and "good games to play some day" and "movies I heard were good" or something and I'm never going to remember them because the file names and folder names themselves were my reminders. I think it's reasonable to believe I can get these file names because I saw my dead drive's file names yesterday flying by at lightning speed in PowerShell. You guys already helped me out so much. It's just that I simply can't get them to show up in a text document is all. It would be beyond ridiculous for me to give up at this point.

I luckily have a copy of the index .EDB file on another computer from before I dropped the now-dead hard drive because at the same time I dropped the drive I was cloning an old mechanical 1TB HD to a 1TB SSD, so I have a completely untouched .EDB file that still thinks the dead drive is working. There has to be some way to get this info from it; in fact I am pretty sure this thread proved I can. I might be a stubborn bastard but I want to be a stubborn bastard that will see file names such as "F:\Movies that are supposed to be good to check out\Freaked (1993).iso", again someday

WWWWWWWWWWWWWWWWWW fucked around with this message at 21:33 on Mar 1, 2019

H110Hawk
Dec 28, 2006


WWWWWWWWWWWWWWWWWW posted:

I live in a 3rd world shithole with abysmal download speeds. But the biggest issue is a lot of the stuff on the drive was named things like "Remember to upload this folder to the PS2 hard drive" and "good games to play some day" and "movies I heard were good" or something and I'm never going to remember them because the file names and folder names themselves were my reminders. I believe it's reasonable to believe I can get these file names because I saw my dead drive's file names yesterday flying by at lightning speed in PowerShell. I just can't get them to show up in a text document is all. It would be beyond ridiculous for me to give up at this point.

I have the index .EDB file on another computer from before I dropped the now-dead hard drive because at the same time I dropped the drive I was cloning an old mechanical 1TB HD to a 1TB SSD, so I have a completely untouched .EDB file that still thinks the dead drive is working. There has to be some way to get this info from it; in fact I am pretty sure this thread proved I can. I might be a stubborn bastard but I want to be a stubborn bastard that will see file names such as "F:\Movies that are supposed to be good to check out\Freaked (1993).iso", again someday

https://www.edbsearch.com/description.html something like this maybe?

Greatest Living Man
Jul 22, 2005

ask President Obama


WWWWWWWWWWWWWWWWWW posted:

I live in a 3rd world shithole with abysmal download speeds. But the biggest issue is a lot of the stuff on the drive was named things like "Remember to upload this folder to the PS2 hard drive" and "good games to play some day" and "movies I heard were good" or something and I'm never going to remember them because the file names and folder names themselves were my reminders. I think it's reasonable to believe I can get these file names because I saw my dead drive's file names yesterday flying by at lightning speed in PowerShell. You guys already helped me out so much. It's just that I simply can't get them to show up in a text document is all. It would be beyond ridiculous for me to give up at this point.

I luckily have a copy of the index .EDB file on another computer from before I dropped the now-dead hard drive because at the same time I dropped the drive I was cloning an old mechanical 1TB HD to a 1TB SSD, so I have a completely untouched .EDB file that still thinks the dead drive is working. There has to be some way to get this info from it; in fact I am pretty sure this thread proved I can. I might be a stubborn bastard but I want to be a stubborn bastard that will see file names such as "F:\Movies that are supposed to be good to check out\Freaked (1993).iso", again someday

It's a good movie.

Flipperwaldt
Nov 11, 2011

Won't somebody think of the starving hamsters in China?



On the surface this looks like a tool for edb files as well:

https://www.nirsoft.net/utils/ese_database_view.html

Can vouch for Nirsoft making useful free tools in general anyway.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


Flipperwaldt posted:

On the surface this looks like a tool for edb files as well:

https://www.nirsoft.net/utils/ese_database_view.html

Can vouch for Nirsoft making useful free tools in general anyway.



Unfortunately I already tried both of these programs before posting here. Unless there's something I'm missing, after messing around with both of them for several hours the most I could "discover" is a mess of shit like this:




Like I can see the raw hex values of everything with no problem but trying to figure out the filenames contained within apparently requires some sort of bachelor's degree that I don't have

edit: I hope I am not coming off as a dillweed; I'm just frustrated with being such a failure

WWWWWWWWWWWWWWWWWW fucked around with this message at 00:00 on Mar 2, 2019

ughhhh
Oct 17, 2012



edit: realized i had already posted my question a long time ago and forgot about it.

Any recommendation on an ITX case?

ughhhh fucked around with this message at 00:34 on Mar 2, 2019

Matt Zerella
Oct 7, 2002


ughhhh posted:

So i have leftover parts from my old build and was thinking about building a NAS/Plex/torrent box with it. Was thinking that i would have it on 24/7 and transferring all my media onto it and steaming it throughout the apartment (to the TV, roomates laptop etc) and scheduling torrents etc.

I currently have :

Intel - Core i5-4590
ASRock - Z97E-ITX
8gb DDR3-1600
1tb WD blue x2

Was thinking i could use this as a base and buy a small case and a cheap psu/ssd and build from that. Is this good enough for what i plan on doing? Any suggestions on where to go forward with this?

I'm running UnRAID on that with 32 gigs of ram, 4x6tb reds and 2 SSDs (one dedicated to plex, one is the array cache).

It's a good setup and you've got a good base to work off of. You have options for OS but I'm an UnRAID fanboy so that's always going to be my recommendation.

Plex/sonarr/radarr/utorrent are all running as dockers and I have a few VMs running for work stuff that I turn off and on as needed.

ughhhh
Oct 17, 2012



Cool! 8gb should suffice for my needs right? I'm working with an itx mobo so I am limited to 2 ram slots.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


ughhhh posted:

edit: realized i had already posted my question a long time ago and forgot about it.

Any recommendation on an ITX case?

I just got a Fractal Design case for my setup (the one where I dropped the damn hard drive) and I have to say it is the greatest and most beautifully engineered case I ever bought

Mr. Crow
May 22, 2008

Snap City mayor for life


Holy shit Powershell is an abomination

Matt Zerella
Oct 7, 2002


ughhhh posted:

Cool! 8gb should suffice for my needs right? I'm working with an itx mobo so I am limited to 2 ram slots.

More than enough.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


Somehow during this fucking case swap not only did an 8tb hard drive die but a the IBM 8 port SATA card that I flashed with the IT firmware. How a goddamn card dies during a case swap, I have no idea.

So I just ordered a DELL PERC H310. I am gonna flash it to IT mode but some people are saying online that I have to put electrical tape over pins 4 and 5? Is this correct? Why is it such a convoluted mess to get 8 SATA ports?

apropos man
Sep 5, 2016

You get a hundred and forty one thousand years and you're out in eight!

Maybe it's time to replace that nylon carpet and stop wearing a rubber johnny on your head?

astral
Apr 26, 2004



H110Hawk posted:

Next time don't pet a static generator (cat) while working with sensitive electronics.

This one.

qutius
Apr 2, 2003
NO PARTIES


Mr. Crow posted:

Holy shit Powershell is an abomination

Except it's really not?

H110Hawk
Dec 28, 2006


qutius posted:

Except it's really not?

It feels that way coming from a Linux world but most of that is just that windows is horrifyingly laid out in comparison. I know in my heart it's good but not knowing all the nuances of wmi vs the other crap makes me want to claw my eyes out.

WWWWWWWWWWWWWWWWWW
Dec 6, 2014

CUCK SJW


qutius posted:

Except it's really not?

Can you help me with my Powershell issue please good friend? It's dumping thousands of file names in files.txt for me but a shitload are missing and I know they should be there because my indexing EDB file is 14 gigs and I'm only getting a 200mb files.txt

Red_Fred
Oct 21, 2010



Fallen Rib

Does anyone know how to fix the issue with Windows 10 and prompting for a password on boot for a network drive? Looks like I have to mess with credentials manager however I have the home version which doesn't have credentials manager.

I've tried some of the suggestions in here. No dice though.

D. Ebdrup
Mar 13, 2009



H110Hawk posted:

It feels that way coming from a Linux world but most of that is just that windows is horrifyingly laid out in comparison. I know in my heart it's good but not knowing all the nuances of wmi vs the other crap makes me want to claw my eyes out.
PowerShell just has a syntax that is utterly different from Unix-likes (which Linux is getting further away from, as well) - but it does have all the features one wants in a shell in the form of stdio, piping/redirection, path and command completion (the latter is something I find myself missing a lot on shells that aren't tcsh or don't offer Tenex-style completion in the runcom file). All that being said, I still have a hard time getting used to its syntax.

H110Hawk
Dec 28, 2006


D. Ebdrup posted:

PowerShell just has a syntax that is utterly different from Unix-likes (which Linux is getting further away from, as well) - but it does have all the features one wants in a shell in the form of stdio, piping/redirection, path and command completion (the latter is something I find myself missing a lot on shells that aren't tcsh or don't offer Tenex-style completion in the runcom file). All that being said, I still have a hard time getting used to its syntax.

And powershell's in line help and examples are a clear winner compared to Linux shells.

priznat
Jul 7, 2009

Let's get drunk and kiss each other all night.

Microsoft is going both ways with adding bash support too so you can use whichever you prefer!

D. Ebdrup
Mar 13, 2009



H110Hawk posted:

And powershell's in line help and examples are a clear winner compared to Linux shells.
Yeah, I've been making use of that quite a lot in learning it - although I don't like the way their help system is implemented; gimme something accessible from a command that I can pipe to a pager of my choice, damn it!

priznat posted:

Microsoft is going both ways with adding bash support too so you can use whichever you prefer!
Yeah, it's a weird world we live in.
I'd rather learn PowerShell than have to deal with bash, though. I use tcsh for interactivity and likely won't change unless a different shell offers me enough additional functionality beyond what I already get, for it to be worth it. For shell scripting, there is only the bourne shell until the POSIX standard changes.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply
«608 »