[SOLVED] another drive goes wacko on me, anyone know what is this dos/mbr thing?

BW-userx · 07-09-2019, 07:56 AM

FoIJF*(AENEEC GRUMBBLE GRUMBBLE GRUMBBLE

as usual just yesterday this hdd worked perfectly, and today.. nope.

another one bytes the dust? They put out over 100 hdd in one second, and it takes over 80hrs+ to check just one for errors.

Code:

root@slack.it.netters:/home/userx
# e2fsck -f -y -v -C 0 /dev/sdc
e2fsck 1.45.2 (27-May-2019)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sdc contains `DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,32,33), end-CHS (0x3ff,254,63), startsector 2048, 1953521664 sectors' data


###################################


# mke2fs -n /dev/sdc
mke2fs 1.45.2 (27-May-2019)
/dev/sdc contains `DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,32,33), end-CHS (0x3ff,254,63), startsector 2048, 1953521664 sectors' data
Proceed anyway? (y,N)

what does that last part really say, what is the significance of it?

I was following that link in here, on how to use another superblock, then I get that as if this DOS/MBR thing is the real issue.

I use use this (these) drives as a usb port external drive. They are internal 2.5" laptop drives. NOT SSD's

does any one know how to proceed?

https://linuxexpresso.wordpress.com/...ock-in-ubuntu/

michaelk · 07-09-2019, 08:22 AM

You did not say why your running fsck but in both posted commands you did not include the partition number.

Quote:

e2fsck -f -y -v -C 0 /dev/sdc

mke2fs -n /dev/sdc

BW-userx · 07-09-2019, 08:46 AM

Quote:

Originally Posted by michaelk

You did not say why your running fsck but in both posted commands you did not include the partition number.

when I pluged it in this morning, and it was not showing up in my file manager, then further investagion showed me that badblock (crap), then I plugged in another drive and ran gparted on it checking it and it shows that command it uses so I tried it on the drive in question, then it again gave me that same superblock message, so I went and found that wed page again and ran that other command on it then it showed me that DOS/MBR message y/N so I selected no and posted, and according to that page it does not indicate partition just device?

Code:

sudo mke2fs -n /dev/xxx

if that is it, partition letter, well give me a second

Code:

Error reading block 17825895 (Input/output error) while getting next inode from scan.  Ignore error? yes

Force rewrite? yes

now it is just sitting at that spot. hanging up? just let it sit like that?

there is no light flashing to indicate it is doing anything to the drive. The light is no longer even on.

BW-userx · 07-09-2019, 09:05 AM

this 2TB had the same situation, but I've dd it, formatted it, used it, then it went back into that same message, and now it sits like this.

Code:

 root@slack.it.netters:/home/userx
# e2fsck -f -y -v -C 0 /dev/sdc1
e2fsck 1.45.2 (27-May-2019)
e2fsck: No such file or directory while trying to open /dev/sdc1
Possibly non-existent device?
root@slack.it.netters:/home/userx
# cfdisk /dev/sdc

Syncing disks.
root@slack.it.netters:/home/userx
# e2fsck -f -y -v -C 0 /dev/sdc1
e2fsck 1.45.2 (27-May-2019)
2TBext4: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes

e2fsck: Input/output error while recovering journal of 2TBext4
e2fsck: unable to set superblock flags on 2TBext4


2TBext4: ********** WARNING: Filesystem still has errors **********

root@slack.it.netters:/home/userx
# fsck -yv /dev/sdc1
fsck from util-linux 2.34
e2fsck 1.45.2 (27-May-2019)
2TBext4: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes

/sbin/e2fsck: Input/output error while recovering journal of 2TBext4
/sbin/e2fsck: unable to set superblock flags on 2TBext4


2TBext4: ********** WARNING: Filesystem still has errors **********

michaelk · 07-09-2019, 09:30 AM

The author posted for most examples /dev/xxx versus /dev/sdx5 probably because many would simply copy/paste and possibly erase/corrupt their data. I am not very patient and would most likely cancel the command. Have you looked SMART data yet?

Took me awhile to post and have not read #4 completely yet...

