I have booted ubuntu and it can see the drive however when i try to access get message
Unable to access “Seagate8TB1”
Error mounting/dev/sdd1 at/media/ubuntu/Seagate8TB1:can’t read superblock on /dev/sdd1
Also if relevant i had to unplug vero as it needed resetting before all this started
This means the drive is corrupted
Are you using a custom enclosure or did the disk come in a case etc already?
Sam
In a case
This is the problem. Seagate drives are notorious for corruption when not properly shutdown. Trust me, I’ve gone thru this on another thread asking questions on the safety of the drives due to the Vero always in the “ON” state. If for whatever reason the drives are being accessed and there is a power failure on improper shutdown, you will stand the chance of corruption. It’s even happened to me with WD drives too.
I’m assuming you have a Windows PC?
Your drives in Windows should be showing as “Healthy (Primary Partition)” in Disk Management and not as “Unallocated”.
Since you can’t access the drives you have 2 options:
- Use a file recovery program to save and recover your files.
- Reformat the drives, which you will lose all your files.
I feel for you, I’ve been down this road many of times. I’ve lost terabytes of files due to this.
My suggestions to you for the future.
- Keep backups on another drive of all you very important files (movies, pics, etc.)
- ALWAYS and I mean ALWAYS safely remove the drive from the Vero, PC or any other device that is using the external hard drive. NEVER leave your external drives hooked up to ANYTHING unless your using them. I’ve had external drives become corrupt due to power loss even on Windows PC.
I want to make clear that is no fault of the Vero. This is the fault of the drives, until the manufacturers can implement better safety measures for power loss, this will always be a problem. But then again maybe they designed it that way to sell more drives.
I have started the recovery this morning just another 15 hours or so to go
Will also be taking your advise on when nit using the drives to safely remove them when not in use
However after they have been removed from the vero they still have lights on, i tske it they are ok in this state or do you recommend after being safely removed that then the power is also switched off?
Then regarding re mounting is it best to reboot the vero?
When i have recovered files is it just a case of re formatting the drive and it will be ok?
I do not want to go down this road again
Very time consuming
Many thanks for reply
The light being on (Steady) means there is just power to the drive. You don’t have to unplug the drive, unless you want to switch them off. Some drives will blink meaning they are in a standby state (slow blink). But then it’s hard to tell if they are being accessed too.
The good thing about Vero is you don’t have to shut down the Vero. You can just reattach the drives and they will remount.
Yes, Hopefully after you recovered your files, do a complete reformat and keep your fingers crossed that the drives will be alright. Do a test first, Just put one movie on the drives and see if Vero can acces them. If all else fails you can return or warranty them.
Did you miss the part where he said this was a ext4 formatted drive?
That not how it works, and you don’t know that the power cycling had anything to do with the file corruption. I don’t imagine he rebooted by pulling the power cord because everything was working as it should.
On a separate note to the Linux pros is there a reason why it had not been recommended he try running fsck -y on this drive?
Because, IIRC, the superblock cannot be found from a mount attempt, so fsck will surely fail.
Well, he can try using the spare (backup_ superblocks). Every ext2/3/4 filesystem has some.
Or fix the superblocks: http://shearer.org/Ext4_recovery
Yes, he can. Should be multiples of 16384 by default.
I have looked at that but don’t understand it
Tried to use the commands and it did appear to be checking the superblocks
Then when finished, another list of commands was displayed
The data recovery programme i used must only work on ntfs and fat as when finished there was over 2000 files found none biggef than 4gb
Can someone reccomend a data recovery programme for ext4
Just tried raise recovery free version and it shows all files im after recovering
Anyone used this before?
You might try the following before going through the whole data recovery route again.
First find the device name of your drive by running the following either with the Linux live disk or your Vero.
fdisk -l
If your drive is showing as /dev/sdd then you would run
sudo fsck -y /dev/sdd
and hopefully that will fix the superblock issue. I’ve not tried it but the post I found this info in cured the issue for that person. Note that you would be running this on the drive (ie /dev/sdd) and not the messed up partition itself (ie /dev/sdd1). To the best of my knowledge this command will only touch the partition tables so if it does not work then it should have no impact on being able to recover files with another method.
You should be able to copy the text from the terminal and paste it here, which makes it easier to read and saves space.
You will need to prefix your commands with ‘sudo’, i.e. sudo e2fsck …
You could try using
32768, 98304, 163840, 229376, 294912
/dev/sda1 2048 15628053133 15628051086 7.3T Linux filesystem
osmc@osmc:~$ sudo fsck -y /dev/sda1
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
Seagate8TB1: recovering journal
JBD2: Invalid checksum recovering block 327 in log
JBD2: Invalid checksum recovering block 328 in log
JBD2: Invalid checksum recovering block 328 in log
JBD2: Invalid checksum recovering block 328 in log
JBD2: Invalid checksum recovering block 329 in log
JBD2: Invalid checksum recovering block 332 in log
JBD2: Invalid checksum recovering block 332 in log
JBD2: Invalid checksum recovering block 332 in log
JBD2: Invalid checksum recovering block 333 in log
JBD2: Invalid checksum recovering block 333 in log
JBD2: Invalid checksum recovering block 333 in log
JBD2: Invalid checksum recovering block 333 in log
JBD2: Invalid checksum recovering block 334 in log
JBD2: Invalid checksum recovering block 335 in log
JBD2: Invalid checksum recovering block 336 in log
JBD2: Invalid checksum recovering block 336 in log
JBD2: Invalid checksum recovering block 337 in log
JBD2: Invalid checksum recovering block 338 in log
JBD2: Invalid checksum recovering block 339 in log
JBD2: Invalid checksum recovering block 339 in log
JBD2: Invalid checksum recovering block 341 in log
JBD2: Invalid checksum recovering block 341 in log
JBD2: Invalid checksum recovering block 342 in log
JBD2: Invalid checksum recovering block 342 in log
JBD2: Invalid checksum recovering block 342 in log
JBD2: Invalid checksum recovering block 346 in log
JBD2: Invalid checksum recovering block 347 in log
JBD2: Invalid checksum recovering block 347 in log
JBD2: Invalid checksum recovering block 348 in log
JBD2: Invalid checksum recovering block 349 in log
JBD2: Invalid checksum recovering block 350 in log
JBD2: Invalid checksum recovering block 351 in log
JBD2: Invalid checksum recovering block 352 in log
JBD2: Invalid checksum recovering block 352 in log
JBD2: Invalid checksum recovering block 353 in log
JBD2: Invalid checksum recovering block 354 in log
JBD2: Invalid checksum recovering block 358 in log
JBD2: Invalid checksum recovering block 358 in log
JBD2: Invalid checksum recovering block 362 in log
JBD2: Invalid checksum recovering block 366 in log
Journal checksum error found in Seagate8TB1
Seagate8TB1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1323567446, counted=1234126589).
Fix? yes
Free inodes count wrong (1907637, counted=1907621).
Fix? yes
Seagate8TB1: ***** FILE SYSTEM WAS MODIFIED *****
Seagate8TB1: 123/1907744 files (0.0% non-contiguous), 719379796/1953506385 blocks
osmc@osmc:~$ /dev/sda1 2048 15628053133 15628051086 7.3T Linux filesystem
-bash: /dev/sda1: Permission denied
osmc@osmc:~$ osmc@osmc:~$ sudo fsck -y /dev/sda1
-bash: osmc@osmc:~$: command not found
osmc@osmc:~$ fsck from util-linux 2.29.2
fsck from util-linux 2.29.2
osmc@osmc:~$ e2fsck 1.43.4 (31-Jan-2017)
-bash: syntax error near unexpected token `(’
osmc@osmc:~$ Seagate8TB1: recovering journal
-bash: Seagate8TB1:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 327 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 328 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 328 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 328 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 329 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 332 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 332 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 332 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 333 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 333 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 333 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 333 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 334 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 335 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 336 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 336 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 337 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 338 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 339 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 339 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 341 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 341 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 342 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 342 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 342 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 346 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 347 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 347 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 348 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 349 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 350 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 351 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 352 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 352 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 353 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 354 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 358 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 358 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 362 in log
-bash: JBD2:: command not found
osmc@osmc:~$ JBD2: Invalid checksum recovering block 366 in log
-bash: JBD2:: command not found
osmc@osmc:~$ Journal checksum error found in Seagate8TB1
-bash: Journal: command not found
osmc@osmc:~$ Seagate8TB1 was not cleanly unmounted, check forced.
-bash: Seagate8TB1: command not found
osmc@osmc:~$ Pass 1: Checking inodes, blocks, and sizes
-bash: Pass: command not found
osmc@osmc:~$ Pass 2: Checking directory structure
-bash: Pass: command not found
osmc@osmc:~$ Pass 3: Checking directory connectivity
-bash: Pass: command not found
osmc@osmc:~$ /lost+found not found. Create? yes
-bash: /lost+found: Is a directory
osmc@osmc:~$
thanks Sam this is result of that
just rebooted and hdd has mounted
just checking the films and all appears ok
many thanks to all that have helped
Sounds good. I would recommend you downloading Seagate Seatools on your PC and checking that drive with a short drive self test (this should work even though Windows can’t read the ext4 partition). If that passes it might not be a bad idea to make a copy of anything you don’t want to lose somewhere else, and then run a long drive self test. This will take a long time, and if your drive is not healthy it can cause the drive to break during the test, but if that test breaks the drive then it already had issues and was going to continue to behave badly. If the drive is healthy then the drive test is actually good for your information as it will find and move information from any areas that have weak sectors.
Feel free to mark this thread as solved.