Tabular: Displays the log in table format.Ĭlear: Deletes the specified controller protocol.Īrcconf getlogs controller-number device ¦ dead ¦ event > FILENAME.log You can also specify the following parameters: You can use the following parameters to specify the type of log entries displayed:Įxample: arcconf getlogs 1 device tabularĭEVICE: Shows all log entries with errors the controller could detect on all connected devices.ĭEAD: Shows all log entries where device and hard disk failures were recorded.ĮVENT: Shows all log entries with information about special events (e.g. Use this command to display the log entries. Use this command to display information about the existing hard disks.Īrcconf getlogscontroller-number device ¦ dead ¦ event This command displays information about the RAID controller, configuration, RAID arrays, available disks and their current state. Ricardogroetaers, on the other hand, offers some interesting thoughts focused on why the problem might have occurred and wants to explore evidence rather than jump to conclusions about blame.Use the commands listed below to access hardware RAID and configuration information: Adaptec RAID Controller If forum comments cannot be constructive nor helpful (which is what most folk look for in a response) then better leave them unsaid. So kadaitcha man's condescending and misdirected comments should be treated with the contempt they deserve. It is one of three I bought about a year ago and have been using in a very similar way: the others are fine, as are several other much older and more heavily used USB sticks. So it had undergone scarcely any write/read cycles. It was not used "as an almost daily driver". I had not used the stick for backups or any other purpose (I have separate hard disk drives for backup). I had run perhaps half a dozen such sessions, maximum, usually just brief tests and in no case using persistence.
When it was brand new and unused, I had burned a single ISO image on to it in order to run Live sessions. My Sandisk USB stick was barely a year old. However the lecture was based on a number of mistaken assumptions. Well, I suppose it was predictable that kadaitcha man would seize the opportunity of my tongue-in-cheek 'witchcraft' remark to deliver a patronising and finger-wagging lecture with the core message that he regards me - like other forum members who have similarly benefited from his opinions - as ignorant and foolish, and that whatever went wrong was my own fault. But I wonder - can anybody suggest any further action to try to recover it? Nor do I fully understand how I might "run e2fsck with an alternate superblock".Īt the end of the day if the USB can't be revived I will simply throw it away. Obviously I have no idea what "bad magic number in superblock" means. Is corrupt, and you might try running e2fsck with an alternate superblock:Į2fsck -b 32768 sudo dd if=/dev/zero of=/dev/sdbĭd: writing to '/dev/sdb': Input/output errorĤ11283456 bytes (411 MB, 392 MiB) copied, 40.2964 s, 10.2 sudo mkfs.msdos -f 32 /dev/sdb If the device is valid and it really contains an ext2/ext3/ext4įilesystem (and not swap or ufs or something else), then the superblock The superblock could not be read or does not describe a valid ext2/ext3/ext4įilesystem. Here is what showed up in the terminal:Įxt2fs_open2: Bad magic number in super-blockįsck.ext2: Superblock invalid, trying backup blocks.įsck.ext2: Bad magic number in super-block while trying to open /dev/sdb When fsck threw up a error message, I just tried dd, and then tried to format. I'm not an expert in terminal commands, but I had a go.
When casting around for other possible rescue techniques I came across a recommendation to try fsck and then dd in the terminal. In both I get error messages which refer to "input/output errors" in write mode.
I have tried to reformat and/or repair it both in Linux Mint (using Gparted) and in Windows (using diskpart). It has no other data or files which are important or need recovering. Somehow the process didn't work, and the USB stick got corrupted in some way.
I was using Rufus on a Windows 7 computer. I recently tried to burn an ISO of a newer version of Mint on to a USB stick which previously had another older and now EOL distro image on it. I have various USB sticks, from which I run Live sessions of Linux distros I want to try.