BW-userx · 07-09-2019, 10:25 AM

Quote:

Originally Posted by michaelk

The author posted for most examples /dev/xxx versus /dev/sdx5 probably because many would simply copy/paste and possibly erase/corrupt their data. I am not very patient and would most likely cancel the command. Have you looked SMART data yet?

Took me awhile to post and have not read #4 completely yet...

as I too got impantent < I plugged in my 2TB that is having the same issues, and issued the commands to check that like I was the 1tb and for some strange reason it went to the sdc1 and completed fixing that and now the 2tb is giving me this, as i been googling around trying to find a fix and this is my latest attempt.
2TB not that one I first posted on, That one is actually fixed(? crossing fingers)

Code:

root@slack.it.netters:/home/userx
# e2fsck -f -b 32768 -y /dev/sdc1
e2fsck 1.45.2 (27-May-2019)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
2TBext4: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: Input/output error while recovering journal of 2TBext4
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: unable to set superblock flags on 2TBext4


2TBext4: ***** FILE SYSTEM WAS MODIFIED *****

2TBext4: ********** WARNING: Filesystem still has errors **********

that SMART is a bit tricky for me, I got a go look that one up. (again)

Code:

 root@slack.it.netters:/home/userx
# smartctl -i /dev/sdc
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.57] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

michaelk · 07-09-2019, 11:17 AM

Some USB bridges don't pass SMART commands so that isn't going to help. It would be a coincidence if two drives started to fail at the same time. Unfortunately I don't have a good answer for fixing the superblock flags and a quick search didn't find much either.

BW-userx · 07-09-2019, 12:35 PM

I know and that is a 2TB too,

got this:

Code:

root@slack.it.netters:/home/userx
# smartctl -T permissive -a -d 3ware,0  /dev/sdc
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.57] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Tue Jul  9 12:34:03 2019 CDT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Warning! SMART Attribute Data Structure error: invalid SMART checksum.
Warning! SMART Attribute Thresholds Structure error: invalid SMART checksum.
=== START OF READ SMART DATA SECTION ===
SMART Status command failed
Please get assistance from https://www.smartmontools.org/
Register values returned from SMART Status command are:
 ERR=0x05, SC=0x00, LL=0x01, LM=0x00, LH=0x00, DEV=0x00, STS=0x00
SMART Status not supported: Invalid ATA output register values
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x00) 	Offline data collection not supported.
SMART capabilities:            (0x0000)	Automatic saving of SMART data		is not implemented.
Error logging capability:        (0x00)	Error logging NOT supported.
					No General Purpose Logging support.

SMART Attributes Data Structure revision number: 30
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
176 Erase_Fail_Count_Chip   0x0000   000   000   000    Old_age   Offline      -       0

SMART Error Log not supported

SMART Self-test Log not supported

Selective Self-tests/Logging not supported

BW-userx · 07-09-2019, 05:58 PM

I had to pull my data storage disk out of my laptop and put this 2TB in and ran this.

Code:

$ sudo e2fsck -y -v /dev/sda1
e2fsck 1.45.2 (27-May-2019)
2TBext4: recovering journal
Setting free inodes count to 122093104 (was 122093106)
Setting free blocks count to 433471778 (was 433633933)
2TBext4: clean, 8656/122101760 files, 54906590/488378368 blocks

then this

Code:

$ sudo e2fsck -f -y -v -C 0 /dev/sda1
e2fsck 1.45.2 (27-May-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure                                           
Pass 3: Checking directory connectivity                                        
Pass 4: Checking reference counts
Pass 5: Checking group summary information                                     
Block bitmap differences:  +67108864 +67108880 +(67108896--67109407)           
Fix? yes

                                                                               
2TBext4: ***** FILE SYSTEM WAS MODIFIED *****

        8656 inodes used (0.01%, out of 122101760)
          19 non-contiguous files (0.2%)
          13 non-contiguous directories (0.2%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 8421/227
    54906590 blocks used (11.24%, out of 488378368)
           0 bad blocks
           8 large files

        8273 regular files
         374 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
        8647 files

Now it is working again, yes!! It does not like usb ports much...

thanks for your suggestions...